I would like to use dnsmasq to cache nameserver query results, and I have set dhcp to prepend the 127.0.0.1 name-server to the list of nameservers. dnsmasq would then automatically exclude the localhost as a name server and use all the others from the list provided by dhcp. But it was too nice to be true, because NetworkManager was there, ready to mess up anything I try to do, including the list of name servers that dhclient puts in /etc/resolv.conf. Is there really no way to convince that idiotic piece of software that it suffered too much brain damage in order for it to manage even a simple eth0 interface, and that dhclient can properly take care of the resolver configuration by itself ? Or do I have to turn it off entirely ? Is there a better way to have dhclient write the list of DNS servers, that dnsmasq could then use ? Thank you, Timothy Madden
On 05/10/2012 06:55 AM, Timothy Madden wrote:> I would like to use dnsmasq to cache nameserver query results, and I > have set dhcp to prepend the 127.0.0.1 name-server to the list of > nameservers. dnsmasq would then automatically exclude the localhost as a > name server and use all the others from the list provided by dhcp. > > But it was too nice to be true, because NetworkManager was there, ready > to mess up anything I try to do, including the list of name servers that > dhclient puts in /etc/resolv.conf. > > Is there really no way to convince that idiotic piece of software that > it suffered too much brain damage in order for it to manage even a > simple eth0 interface, and that dhclient can properly take care of the > resolver configuration by itself ? > > Or do I have to turn it off entirely ? > > Is there a better way to have dhclient write the list of DNS servers, > that dnsmasq could then use ? > > Thank you, > Timothy Madden > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >I turned if off long ago. I don't see any need for it unless maybe you have a laptop that you are carrying around to a lot of different environments. My $.02 -- Stephen Clark *NetWolves* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark at netwolves.com http://www.netwolves.com
On 10/05/12 20:55, Timothy Madden wrote:> > I would like to use dnsmasq to cache nameserver query results, and I > have set dhcp to prepend the 127.0.0.1 name-server to the list of > nameservers. dnsmasq would then automatically exclude the localhost as a > name server and use all the others from the list provided by dhcp. > > But it was too nice to be true, because NetworkManager was there, ready > to mess up anything I try to do, including the list of name servers that > dhclient puts in /etc/resolv.conf. > > Is there really no way to convince that idiotic piece of software that > it suffered too much brain damage in order for it to manage even a > simple eth0 interface, and that dhclient can properly take care of the > resolver configuration by itself ? > > Or do I have to turn it off entirely ? > > Is there a better way to have dhclient write the list of DNS servers, > that dnsmasq could then use ?Have a look in /etc/NetworkManager/dispatcher.d/11-dhclient you might be able to figure out a tweak to put 127.0.0.1 back in. Kal -- Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty Ltd (w) +61 (0) 3 9008 5281 Suite 1415 401 Docklands Drive Docklands VIC 3008 Australia "All parts should go together without forcing. You must remember that the parts you are reassembling were disassembled by you. Therefore, if you can't get them together again, there must be a reason. By all means, do not use a hammer." -- IBM maintenance manual, 1925
On 10.05.2012 11:55, Timothy Madden wrote:> I would like to use dnsmasq to cache nameserver query results, and I > have set dhcp to prepend the 127.0.0.1 name-server to the list of > nameservers. dnsmasq would then automatically exclude the localhost > as a > name server and use all the others from the list provided by dhcp. > > But it was too nice to be true, because NetworkManager was there, > ready > to mess up anything I try to do, including the list of name servers > that > dhclient puts in /etc/resolv.conf. > > Is there really no way to convince that idiotic piece of software > that > it suffered too much brain damage in order for it to manage even a > simple eth0 interface, and that dhclient can properly take care of > the > resolver configuration by itself ? > > Or do I have to turn it off entirely ? > > Is there a better way to have dhclient write the list of DNS servers, > that dnsmasq could then use ? > > Thank you, > Timothy Madden > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centosI'm doind the same thing (running local cache) and NM works just fine. You should be setting NM to use the "DHCP (addresses only)" as in this image: http://img.nux.ro/4PsJ-dhcpnmlocaldns.png Put the upstream resolvers in some other file, e.g. /etc/nameservers and tell dnsmasq to get it's nameservers from there. Or just run a full fledge nameserver yourself and get rid of dnsmasq (I use pdns-recursor). HTH -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
On Friday, May 11, 2012 06:16:44 AM Timothy Madden wrote:> How can such software be part of CentOS _base_ distribution ?Upstream put it there; CentOS simply replicates upstream's behavior (bug for bug compatibility is one of the distribution's goals, after all). You would need to file a bugzilla with upstream to get the behavior changed. As dnsmasq is shipped upstream (I just verified with my own upstream EL6 machine), it should be in a usable condition as shipped.