Name servers scenario

ISPmanager 5 + 2 DNSmanager as slave name servers

This is standard configuration. The server running ISPmanager is master, two servers running DNSmanager are slave. The first DNSmanager server has IP address 1.1.1.1, where ns1.domain.com will be located. The second DNSmanager server will have IP address 2.2.2.2 and ns2.domain.com. Mind that some registrars require that IP addresses of the two NSs belong to different C class networks.

  • In each DNSmanager create a user.

Dnsuser.png

  • В ISPmanager --- Domain names --- The NS icon --- The Add icon --- specify access details ro each DNSmanager: IP address, username and password created on the first step (Manage external name servers).

Dnsdomain.png

  • Integration is set up. In order to specify NSs for the registar, they should be accessible from the IP addresses to which they are assigned.

Create domain.com in ISPmanager --- Domain name. Records for domain.com shold look like as follows:

Dns3.png

1.1.1.1 and 2.2.2.2 - DNSmanager IP addresses that will be assigned to our ns1.domain.com and ns2.domain.com

3.3.3.3 - master IP address (ISPmanager).

Update data on both DNSmanager servers. Go to ISPmanager --- Domain names --- select domain.com --- click the Update icon. Execute the dig. Со slave 1.1.1.1 command to make sure everything is configured correctly.

dig domain.com @1.1.1.1

; <<>> DiG 9.8.1-P1 <<>> domain.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9480
;; 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       3.3.3.3

;; AUTHORITY SECTION:
domain.com.             3600    IN      NS      ns1.domain.com.
domain.com.             3600    IN      NS      ns2.domain.com.

;; ADDITIONAL SECTION:
ns1.domain.com.         3600    IN      A       1.1.1.1
ns2.domain.com.         3600    IN      A       2.2.2.2

The same result should be sent from slave 2.2.2.2 .

  • Now you can configure default domain names. Go to ISPmanager --- Domain names --- the Settings icon. Specify Name servers: ns1.domain.com. ns2.domain.com. (you may not use the dots at the end).

Dnsdefault.png

  • For the domain.com domain's registrar specify the name servers with IP addresses:
ns1.domain.com/1.1.1.1
ns2.domain.com/2.2.2.2
  • Once domain.com is successfully delegated on names servers ns1.domain.com and ns2.domain.com (updating DNS cache may take 24-48 hours), you may use them for registration and delegation of new domains.

Advantages of this scenario

Theoretically, name servers should locate on different physical servers that are located in different places. This will provide 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.

Disadvantages of this scenario

You must have two additional servers (virtual machines) for slave, that should locate at different places.

Due to failures, the information will update only on one slave. If the information differs on both slave servers, sites won't work properly.

ISPmanager 5 as master + DNSmanager as slave

In this case ISPmanager is used as master, and DNSmanager as slave. ISPmanager is installed on the server with IP 1.1.1.1. DNSmanager has IP address 2.2.2.2.

  • Create a user in DNSmanager.

Dnsuser2.png

  • ISPmanager --- Domain names --- click the NS icon --- the Add icon --- specify the DNSmanager access details: IP address, username ans password that were created on the first step (Manage external name servers).

Dnsdomain.png

  • Create the domain domain.com in ISPmanager

Update the data on DNSmanager. Go toISPmanager --- Domain names --- select domain.com --- click the Update icon.

Execute the dig command to check

dig domain.com @2.2.2.2

; <<>> DiG 9.8.1-P1 <<>> domain.com @2.2.2.2
;; 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       1.1.1.1

;; 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       1.1.1.1
ns2.domain.com.         3600    IN      A       2.2.2.2
  • Configure creation of default domain names. Go to ISPmanager --- Domain names --- the Settings icon. Specify Name servers: ns1.domain.com. ns2.domain.com. (you may not use dots at the end).

Dnsdefault.png

  • For the domain.com domain's register specify the servers with their IP addresses:
ns1.domain.com/1.1.1.1
ns2.domain.com/2.2.2.2
  • Once the domain domain.com is sucessully delegated on the name servers ns1.domain.com and ns2.domain.com (updating DNS cache may take 24-48 hours), you can use them for registration and delegation of new domain names.

Advantages of this scenario

You do not need to use several slave servers.

Disvantages of this scenario

You must have a powerfull master server that will be able to process both requests and name servers. In case of 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.

One ISPmanager 5 manages name servsrs

ISPmanager is used both as master and slave. For name servers you will need two IP addresses, some registrars require IP addresses belong to different C class networks. , причем некоторые регистраторы требуют, чтобы IP адреса были в разных сетях класса C. На практике это один основной адрес сервера, пусть будет 1.1.1.1, и один дополнительный - 2.2.2.2.

he first DNSmanager server has IP address 1.1.1.1, where ns1.domain.com will be located. The second DNSmanager server will have IP address 2.2.2.2 and ns2.domain.com. please mind that some registrars require that IP addresses of the two NSs belong to different C class networks.

  • Create domain.com in ISPmanager

Make sure you put dots in the NS records. The dot means that you don't need to add the main domain to the record.

  • Configure creation of default domain names. Go to ISPmanager --- Domain names --- the Settings icon. Specify Name servers: ns1.domain.com. ns2.domain.com. (you must use the dot at the end)

Dnsdefault.png

  • Execute the dig command to make sure everything is configured correctly.

Со slave 1.1.1.1

dig domain.com @1.1.1.1

; <<>> DiG 9.8.1-P1 <<>> domain.com @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9480
;; 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       1.1.1.1

;; AUTHORITY SECTION:
domain.com.             3600    IN      NS      ns1.domain.com.
domain.com.             3600    IN      NS      ns2.domain.com.

;; ADDITIONAL SECTION:
ns1.domain.com.         3600    IN      A       1.1.1.1
ns2.domain.com.         3600    IN      A       2.2.2.2

The same result should be sent from slave slave 2.2.2.2 .

  • For the domain.com domain's registrar specify the name servers with IP addresses:
ns1.domain.com/1.1.1.1
ns2.domain.com/2.2.2.2
  • Once domain.com is successfully delegated on names servers ns1.domain.com and ns2.domain.com (updating DNS cache may take 24-48 hours), you may use them for registration and delegation of new domains.

Advantages of this scenario

You do not need to use several slave servers.

Do not need to add records on the DNS records.

Disadvantages of this scenario

The service responsible for DNS may fail. In this case all the main services will continue running, but users won't be able to acess them as their domains do not work.

You must have a powerfull master server that will be able to process requests and name servers. in case of high load on master servers, sites may open more slowly, as DNS requests will be processes for a long time.

 

Was this answer helpful?

 Print this Article

Also Read

Plug-in management

A plug-in is an add-on for a program that adds a specific feature or service to it. For...

Administrators (ISPmanager)

An Administrator is a special user type which can manage the server with the same...

Updating server software

ISPmanager 5 enables to update software products installed on Debian, CentOS, FreeBSD. Complete...

ISPmanager installation guide

Installation from system repository ISPsystem software products 5.15.0 and later can be...

Exim configuration file

Exim configuration file in details Following is an example of the Exim configuration file on...