Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Jun 2019 08:26:53 -0700 (PDT)
From:      "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>
To:        "Ronald F. Guilmette" <rfg@tristatelogic.com>
Cc:        freebsd-net <freebsd-net@freebsd.org>
Subject:   Re: localhost woes -- help requested
Message-ID:  <201906191526.x5JFQrVT018680@gndrsh.dnsmgr.net>
In-Reply-To: <26907.1560925410@segfault.tristatelogic.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> In message <201906190617.x5J6HQmA016708@gndrsh.dnsmgr.net>, 
> Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> wrote:
> 
> >> In message <201906181719.x5IHJ8g0014687@gndrsh.dnsmgr.net>, 
> >> "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> wrote:
> >> 
> >> >What is in /etc/host.conf, /etc/resolv.conf, do you have DNS running?
> >> 
> >> 
> >> 1)  https://pastebin.com/raw/wXTTgd9R
> >This is /etc/hosts, not /etc/host.conf
> ># cat /etc/host.conf
> ># Auto-generated from nsswitch.conf
> >hosts
> >dns
> >
> >> 2)  https://pastebin.com/raw/PiGpN0LU
> >> 
> >> 3)  Yes, local-unbound
> >
> >Ok, if you comment out ::1 from /etc/hosts then the lookup is
> >going to fall through to DNS with the default /etc/host.conf file
> >and you'll get what ever your dns is configured to return, which
> >is usually the exact some thing as /etc/hosts has.
> 
> So basically you're telling me that local-unbound has taken it upon
> itself to decide for me, regardless of what is or isn't in my /etc/hosts
> file, what addresses "localhost" should resolve to??

Yes, dns resolvers shipping for the last 5 decades have all shipped
with default "localhost" values.  Both "localhost" and 127.in-addr.arpa
zones existed iirc in the very first version of bind.

> 
> If so, that really is rather presumptive on its part.

No, well defined by RFC.
I would suggest a starting read at https://en.wikipedia.org/wiki/Localhost

Specifically this detail:
	In the Domain Name System, the name localhost is reserved as a
	top-level domain name, originally set aside to avoid confusion
	with the hostname used for loopback purposes.[3] IETF standards
	prohibit domain name registrars from assigning the name localhost. 


And finally:
https://tools.ietf.org/html/rfc2606#section-2
at 
      The ".localhost" TLD has traditionally been statically defined in
      host DNS implementations as having an A record pointing to the
      loop back IP address and is reserved for such use.  Any other use
      would conflict with widely deployed code which assumes this use.

Regards,
-- 
Rod Grimes                                                 rgrimes@freebsd.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201906191526.x5JFQrVT018680>