From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why do we add the local host name to the 127.0.0.1 / ::1 entry in the /etc/hosts file?
Date: Wed, 10 Mar 2021 09:58:47 -0700 [thread overview]
Message-ID: <c3fb63b9-208a-a7d5-687f-d1c9e0563324@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <9854601.nUPlyArG6x@lenovo.localdomain>
On 3/10/21 8:25 AM, Michael wrote:
> I think this is relevant to DNS resolution of/with domain controllers
> and may depend on the AD/DC topology.
I disagree. Pure Linux in a MIT / Heimdal Kerberos environment has the
same requirements. Hence having nothing specific to do with Active
Directory, much less the AD topology.
> The idea is to use the LAN address of the box as the first address
> in /etc/hosts and use 127.0.0.1 as the second address in the file.
Please elaborate. Because I believe the following qualifies with your
statement:
192.0.2.1 host.example.net host
127.0.0.1 localhost
Which is effectively the same as the following:
127.0.0.1 localhost
192.0.2.1 host.example.net host
Both of which are different than the following:
192.0.2.1 host.example.net host
127.0.0.1 localhost host.example.net host
Putting host.example.net and host on the 127.0.0.1 line doesn't
accomplish anything. And it still suffers from -- what I think is --
the poor recommendation that I'm inquiring about.
> If more AD/DNS servers exist in the network, then 127.0.0.1 could be
> even further down the list.
>
> https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff807362(v=ws.10)?redirectedfrom=MSDN
What does the number of DNS servers have to do with the contents of the
/etc/hosts file?
How is the contents of the /etc/hosts file related to the
/etc/resolv.conf file?
> I haven't over-thought this and there may be more to it, but on a
> pure linux environment I expect this would not be a requirement,
> hence the handbook approach.
Apples and bowling balls. /etc/hosts is not the same concept as
/etc/resolv.conf.
--
Grant. . . .
unix || die
next prev parent reply other threads:[~2021-03-10 16:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 22:23 [gentoo-user] Why do we add the local host name to the 127.0.0.1 / ::1 entry in the /etc/hosts file? Grant Taylor
2021-02-22 6:20 ` Andrew Udvare
2021-02-25 2:37 ` Peter Humphrey
2021-02-25 2:50 ` Grant Taylor
2021-02-25 7:02 ` Arve Barsnes
2021-02-25 7:33 ` Grant Taylor
2021-03-10 5:09 ` Grant Taylor
2021-03-10 13:27 ` Mark Knecht
2021-03-10 15:25 ` Michael
2021-03-10 16:00 ` Mark Knecht
2021-03-10 16:38 ` Michael
2021-03-10 17:07 ` Grant Taylor
2021-03-10 17:01 ` Grant Taylor
2021-03-10 16:58 ` Grant Taylor [this message]
2021-03-11 13:38 ` Michael
2021-03-11 16:50 ` Grant Taylor
2021-03-12 19:04 ` Michael
2021-03-13 19:01 ` Grant Taylor
2021-03-16 12:16 ` Michael
2021-03-16 12:33 ` Peter Humphrey
2021-03-16 18:54 ` Grant Taylor
2021-03-11 17:04 ` Grant Taylor
2021-03-10 16:44 ` Grant Taylor
2021-03-10 17:43 ` Mark Knecht
2021-03-10 18:37 ` Grant Taylor
2021-03-11 10:54 ` Wols Lists
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3fb63b9-208a-a7d5-687f-d1c9e0563324@spamtrap.tnetconsulting.net \
--to=gtaylor@gentoo.tnetconsulting.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox