There are upcoming maintenance events which may impact our services. Learn more

My Plesk slave DNS server isn't creating zone files Print

  • 3

As with most things web-server related, Plesk users have a great advantage when configuring a slave DNS server to work with Plesk thanks to the Extension that manages it for you here. It even walks you through most of the setup process. However there are a few things that can prevent it from working when simply following the directions. Here are the solutions:

  1. If the master server takes a long time and never reaches the slave with a timeout, make sure the firewall on the master server allows port 953 outgoing (Egress)
  2. Be sure to disable recursion on the slave server by editing /etc/named.conf and setting `recursion no;` under the options { } config
  3. Configure named to listen on the server IP and not just localhost by adding it to the "listen-on port 53" directive.
  4. Configure named to allow external queries, by changing "allow-query" to "any;" rather than just "localhost;"
  5. Finally, be sure to set permissions correctly with this command: `chown named:named /var/named/`. By default its ownership is root:named which will prevent zone files from being created. Source
For those MOVING their master server to a new IP, you'll probably start seeing this on your slave even after updating named.conf with the new master IP: "failed while receiving responses: REFUSED". You may also notice that the named log entries are still showing the master server as the old server IP.

To fix this, look in /var/named/ for a file that ends in .nzf. In our case it was "3bf305731dd26307.nzf" but yours is bound to be different. This file contains the cached master server for each zone. Find and replace the old IP with the new, then restart named and you should be all set!

Was this answer helpful?

← Back