Named deleting interface at random times

[Kevin Darcy]

If you simply want to disable dynamic interface-addition and -deletion in BIND,
then you can specify "interface-interval 0" in your options. Just make sure the
interface exists whenever you start/restart named, otherwise it won't listen on
it.

If, on the other hand, you want to get to the bottom of why the interface is
constantly being deleted, then look more closely at what your OS is doing.
named is just reacting to the information it's getting back from your
OS through the standard network-interface-related API (namely, a SIOCGIFCONF
ioctl()). You could probably run "ifconfig" periodically -- with a
"-a" argument if it's available -- to confirm the same results that named is
seeing, or write your own little wrapper around ioctl(..., SIOCGIFCONF, ...).
Seems like you have an interface that's phasing in and out of existence for
some reason.


- Kevin

Nik Okuntseff wrote:

> Thanks for you help, Jim.
>
> A little bit more details on the problem. I have found 3 instances of the
> "deleting interface" in one of the log files. Here they are:
>
> Aug 14 10:01:37 ajhe20j4y335f named[861]: XX
> /165.224.216.254/www.wrconsulting.com/A/IN
> Aug 14 10:10:00 ajhe20j4y335f CROND[8196]: (root) CMD (   /sbin/rmmod -as)
> Aug 14 10:10:28 ajhe20j4y335f named[861]: Cleaned cache of 0 RRsets
> Aug 14 10:10:28 ajhe20j4y335f named[861]: deleting interface
> [64.180.21.66].53
>
> Aug 16 13:58:34 ajhe20j4y335f named[923]: XX
> /213.221.9.5/www.wrconsulting.com/A/IN
> Aug 16 14:00:00 ajhe20j4y335f CROND[2005]: (root) CMD (   /sbin/rmmod -as)
> Aug 16 14:01:00 ajhe20j4y335f CROND[2007]: (root) CMD (run-parts
> /etc/cron.hourly)
> Aug 16 14:06:32 ajhe20j4y335f rhnsd[2008]: running program
> /usr/sbin/rhn_check
> Aug 16 14:06:35 ajhe20j4y335f rhnsd[855]: command returned: ERROR: unable to
> read system id.
> Aug 16 14:10:00 ajhe20j4y335f CROND[2010]: (root) CMD (   /sbin/rmmod -as)
> Aug 16 14:20:00 ajhe20j4y335f CROND[2013]: (root) CMD (   /sbin/rmmod -as)
> Aug 16 14:22:51 ajhe20j4y335f named[923]: Cleaned cache of 0 RRsets
> Aug 16 14:22:51 ajhe20j4y335f named[923]: deleting interface
> [64.180.21.66].53
>
> Aug 17 16:29:54 ajhe20j4y335f named[860]: XX
> /62.104.218.72/www.wrconsulting.com/A/IN
> Aug 17 16:30:00 ajhe20j4y335f CROND[1457]: (root) CMD (   /sbin/rmmod -as)
> Aug 17 16:37:39 ajhe20j4y335f rhnsd[1458]: running program
> /usr/sbin/rhn_check
> Aug 17 16:37:41 ajhe20j4y335f rhnsd[842]: command returned: ERROR: unable to
> read system id.
> Aug 17 16:40:00 ajhe20j4y335f CROND[1460]: (root) CMD (   /sbin/rmmod -as)
> Aug 17 16:44:59 ajhe20j4y335f named[860]: Cleaned cache of 0 RRsets
> Aug 17 16:44:59 ajhe20j4y335f named[860]: deleting interface
> [64.180.21.66].53
>
> I have included at least one successful external query in each case
> indicating that it was working some time before "deleting interface".
>
> If I lose network connectivity before named deletes the interface why there
> are no entries in logs (something like failed to update the lease on
> eth0...).  May be the system can't log this for some reason because it was
> broken into in the past... Is there a way to check whether the system logs
> everything it is supposed to?
>
> Any help is greatly appreciated.
>
> Cheers,
>
> Nik
>
> -----Original Message-----
> From: Jim Reid [mailto:jim at rfc1035.com]
> Sent: Monday, August 20, 2001 1:16 AM
> To: niko at wrconsulting.com
> Cc: comp-protocols-dns-bind at moderators.isc.org
> Subject: Re: Named deleting interface at random times
>
> >>>>> "Nik" == Nik Okuntseff <niko at wrconsulting.com> writes:
>
>     Nik> I am having a strange problem.
>
>     Nik> In /var/log/messages I see entries like
>
>     Nik> named[860]: Cleaned cache of 0 RRsets named[860]: deleting
> interface [IP_ADDRESS_HERE].53
>
> Don't hide or mangle log messages (or snippets of config files).
>
> The name server checks the status of the system's network interfaces
> every cleaning-interval minutes. By default this is done once an hour.
> If the server finds a new network interface has been enabled, it will
> try set up a listener socket for incoming queries on that interface.
> Similarly if the server finds that an interface has gone away, it
> deletes that interface from the ones it listens on.