Re: resolv.conf changing at boot -- solved for now at least
Don Jackson wrote: > After recent upgrades in etch, I found my Firefox, Thunderbird, etc. > waiting long periods for apparently DNS lookup (10-20 seconds every > time). This is happening on two different computers which were upgraded. > > I find that my original entries of two nameservers in my resolv.conf > file are being wiped out every time I boot. > > I have a router (D-Link DI-604) and several computers on my LAN. The > router is 192.168.0.1. That is the address the resolv.conf file is > being changed to for nameserver on bootup. By restoring (editing) the > resolv.conf file to the proper nameservers of 214.134.xxx.yyy and > 214.134.xxx.zzz. then everything works fine (no significant delay for > DNS lookup)...until next time I reboot and they're back to 192.168.0.1 > in resolv.conf. (and the 214.134... entries missing). > > Can anyone point me to where/what is happening here? Maybe I have a > misunderstanding of wherein the problem lies. The DI-604 router shows > the 214.134... nameservers correctly when I look at it. These are > nameservers provided by my ISP. I have not changed anything recently > that I could imagine would affect this. > > (I do not have "resolvconf" installed -- as mentioned in some past > messages on this list.) > > Thanks, > Don Thanks for the several responses on this. I have "fixed" my problem for the time being by following the suggestion of several by installing resolvconf. My understanding of the total situation is still not clear (and may never be) and I see that it appears to be not only a very large "can of worms" but also an emotional topic as well. Just to document (not that anyone cares... ;-) ... I was hesitant to install resolvconf since in searching past archives on the resolv.conf problem, the resolvconf package was mentioned many times AS BEING THE CAUSE of problems and it was suggested uninstalling it and the links it created. The other problem I had with this situation is that everything had been running smoothly for months, I had changed nothing recently with either router or Debian "etch" installation on either computer, when suddenly on Monday (May 22) both computers started having the DNS lookup delay. (The computers are periodically upgraded to latest etch however.) I found that by restoring my resolv.conf file to what it had been several months ago (from a backup) with the often suggested procedure of putting in the actual nameserver IP address, the lookup delay problem went away (until reboot). This suggested to me that it was not an ISP change or problem. Since both computers in question are dual-booting to seldom-used Windows 2000, there was not a delay problem at all with Win2k. Again, showing not an ISP change or problem. Back with etch and the delay... pinging a domain name gives about 10 second delay between "pings". This is not the case after installing and configuring the resolvconf program. Thanks again for the help and advice. I'd still love to have a pointer or two to a good "howto" on really how one should set up a rather simple system such as mine relative to the DNS nameservers the "correct way" (instead of any "workarounds"). Or is it just a big can of worms? Regards, Don -- Those who say it can't be done are usually interrupted by others who are doing it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: resolv.conf changing at boot
Don Jackson wrote: > After recent upgrades in etch, I found my Firefox, Thunderbird, etc. > waiting long periods for apparently DNS lookup (10-20 seconds every > time). This is happening on two different computers which were upgraded. > > I find that my original entries of two nameservers in my resolv.conf > file are being wiped out every time I boot. > I have a router (D-Link DI-604) and several computers on my LAN. The > router is 192.168.0.1. That is the address the resolv.conf file is > being changed to for nameserver on bootup. Sounds like you are using DHCP which will indeed overwrite the resolv.conf. The router then supplies itself as a DNS server, unfortunately it is not very good (I know, I own a few DI-604's.) You may want to investigate the resolvconf package (which is designed to fix this exact sort of problem,) or stop using DHCP. Hope this helps, -- George Borisov DXSolutions Ltd signature.asc Description: OpenPGP digital signature
Re: resolv.conf changing at boot
On Tue, May 23, 2006 at 01:03:48PM -0500, Don Jackson wrote: >After recent upgrades in etch, I found my Firefox, Thunderbird, etc. >waiting long periods for apparently DNS lookup (10-20 seconds every >time). This is happening on two different computers which were >upgraded. > >I find that my original entries of two nameservers in my resolv.conf >file are being wiped out every time I boot. > >I have a router (D-Link DI-604) and several computers on my LAN. The >router is 192.168.0.1. That is the address the resolv.conf file is >being changed to for nameserver on bootup. By restoring (editing) the >resolv.conf file to the proper nameservers of 214.134.xxx.yyy and >214.134.xxx.zzz. then everything works fine (no significant delay for >DNS lookup)...until next time I reboot and they're back to 192.168.0.1 >in resolv.conf. (and the 214.134... entries missing). > >Can anyone point me to where/what is happening here? Maybe I have a >misunderstanding of wherein the problem lies. The DI-604 router shows >the 214.134... nameservers correctly when I look at it. These are >nameservers provided by my ISP. I have not changed anything recently >that I could imagine would affect this. > >(I do not have "resolvconf" installed -- as mentioned in some past >messages on this list.) If your router is handing out IP addresses using DHCP then it might also hand out DNS entries. That would explain why your /etc/resolv.conf keeps being overwritten. AFAICS you have two options: 1. Make sure your router (DHCP server) knows of the DNS you want to use. 2. Add a script to get your DCHP client to add the DNS entries you want. (If you use dhcp3-client then you should take a look at /etc/dhcp3/dhclient-*-hooks.d/.) /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. Most people, I think, don't even know what a Rootkit is, so why should they care about it? -- Thomas Hesse, president of Sony-BMG's Global Digital Business, commenting on XCP pgp5lcSEztKIr.pgp Description: PGP signature
Re: resolv.conf changing at boot
Have you set a DHCP in your router for clients LAN? I have had the same problem, and using static IP and DHCP disabled i fixed the problem. ... On 5/23/06, Don Jackson <[EMAIL PROTECTED]> wrote: After recent upgrades in etch, I found my Firefox, Thunderbird, etc. waiting long periods for apparently DNS lookup (10-20 seconds every time). This is happening on two different computers which were upgraded. I find that my original entries of two nameservers in my resolv.conf file are being wiped out every time I boot. I have a router (D-Link DI-604) and several computers on my LAN. The router is 192.168.0.1. That is the address the resolv.conf file is being changed to for nameserver on bootup. By restoring (editing) the resolv.conf file to the proper nameservers of 214.134.xxx.yyy and 214.134.xxx.zzz. then everything works fine (no significant delay for DNS lookup)...until next time I reboot and they're back to 192.168.0.1 in resolv.conf. (and the 214.134... entries missing). Can anyone point me to where/what is happening here? Maybe I have a misunderstanding of wherein the problem lies. The DI-604 router shows the 214.134... nameservers correctly when I look at it. These are nameservers provided by my ISP. I have not changed anything recently that I could imagine would affect this. (I do not have "resolvconf" installed -- as mentioned in some past messages on this list.) Thanks, Don -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Michele Della Marina [EMAIL PROTECTED]
Re: resolv.conf changing at boot
Don Jackson wrote: > I have a router (D-Link DI-604) and several computers on my LAN. The > router is 192.168.0.1. That is the address the resolv.conf file is > being changed to for nameserver on bootup. By restoring (editing) the > resolv.conf file to the proper nameservers of 214.134.xxx.yyy and > 214.134.xxx.zzz. then everything works fine (no significant delay for > DNS lookup)...until next time I reboot and they're back to 192.168.0.1 > in resolv.conf. (and the 214.134... entries missing). > > Can anyone point me to where/what is happening here? You use DHCP and your DHCP client changes /etc/resolv.conf because new name servers are announced. It is one of the main reasons to use DHCP: getting a working network setup > Maybe I have a > misunderstanding of wherein the problem lies. The DI-604 router shows > the 214.134... nameservers correctly when I look at it. These are > nameservers provided by my ISP. I have not changed anything recently > that I could imagine would affect this. > > (I do not have "resolvconf" installed -- as mentioned in some past > messages on this list.) But installing it would be the solution to your problem as you can define settings that are always present. Another solution would a setup of the router to your preferred settings. Also ask yourself what piece in the chain causes the DNS lookup delay that you experience. Then, either complain to your provider or to the vendor of your router. But people like work-arounds and hacks instead of going the direct route. Your handling of some obscure name server addresses is such one. HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org pgp5B5xzs3yDw.pgp Description: PGP signature
resolv.conf changing at boot
After recent upgrades in etch, I found my Firefox, Thunderbird, etc. waiting long periods for apparently DNS lookup (10-20 seconds every time). This is happening on two different computers which were upgraded. I find that my original entries of two nameservers in my resolv.conf file are being wiped out every time I boot. I have a router (D-Link DI-604) and several computers on my LAN. The router is 192.168.0.1. That is the address the resolv.conf file is being changed to for nameserver on bootup. By restoring (editing) the resolv.conf file to the proper nameservers of 214.134.xxx.yyy and 214.134.xxx.zzz. then everything works fine (no significant delay for DNS lookup)...until next time I reboot and they're back to 192.168.0.1 in resolv.conf. (and the 214.134... entries missing). Can anyone point me to where/what is happening here? Maybe I have a misunderstanding of wherein the problem lies. The DI-604 router shows the 214.134... nameservers correctly when I look at it. These are nameservers provided by my ISP. I have not changed anything recently that I could imagine would affect this. (I do not have "resolvconf" installed -- as mentioned in some past messages on this list.) Thanks, Don -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
