Peter Crowther wrote:
I'm somewhat more interested as to how a "correctly configured" DNS for this environment would either take 3 seconds to fail, or return an IP address that can't then be pinged. Surely it should fail immediately without returning an address? So I agree with you that the DNS needs work, just not about the symptom :-).
Correctly configured DNS in any configuration will return almost immediately.. it'll either fail or succeed. I'm not actually sure how a machine not connected to the internet could take 3 seconds to resolve a name.. that's a new one on me. Even if it somehow returns an unpingable address as there's no default route the machine will just return immediately with a failure, so no harm done. If for some reason there's a default route given by a misconfigured dhcp server that router will immediately return an ICMP host unreachable or similar, so that doesn't really slow things down. What we appear to be seeing in some cases is a combination of misconfigurations where a network is setup as if it is connected to the internet but isn't.. that's quite creative - I can't think of a way to do it (well not a sane way anyway.. certainly nothing that could be done accidentally). Tony _______________________________________________ cvsnt mailing list cvsnt@cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/
