Re: DSL Internet Connection Question
Hello Robert, Wednesday, December 21, 2005, 4:20:28 PM, you wrote: RCW> Would adding the line: RCW> supercede domain-name-servers "dns.IP.address.1 dns.IP.address.2"; RCW> ...do the job of hardcoding: RCW> nameserver dns.IP.address.1 RCW> nameserver dns.IP.address.2 RCW> ...into the 'resolv.conf' file? Answering my own question... the syntax and corrected spelling that works for this, is: supersede domain-name-servers dns.IP.address.1, dns.IP.address.2; Works great... but still does not address why a kludge is needed, which I now will get to work figuring out. TU>> You should however check, why you get wrong values from your TU>> router. I have given this some thought... since the same value... 192.168.1.254 which is the internal IP value on the modem/router, is the same value that is passed to Red Hat, and Windows, and works for them, I do not thing the value is 'wrong'... and since it also works with OpenBSD, but with about a 60 second delay (like something times out, and then defaults to a secondary (else) behaviour, which does work... ...I suspect that I have something else set wrong, for when I installed the operating system, and when I eventually, using trial and error, on one thing at a time, get lucky and change the right variable, I will be able to remove the hard-coded DNS IP's from dhclient.conf, and things will run smoothly. At least now, I can use the machine with Internet access, while I figure out the right configuration. -wittig http://www.robertwittig.com/ .
Re: DSL Internet Connection Question
Hello Fred, Wednesday, December 21, 2005, 4:49:51 PM, you wrote: FC> You could put your local changes in /etc/resolv.conf.tail - thus when FC> resolv.conf is overwritten your local changes will be preserved. Yep, thanks! Another listmember suggested this to me off-list, and I did it, and it has reduced the lag time to three seconds... the amount of time that it takes for the incorrect entry applied by DHCP to time out, and for the next nameserver (from the *.tail file to be read. -wittig http://www.robertwittig.com/ .
Re: DSL Internet Connection Question
Hello Tobias, Wednesday, December 21, 2005, 1:00:08 PM, you wrote: TU> To fix these values locally, take a look at dhclient.conf(5), especially TU> at the supersede option and domain-name-servers. Right now 'dhclient.conf' is completely commented out. Would adding the line: supercede domain-name-servers "dns.IP.address.1 dns.IP.address.2"; ...do the job of hardcoding: nameserver dns.IP.address.1 nameserver dns.IP.address.2 ...into the 'resolv.conf' file? TU> You should however check, why you get wrong values from your TU> router. Yes, I plan on figuring this out, eventually. What puzzles me, is that exactly the same line... nameserver 192.168.1.254 ...which is a private IP addy, placed in the 'resolv.conf' file by DHCP on my Red Hat installation, and there, everything works fine. As soon as I know OpenBSD a little better, I will probably be able to figure out what is different, that makes things work in Red Hat, but break in Open BSD. Then I can replace the kludge with something permanent. thanks, -wittig http://www.robertwittig.com/ .
Re: DSL Internet Connection Question
Robert C Wittig wrote: 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. Thanks in advance, for any suggestions, comments, etc. -wittig website: http://www.robertwittig.com/ . Hi, You could put your local changes in /etc/resolv.conf.tail - thus when resolv.conf is overwritten your local changes will be preserved. HTH Fred
Re: DSL Internet Connection Question
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
