On Wednesday 15 February 2006 23:37, Patrick von der Hagen <patrick@xxxxxxxxx> wrote: > > [root@localhost ~]# cat /etc/resolv.conf > # generated by NetworkManager, do not edit! > > search hek.uni-karlsruhe.de > > > nameserver 62.72.64.237 > nameserver 62.72.64.241 > This appears to be the problem - your glibc resolver is contacting those nameservers directly, and they are possibly returning AAAA records before A records for the NS or name you are looking up - sending us the tcpdump log may be helpful in diagnosing the glibc resolver problem. NetworkManager(NM) is meant to use named in caching-nameserver mode, and to write ONLY the line: 'nameserver 127.0.0.1 ' to /etc/resolv.conf . It appears that this aspect of NM is not working correctly at the moment - the NM maintainer has been informed and is working on a solution. Meanwhile, if you remove the nameservers from /etc/resolv.conf: $ sed -i '/nameserver/d' /etc/resolv.conf and start named: $ service named start The timeouts should disappear. Regards, Jason Vas Dias<jvdias@xxxxxxxxxx> Red Hat Inc. -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list