• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Slave DNS setup not working...

XCore

New Pleskian
I'm trying to setup two slave DNS servers to use exclusively for all domains in my system.
I followed a combination of docs on the subject at:
http://devblog.plesk.com/2013/10/slave-dns-and-plesk/ (the link provided inside Plesk on the setup page)
http://docs.plesk.com/en-US/12.5/extensions-guide/setting-up-a-slave-dns-server/
http://download1.parallels.com/Ples...inistrator-guide/index.htm?fileName=72230.htm
I've added the two nameservers via the extension in the Plesk admin area, added the text as instructed to the '/etc/named.conf' on both, setup the nameservers at the registrar and pointed a domain to it.
Plesk "says" it's ok with a green check next to each nameserver.
I'v applied the dns template to all zones.
The pointed domain name nor the nameservers are found.
I've also set Plesk as a slave to see if it made a difference and it doesn't.
The only thing I did change from all the docs is the line in named:
Code:
inet * port 953 allow { 172.10.10.1; 127.0.0.1; } keys { "rndc-key"; "rndc-key-172.10.10.10"; };
to
Code:
inet * port 953 allow { 172.10.10.1; 127.0.0.1; } keys { "rndc-key-172.10.10.1"; };
because named would not start the way rndc-key is phrased in the first line.
"dig" seems to work when I use the local server IP but not if I use either of the assigned IPs.

Any help is greatly appreciated.

OF NOTE:
Plesk, NS1 and NS2 are all running in OpenVZ containers on CentOS 6.7 X86_64
Plesk 12.5, Bind 9.8.2

Thank you!

pleskslave.jpg
 
Back
Top