Thaths wrote:
> Are you able to ping the nameserver IP addresses? If you are, then the
> problem would appear to be not your connectivity. Also, try telnetting
> to port 53 of your name servers.
Telneting to port 53 is fine - but easier still is something like
$ dig @ip.of.name.server www.yahoo.com
or something similar
See if you can get an answer from that nameserver, and if so, how fast
If there's some latency / timeout issues with one or both your
nameservers due to load issues it might explain what you are seeing
[quite likely with cable ISPs that stick their nameserver / resolvers
onto a box that does several other things, and moreover is likely being
hammered by nimda etc junk virus generated dns queries ...]
Or your cable ISP's dhcp servers are returning a pair of totally wrong
nameservers (like, they changed the IPs of their dns servers but forgot
to update their dhcp server settings to show the new IPs]
Fun like this can be resolved by setting up bind or djbdns as a local
resolver, and sticking 127.0.0.1 in resolv.conf
Having v6 in there is not much use unless you have v6 access or use it
(I do have a v6 tunnel in place so it comes in handy) .. you can't rmmod
v6 but you can edit /etc/modules.conf or whatever your distro uses to
stop loading the v6 module at boot.
srs
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
linux-india-help mailing list
linux-india-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-india-help
