Why is named started, but not being used?

Neal Becker ndbecker2 at gmail.com
Mon Nov 19 02:07:40 UTC 2007


Jeffrey Ollie wrote:

> On 11/18/07, Neal Becker <ndbecker2 at gmail.com> wrote:
>> /sbin/chkconfig named --list
>> named           0:off   1:off   2:off   3:off   4:off   5:off   6:off
>>
>> named     2794  0.0  0.5 131440 10568 ?        Ssl  Nov16
>> 0:00 /usr/sbin/named -u named -D -t /var/named/chroot
>>
>> Well, someone started named!
>>
>> But I checked using wireshark.  Repeating the same query resulted in dns
>> packets being sent out - so it seems the local named isn't being used.
> 
> Check /etc/resolv.conf.  I've seen recently that NetworkManager or
> dhclient is writing the name servers received from the DHCP server
> into /etc/resolv.conf rather than 127.0.0.1 being in /etc/resolv.conf
> and using D-Bus to tell named about the local name servers.
> 

Yeah, seems NM is writing resolv.conf, but I believe NM is also starting
named (as you see, chkconfig reports that named is not set to start)
---/etc/resolv.conf --
# generated by NetworkManager, do not edit!



nameserver 192.168.1.1







More information about the fedora-test-list mailing list