Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
up vote 4 down vote accepted

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
share|improve this answer

BIND will write startup errors to syslog.

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

share|improve this answer

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

share|improve this answer

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
share|improve this answer

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.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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