Does named log startup errors if so what is the default path?

The Wikipedia page for BIND speak of a configuration file verification tool - does anyone know of this?


most daemons log to /var/log/daemon. errors sometimes are also logged to /var/log/messages. you can check this by looking at the syslog configuration file /etc/syslog.conf.

the configcheck util for BIND is named-checkconf. it's a bit tricky, if you run your BIND chrooted.

first start with:


to check the zone files also:

named-checkconf -z

in a chrooted environment try this:

named-checkconf -t /var/named -z

BIND will write startup errors to syslog.

Hence the logs will appear wherever your syslog.conf says they should go (typically /var/log/messages).


I'd look in the default system log. On my system it's /var/log/messages but I bet that's distribution-dependent.


There are two verification tools, one for the configuration file itself, and one for zone files. In Debian, they are called:

  • named-checkconf
  • named-checkzone

There is a number of DNS validation tools. NSLint is one such tool, which checks zone files on disk.

I've used DNS Sleuth in the past, which does DNS queries to check your setup. You can use the website or download a copy to use locally.


There's also a configurable log file. By default it can be found at /etc/named/data/named.run

You can change it's path and control the severity of the messages at /etc/named.conf at this part of the file:

  channel default_debug {
    file "data/named.run";
    severity dynamic;

With the default settings, the content of the named.run file would be similar to what is printed at the /var/log/messages.

  • Please don't post pictures of text. Mar 8 at 8:38
  • all fixed, chief.
    – Ramon Dias
    Mar 8 at 13:57
  • You'll see, you will get plenty of upvotes :) Mar 8 at 15:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.