Re: NetworkManager vs Cacheing nameserver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2010-01-05 at 11:07 -0500, Matthew Saltzman wrote:
> On Tue, 2010-01-05 at 15:24 +0000, Patrick O'Callaghan wrote: 
> > On Tue, 2010-01-05 at 09:54 -0500, Tom Horsley wrote: 
> > > On Tue, 05 Jan 2010 14:30:02 +0000
> > > Patrick O'Callaghan wrote:
> > > 
> > > > That seems to be working for the moment, but there's an element of magic
> > > > in it that makes me nervous. The default named.conf file is set up as a
> > > > simple cacheing nameserver for local queries, but where does named do
> > > > its recursive lookups if not from the DHCP service?
> > > 
> > > If you want to add the name servers specified by DHCP to lookups,
> > > then you don't want your resolv.conf file to be unmodified,
> > > instead you want NM to modify it "correctly", like by
> > > leaving 127.0.0.1 as one nameserver and adding additional
> > > nameservers. <sarcasm> How to get NM to do this is no doubt described
> > > fully in the extensive NetworkManager documentation. </sarcasm>
> > 
> > Quite.
> > 
> > > With bind configured as a cacheing server, there is usually
> > > a "forwarders" section in named.conf that points to the DNS
> > > servers it should look at.
> > 
> > There isn't. This is the default, unmodified named.conf.
> > 
> > I've now rebooted to check, and /etc/resolv.conf has again been
> > overwritten by NM, despite the PEERDNS=no line in the ifcfg file, i.e.
> > it has reverted to what it was. NM seems to be calling dhclient with its
> > own private config file, the whereabouts of which are non-obvious.
> 
> You might want to take this question to the NetworkManager list at
> gnome.org.  The developers hang out there--if it's a bug, they'd
> probably like to know about it.  If it's by design, they can probably
> explain it.

I may do that. However I'm still not able to say it's a bug. I can't
believe that no-one has ever tried to do this before as it's so obvious,
so I was hoping simply to learn the Right Way To Do It.

poc

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux