On Wed, Dec 21, 2005 at 11:31:07AM -0600, Robert C Wittig wrote: > I re-wrote /etc/resolv.conf with the nameserver values that my > Modem/Router describes as DNS-1 and DNS-2, and as soon as I saved the > file, lynx, whois, etc., worked fast like a rocket, when domain names > were used, so obviously, this 'fixed' the problem. > > So I wrote a shell script that, when run, will re-write > /etc/resolv.conf with the current working DNS-1 and DNS-2 values, that > I can run after boot, to replace the faulty info that is being place > in /etc/resolv.conf, during bootup... but the 'fix' only works for 30 > minutes, at which time the resolv.conf file is over-written, I would > assume, by DHCP, and everything reverts to the delay of about 1 > minute, for domain name resolution. > > This is a lame solution, but better than nothing, for the moment, but > I definitely have to figure out what actually needs fixing. My best > guess is that the 'one minute hang' is because something, in one of > the config files, should not be where it is, but there are a lot of > variables to play with, and I don't want to just continue blindly > messing with things, which I have been trying for the last couple > days, and having them not help, or make things worse, and then > restoring them to their original state. > > Thanks in advance, for any suggestions, comments, etc. > > > -wittig > website: http://www.robertwittig.com/ > . > >
To fix these values locally, take a look at dhclient.conf(5), especially at the supersede option and domain-name-servers. You should however check, why you get wrong values from your router. Tobias
