-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Maybe your local domain ends in .local ? Change it. The Bind release notes included in 9.1 says that from now, .local domain is used as a broadcasting one (I don't know why, but seems there's an RFC to read). In my LAN, I had same problem until I've RTFM an discovered this "little" issue. Changed .local domain for another one, and question solved. El Domingo, 6 de Junio de 2004 21:23, Brett A. Taylor escribió:
hi everyone,
Finally got around to abandoning Mandrake on my workstation in favour of SUSE 9.1. I'm having some rather frustrating problems with the DNS resolver. First, some background: the SUSE system sits behind another box that connects to my DSL connection and provides NAT, DHCP and a DNS forwarder. AFAIK, there is *nothing* wrong with this system, nor the DNS forwarder (not even with my ISP's DNS) as all other systems on the lan all run fine. Even before the switch to SUSE I had no problems on this particular box, so I'm quite confident it's not a physical/hardware-layer issue.
So the problem ... the new SUSE box gets an IP and everything totally fine. And quickly, too. When I ping, use host or dig, names are resolved instantly. But when I try and actually connect to a remote host, there's a 5+ second delay on the resolution. So, pinging www.suse.com is fine and quick, but as soon as I try and use Mozilla, Konquerer, lynx, or anything (even telnetting to port 80), there's a HUGE delay before the name is resolved. Once it's resolved the connection is fine. And it's not unique to port 80 -- this happens with any other protocol, so it seems.
I've fiddled with network settings manually a little, and restarted the computer, and network a gazillion times, with no luck.
What can I do? This is highly annoying and rending this computer almost entirely unusable...
Thanks. Brett -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAxCW8SpJ/cZmKQqcRArNsAJ4zzplXTvCfOYucnAQdaE3FVDDASwCcDiep ET2jSYI3vjyaTvmCzk4Mk5Y= =hDfJ -----END PGP SIGNATURE-----