This question already has an answer here:

Feb 24 15:54:34 ns1 named[20308]: all zones loaded
Feb 24 15:54:34 ns1 named[20308]: running
Feb 24 15:54:34 ns1 systemd[1]: PID file /var/run/named/named.pid not readable (yet?) after start.
Feb 24 15:56:03 ns1 systemd[1]: named.service operation timed out. Terminating.
Feb 24 15:56:03 ns1 named[20308]: shutting down
Feb 24 15:56:03 ns1 named[20308]: stopping command channel on
Feb 24 15:56:03 ns1 named[20308]: exiting

I have tried renaming to named.service as mentioned here: named does't start when using systemctl

marked as duplicate by slm Jul 23 '15 at 7:04

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • what does ls -l /var/run/named/ show – X Tian Feb 24 '14 at 16:33
  • @XTian # ls -l /var/run/named/ total 4 -rw------- 1 named named 102 Feb 24 15:25 session.key – SavageCore Feb 24 '14 at 16:36

This looks to be a bug. See this ticket titled: Bug 984764 - bind-chroot-9.9.3-3.P1.fc19.x86_64 failed to start.

The fix is to add this to your named.conf file:

pid-file      "/var/run/named/named.pid";

There are additional tips in the ticket with respect to getting your system back into a state where you can successfully run Bind afterwards.

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