BIND not talking to syslog daemon

[Todd Snyder]

Good day,

I've run into a bit of an oddity, and I'm hoping someone might have an
idea.

I have a nameserver running BIND 9.3.5-p1 that doesn't want to log to
the syslog daemon.  I have 2 identically configured servers, one of them
works, one doesn't.

My logging configuration looks like:

        category default                { my_default; default_syslog;
default_debug; };

I don't have a channel defined for "default_syslog" which means the
daemon should be using the built-in channel, as I understand it.

While logs are seen in "my_default", they are just not showing up in
syslog.  We have restarted syslog-ng and verified the configuration,
it's the same as the working unit.

Syslog works otherwise on the box from other daemons, just not named.
Our thought is that for some reason the named daemon can't connect to
syslog, or gave up trying.

We cannot reload named on the box right now, so I am looking to see if
anyone has suggestions about what might be causing this, and/or ways to
resolve it without restarting the named daemon.

Thanks in advance,

Todd.





---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.