• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

DNS Master/slave

D

Dimka

Guest
Hello There!

Need advance in master and slave DNS settings I have 2 servers and i want to setup them that way if one is timeout all queries will follow to another . I have a plesk 7.5 panel and it's default template is made only for a single server setup. I also have 2 NS addresses in deferent C class networks


here is the template

<domain>. NS ns.<domain>.
<domain>. A <ip>
<domain>. MX (10) mail.<domain>.
<ip> / 24 PTR <domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
ns.<domain>. A <ip>
webmail.<domain>. A <ip>

i assume this template should be remade like this

<domain>. NS ns1.<domain>.
<domain>. NS ns2.<domain>.
<domain>. A <ip>
<domain>. MX (10) mail.<domain>.
<ip> / 24 PTR <domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
ns1.<domain>. A 10.0.1.10
ns2.<domain>. A 10.0.2.10
webmail.<domain>. A <ip>

the same stuff on the slave server

Then add definition string into named.conf

zone "example.com" in{
type master;

and the slave sting to the slave server

will it work like this ?

or there is another way?

Thanks in advance
 
Assuming the Plesk server is the Master and the other is the slave, then what you propose sounds good and should work.

Don't forget to put the servers into the common acl list.

It is very nice to see someone actually setting up a separate 2nd DNS server, rather than trying to use a single Plesk box to be both primary and secondary (which defeats the purpose of having 2 name servers).
 
Originally posted by Dimka


<domain>. NS ns1.<domain>.
<domain>. NS ns2.<domain>.
<domain>. A <ip>
<domain>. MX (10) mail.<domain>.
<ip> / 24 PTR <domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
ns1.<domain>. A 10.0.1.10
ns2.<domain>. A 10.0.2.10
webmail.<domain>. A <ip>


I want to know the following:
<domain>. NS ns1.mydomain.tld.
<domain>. NS ns2.mydomain.tld.
..
..
..
ns1.mydomain.tld. A <mybox1-ip>
ns2.mydomain.tld. A <mybox2-ip>

according to my understanding, this should work too?

i dont want anyother domain hosted on my stem to be ns1.thatdomain.tld and ns2.thatdomain.tld
 
ChipMonk - I believe I understand your post and that should work fine.

You have 2 IPs on your box <mybox1-ip> and <mybox2-ip>.

As long as you have registered both name server names and pointed them to the proper IPs on your box (you do this at your registrar company), and you can then use those 2 entries for all the domains hosted on your server.
 
just one clarification

box1 and box2 are seperate boxes.

and ofcourse, name servers are already pointed to respective IP addresses.
 
Back
Top