Ispmanager is used a master name server. You can use DNSmanager as slave name servers. There are several ways to set up name servers using Ispmanager software.
.1Ispmanager + 2 DNSmanager.
.2Ispmanager + DNSmanager.
.3Ispmanager.
Ispmanager + 2 DNSmanager
Better security of the DNS system and ensure that your domain names are always accessible.The risk that two servers in different parts of the globe are not accessible at the same time is considerably low.
You must have two additional servers that should locate on different physical servers that are located in different places. Due to failures, the information will update only on one slave server. If the information differs on both slave servers, sites won't work properly.
You do not need to use several slave servers.
You must have a powerful master server that will be able to process both requests and name servers. In case of a high load on master servers, sites may open more slowly, as DNS requests will be processed for a longer time. The first scenario is more fault-tolerant.
You do not need to use several slave servers.
The service responsible for DNS may fail. In this case, all the main services will continue running, but users won't be able to access them as their domains do not work.You must have a powerful master server that will be able to process requests and name servers. in case of a high load on master servers, sites may open more slowly, as DNS requests will be processed for a long time. Perform the following steps to configure the name servers:
.2 Make sure that the name servers respond from the IP-addresses on which they are located:
.bIn thechoose and check the NS-records of the domain. Check that the IP-addresses of both DNSmanager are specified in the field for the NS-records. For more information please refer to the article Resource records . .cUpdate the data on the slave servers: .
.dExecute the following command to check the information about the name servers:
dig domain.com @<IP-address of the slave DNS>
.eThe response should look like this:; <<>> DiG 9.8.1-P1 <<>> domain.com @<IP-address of the slave DNS>;; global options: +cmd;; Got answer:;; ->>HEADER<<-
opcode: QUERY, status: NOERROR, id: 46010 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;domain.com. IN A ;; ANSWER SECTION: domain.com. 3600 IN A <ISPmanager IP-address> ;; AUTHORITY SECTION: domain.com. 3600 IN NS ns2.domain.com. domain.com. 3600 IN NS ns1.domain.com. ;; ADDITIONAL SECTION: ns1.domain.com. 3600 IN A <DNSmanager 1 IP-address> ns2.domain.com. 3600 IN A <DNSmanager 2 IP-address>
.3Specify the name server with the IP-address on the domain registrar side: ns1.domain.com/ <DNSmanager 1 IP-address> ns2.domain.com/ <DNSmanager 2 IP-address>Delegating the domain to the name server can take up to 24-48 hours. Once completed, you can use them for registration and delegation of new domain names.
Perform the following steps to configure the name servers:
.2 Make sure that the name servers respond from the IP-addresses on which they are located:
.bIn thechoose and check the NS-records of the domain. Check that the IP-addresses of both DNSmanager are specified in the field for NS-records. The column for the NS records must contain ispmanager and DNSmanager IP addresses. For more information please refer to the article Resource records . .cUpdate the data on the slave servers:
.dExecute the following command to check the information about the name servers:
dig domain.com @<IP-address of the slave DNS>
.eThe response should look like this:; <<>> DiG 9.8.1-P1 <<>> domain.com @<IP-address of the slave DNS>;; global options: +cmd;; Got answer:;; ->>HEADER<<-
opcode: QUERY, status: NOERROR, id: 46010 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;domain.com. IN A ;; ANSWER SECTION: domain.com. 3600 IN A <ISPmanager IP-address> ;; AUTHORITY SECTION: domain.com. 3600 IN NS ns2.domain.com. domain.com. 3600 IN NS ns1.domain.com. ;; ADDITIONAL SECTION: ns1.domain.com. 3600 IN A <ISPmanager IP-address> ns2.domain.com. 3600 IN A <DNSmanager IP-address>
.3Specify the name server with the IP-address on the domain registrar side: ns1.domain.com/ <ISPmanager IP-address> ns2.domain.com/ <DNSmanager IP-address>Delegating the domain to the name server can take up to 24-48 hours. Once completed, you can use them for registration and delegation of new domain names.
Perform the following steps to configure the name servers:
.1Make sure the server with Ispmanager has at least 2 IP-addresses.
.2Check that the name servers respond from the IP-addresses on which they are located:
.bIn the choose → and check the NS-records of the domain. The column for NS records should contain the domain names corresponding to the primary and secondary ispmanager IP addresses. For more information please refer to the article Resource records . .cExecute the following command to check the information about the name servers:
dig domain.com @<ispmanager IP-address>
.dThe response should look like this:; <<>> DiG 9.8.1-P1 <<>> domain.com @<ispmanager IP-address>;; global options: +cmd;; Got answer:;; ->>HEADER<<-
opcode: QUERY, status: NOERROR, id: 46010 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;domain.com. IN A ;; ANSWER SECTION: domain.com. 3600 IN A <ISPmanager primary IP-address> ;; AUTHORITY SECTION: domain.com. 3600 IN NS ns2.domain.com. domain.com. 3600 IN NS ns1.domain.com. ;; ADDITIONAL SECTION: ns1.domain.com. 3600 IN A <ISPmanager additional IP-address> ns2.domain.com. 3600 IN A <ISPmanager primary IP-address>
.3Specify the name server with the IP-address on the domain registrar side: ns1.domain.com/ <ispmanager additional IP-address> ns2.domain.com/ <ispmanager primary IP-address>Delegating the domain to the name server can take up to 24-48 hours. Once completed, you can use them for registration and delegation of new domain names