Ian wrote: > I went back and forth between my Debian server and my Fedora desktop > and noticed some interesting things. On Fedora DNS lookups work fine > in elinks and every other applications except wget, unless ipv6 is > enabled in which case it takes exactly 20 seconds to do a DNS lookup. > Wget on Fedora still takes 20 seconds to do its DNS lookup even with > ipv6 disabled unless I explicitly use the -4 flag with it. On Debian > all DNS lookups take 20 seconds for me even with ipv6 disabled. The > resolv.conf on both boxes just has the ip of the router listed as the > nameserver. > > When I added OpenDNS as the first nameserver in resolve.conf, all DNS > lookups started working like they should in Debian and wget lookups > were corrected in Fedora. If I can figure out how to keep my /etc/ > resolv.conf from being wiped out on reboot I think everything will be > working correctly. > > I'm curious why OpenDNS works so much better for me than my ISPs > nameservers and why there is this difference in behaviour between > Debian and Fedora when both are setup right now as standard clients on > the network. > > Thanks > Ian > Well, one thing I notice from your post above, is that you were *not* using your isp's name servers, if you had your router's ip listed as the name server. in resolv.conf. That was very likely the cause of the slow look ups.
If I log into my router, I get the following values for name servers - DNS Address #1: 205.171.3.25 DNS Address #2: 205.171.2.25 The router's it self's ip address is 192.168.0.1, which is a far cry from the correct settings for a name server. You seem to have found a solution, by setting your name server to OpenDNS, but you should additionally be able to call your isp, and ask them what the correct values are for your two default name servers. You may be getting good look up times now with only one setting to OpenDNS for a name server, but as they gain in popularity, it's entirely possible that their increasing client load will slow things down for you, especially as you continue to only have one correctly specified name server. Having a second name server correctly specified, can keep your look up speeds in an acceptable range, if one of the name servers slows down for some reason, and is likely why your isp usually points your configuration at two of them, instead of just one. For servers that you access on a very often basis, you can also bypass the DNS servers entirely, by specifying the ip addresses for those web sites you visit most frequently directly in your /etc/hosts file. Just do a whois on each server to get it's ip address, and add that ip to the front of a new line in your hosts file, with the corresponding domain name following it after a space on the same line, and you will have your own name server going on there, which is much quicker, at least until you begin to get a very, very, large hosts file which may slow things a little. You should be in good shape with that trick, unless one of your often accessed servers changes it's ip address for some reason, but for the most part they tend to remain at a static ip address, so that shouldn't be too much of a problem. Later, Ray Parrish -- Human reviewed index of links about the computer http://www.rayslinks.com Poetry from the mind of a Schizophrenic http://www.writingsoftheschizophrenic.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup -~----------~----~----~----~------~----~------~--~---
