Doug Barton wrote: > Howdy, > > With -current built from sources updated at around 8pm PST, I can't > resolve hosts on the command line if /etc/resolv.conf points to a name > server running on the local host. The local name server itself is > working fine, and I can reach any host in /etc/hosts as well. > > ktrace /sbin/ping hub.freebsd.org > ^C > > kdump > 651 ktrace RET ktrace 0 > 651 ktrace CALL execve(0xbfbffb03,0xbfbff9e4,0xbfbff9f0) > 651 ktrace NAMI "/sbin/ping" > > /etc/nsswitch.conf is unchanged, and contains only: > hosts: files dns > > It doesn't matter if /etc/resolv.conf points to 127.0.0.1, or the IP of > the box. As soon as I point /etc/resolv.conf at a name server on another > host, it works.
I'm having similar problems. If I have 2 or 3 nameservers listed and 127.0.0.1 first, then I get a 10-20 second timeout before the resolver library switches to another server. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
