Name servers configuration

From ISPWiki
Jump to: navigation, search

There are several scenarious of how you can use our software prodcut for configuring name servers.

ISPmanager 5 Lite + 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 82.146.54.223, where ns1.domain.com will be located. The second DNSmanager server will have IP address 92.63.100.32 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. Go to Account management --- Users and press Add

Scen Real DNS En 1.png

Then fill username, password, DNS namespace and press OK.

Scen Real DNS En 2.png

In ISPmanager --- Domain names --- The NS icon

Scen Real DNS En 3.png

Then press the Add icon

Scen Real DNS En 4.png

Specify access details to each DNSmanager: URL of the control panel, username and password created on the first step and press OK.

Scen Real DNS En 5.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 --- Domains --- Domain names. Then focus the created domain and click Records. Records for domain.com should look like as follows:

Scen Real DNS En 6.png

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

212.109.220.118 - master IP address (ISPmanager).

Update data on both DNSmanager servers. Go to ISPmanager --- Domain names --- select domain.com --- click the Update icon.

Scen Real DNS En 12.png

Execute the "dig" command with slave 82.146.54.223 to make sure everything is configured correctly.

dig domain.com @82.146.54.223

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

;; 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       82.146.54.223
ns2.domain.com.         3600    IN      A       92.63.100.32

The same result should be sent from slave 92.63.100.32 .

Now you can configure default domain names. Go to ISPmanager --- Domain names --- the Settings icon.

Scen Real DNS En 7.png

Specify Name servers: ns1.domain.com. ns2.domain.com. (you must use the dot at the end).

Scen Real DNS En 8.png

For the domain.com domain's registrar specify the name servers with IP addresses:

ns1.domain.com/82.146.54.223
ns2.domain.com/92.63.100.32

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 Lite + 2 DNSmanager as slave name servers

After adding users on both DNSmanager servers go to ISPmanager Business control panel to Integration --- External name servers and press "Add" icon.

Scen Real DNS En 13.png

Specify access details ro each DNSmanager: URL of the control panel, username and password and press OK.

Scen Real DNS En 14.png

After specifying, further settings are same to ISPmanager Lite. Advantages and disadvantages of the scheme are same to ISPmanager Lite too.

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 212.109.220.118. DNSmanager has IP address 92.63.100.32.

Create a user in DNSmanager. Go to Account management --- Users and press Add

Scen Real DNS En 1.png

Then fill username, password, DNS namespace and press OK.

Scen Real DNS En 9.png

In ISPmanager --- Domain names --- click the NS icon

Scen Real DNS En 3.png

Then press the Add icon

Scen Real DNS En 4.png

Enter access details to DNSmanager: URL of the control panel, username and password that were created on the first step.

Scen Real DNS En 10.png

Create the domain domain.com in ISPmanager --- Domain names. Records for domain.com should look like something like this

Scen Real DNS En 11.png

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

Scen Real DNS En 12.png

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

dig domain.com @92.63.100.32

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

;; 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       212.109.220.118
ns2.domain.com.         3600    IN      A       92.63.100.32

Configure creation of default domain names. Go to ISPmanager --- Domain names --- the Settings icon.

Scen Real DNS En 7.png

Specify Name servers: ns1.domain.com. ns2.domain.com. (you must use the dot at the end).

Scen Real DNS En 8.png

For the domain.com domain's register specify the servers with their IP addresses:

ns1.domain.com/212.109.220.118
ns2.domain.com/92.63.100.32

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.

Only ISPmanager 5 manages name servers

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. Foe example, the first IP-address is 212.109.220.118, the second is 82.146.54.223.

For ISPmanager Business you can use DNS-servers on a nodes of cluster. To realize that you should assign a "Name server (secondary)" role to one or more nodes.

There are settings for ISPmanager Lite below.

Create domain.com in ISPmanager --- Domain names.

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.

Scen Real DNS En 7.png

Specify Name servers: ns1.domain.com. ns2.domain.com. (you must use the dot at the end)

Scen Real DNS En 8.png

Execute the "dig" command with slave 212.109.220.118 to make sure everything is configured correctly.

dig domain.com @212.109.220.118

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

;; 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       212.109.220.118
ns2.domain.com.         3600    IN      A       82.146.54.223

The same result should be sent from slave slave 82.146.54.223 .

For the domain.com domain's registrar specify the name servers with IP addresses:

ns1.domain.com/212.109.220.118
ns2.domain.com/82.146.54.223

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.