[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ipv6 maybe has arrived.



On Wed, Feb 15, 2023 at 08:30:08AM +0100, Michel Verdier wrote:
> Le 15 février 2023 gene heskett a écrit :
> 
> > gene@bpi54:~$ grep -i bpi54 /etc/hosts
> > 192.168.71.12		bpi54.coyote.den	bpi54
> > gene@bpi54:~$ getent hosts bpi54
> > fe80::4765:bca4:565d:3c6 bpi54
> > gene@bpi54:~$ ping -c1 coyote (this machines alias in /etc/hosts)
> > ping: coyote: Name or service not known
> 
> If coyote is really an alias and not part of domain name give us
> grep -i coyote /etc/hosts
> 
> For what you show bpi54 is the short hostname so you need to do
> ping -c1 bpi54
> and not
> ping -c1 coyote

bpi54 is the machine where Gene is issuing the commands.  What we
need to see is bpi54 failing to ping some OTHER machine on his local
network.  I don't know whether "coyote" is such a machine, but if it
is then I would have expected to see something like:

gene@bpi54:~$ grep -i coyote /etc/hosts
192.168.71.11                   coyote.coyote.den       coyote

followed by a whole bunch of other lines that are false hits, because
for some reason Gene used "coyote" as both a local hostname *and* part
of his local domain name.

Surely there must be some machine on Gene's network which is in the
/etc/hosts file on bpi54, and which is not named "coyote" or "den".
That's what we want to see.

As I said before, it doesn't even have to be a machine that works and
responds to pings.  It could be a printer that he used in 2003 and no
longer exists, but is still in the /etc/hosts file.  Anything.

That said, I'm curious about this part oF Gene's result:

> > gene@bpi54:~$ grep -i bpi54 /etc/hosts
> > 192.168.71.12               bpi54.coyote.den        bpi54
> > gene@bpi54:~$ getent hosts bpi54
> > fe80::4765:bca4:565d:3c6 bpi54

Where does getent pull that IPv6 address from?  That's not what I get
when I look myself up:

unicorn:~$ grep -i unicorn /etc/hosts
127.0.1.1   unicorn.wooledge.org    unicorn
unicorn:~$ getent hosts unicorn
127.0.1.1       unicorn.wooledge.org unicorn

I don't understand Gene's result.

Oh, and one last thing that popped into my head this morning: name
service caching daemons.  Is it possible that Gene is running nscd or
something like it, and that this is influencing his results?  It might
explain why he felt a need to reboot after changing something.


Reply to: