Re: hosts, resolv setup?
Sorry, adding a dot to hostnames in /etc/hosts makes it even
worse. Then .my.own.domain is added twice: host4.my.own.domain. is
followed by host4.my.own.domain.my.own.domain. instead of
host4.my.own.domain.
It seems that the search order is: first external nameservers, then hosts
files. This is in contrast to the setup in resolv.conf etc.
Everything is OK on my RHL(rawhide) and MDK(cooker) boxes but not the
debian(unstable) box.
BTW:
cat /etc/hostmame gives
host4.my.own.domain
this name is also present in
/etc/hosts
/Svante
stefan@alfredsson.org writes:
> Quoting Svante Signell <svante.signell@telia.com> [010221 10:28]:
> > > > Quoting Svante Signell <svante.signell@telia.com> [010217 07:50]:
> > > > /etc/hosts:
> > > > 192.160.0.1 host1.my.own.domain host1
> > > > 192.160.0.2 host2.my.own.domain host2
>
> > Tried tcpdump on a ssh to the same host using the local I/F 127.0.0.1
> > and the LAN I/F 192.160.0.4. sshd tries to contact the tree nameservers in my resolv.conf twice
> > times before timing out. In other cases it tries four itmes before
> > password prompt and the twice after.
>
> > 09:37:07.565017 192.168.0.4.32824 > nameserver1.53: 58110+ A? host4.my.own.domain. (39) (DF)
>
> I remember some problems I had with sendmail, when I used dialup. It
> would hang the bootup 60 seconds, while trying to resolve its own
> hostname. It turned out that I needed to append a '.' to my hostnames in
> the hostfile. Seeing that the names from tcpdump are asked for with a
> dot at the end (indicating the final "top domain"?), it might be worth
> trying to add a dot to your names?
>
>
> > Feb 21 09:23:00 host4 sshd[6451]: WARNING: /etc/ssh/primes does not exist, using old prime
> > Feb 21 09:23:34 host4 sshd[6451]: reverse mapping checking getaddrinfo for host4.my.own.domain failed - POSSIBLE BREAKIN ATTEMPT!
>
> I can understand that a 34 second delay while logging in is annoying :)
>
> /Stefan
Reply to: