On Sun, 27 Dec 2009, Denis Heidtmann wrote: > Date: Sun, 27 Dec 2009 14:36:31 -0800 > From: Denis Heidtmann <[email protected]> > Reply-To: "General Linux/UNIX discussion and help; civil and on-topic" > <[email protected]> > To: "General Linux/UNIX discussion and help, civil and on-topic" > <[email protected]> > Subject: Re: [PLUG] resolve.conf file > > Thanks for all the information and advice. Unfortunately, Carlos' > comment about dsl modems applies in my situation: an Actiontec modem > from Qwest. So attempts to change its dhcp behavior will not bear > fruit. My use of resolvconf is a sensible solution to a > less-than-perfect state of affairs. Mike's suggestions seem a better > solution, and I will study those, but until then, resolvconf is my > ticket to functioning. (To settle the question of what this modem > can/cannot do, from Actiontec I received: "The PK5000 itself is NOT a > DNS server or redirection device. There is no programming in fact to > do a DNS redirection internally. It cannot do that at all.") > > With regard to the /etc/resolv.conf file, it is a link to > etc/resolvconf/run/resolv.conf, which is maintained by resolvconf. > > Now, to get to the unanswered questions in my post: > > Why does the presence of "nameserver 192.168.0.1" in resolv.conf not > break dns searches occasionally? > > Should I attempt to clean up this file? If I should, how might that > be done? Since a dhcp client in not now running on my machine, the > bogus entries, once gone, should stay gone. > > -Denis
Easy pal, no one is trying to steer you wrong. It can feel like that if you remain fixated on a solution that isn't necessarily the best. The best solution: get off qwest, go with a cable provider that uses a pass-through modem, and use your own router/firewall (a $30 hardware job or a linux box). But to stick within the confines of your situation: It is quite possible to do DHCP without rewriting the resolv.conf file. Gentoo allows a line like the following to be placed into /etc/conf.d/net: dhcp_eth0="nodns" This produces the required behavior of leaving resolv.conf alone. It does so by adding the appropriate command-line option to the DHCP client. I use pump. It has this option: -d --no-dns Don't update DNS resolver configuration Every distro has its own way of configuring custom options for startup services like DHCP. Which distro are you using? Once we know that, we can figure out where the -d must go. Once you achieve this, you can write the resolv.conf file any way you like, and it will remain so. Or, if you don't want to turn DHCP back on, simply edit resolv.conf right now in an editor, and it will stay put as long as you aren't running any services that can change it, like resolvconf. Simply turn resolvconf off. It has performed its duty of sniffing out the qwest nameservers for you; its work is done. It doesn't need to redo this on every boot. Carlos _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
