How To Run Your Own Name Servers With ISPConfig And GoDaddy - Page 3

Want to support HowtoForge? Become a subscriber!
 
Submitted by falko (Contact Author) (Forums) on Tue, 2006-06-13 22:43. ::

6 Create DNS Records For ifwolfpack.com On ns2.erikturk.com

(The steps from this chapter have to be done on ISPConfig server #2/ns2.erikturk.com.)

I will refer to ISPConfig server #2 as ns2.erikturk.com from now on.

ns2.erikturk.com must hold the same DNS records as ns1.erikturk.com so if ns1.erikturk.com goes down for some reason, ns2.erikturk.com can take over. Now it would be stupid to create the same records again on ns2.erikturk.com. To avoid this work, we can simply transfer the ifwolfpack.com zone from ns1.erikturk.com to ns2.erikturk.com. This is called a zone transfer.

To do this, go to the DNS Manager in ISPConfig on ns2.erikturk.com and click on New Slave (remember, ns2.erikturk.com is our secondary name server).

Enter ifwolfpack.com as Title and Domain and specify ns1.erikturk.com's IP address (64.25.171.8) as DNS-Master IP:

That's all you have to do. The ifwolfpack.com zone will now be transferred from ns1.erikturk.com to ns2.erikturk.com automatically.


7 Do Some Testing

We have not specified ns1.erikturk.com and ns2.erikturk.com as the authoritative name servers for ifwolfpack.com in the GoDaddy interface yet. Nevertheless we can do some tests now to see that ns1.erikturk.com and ns2.erikturk.com resolve ifwolfpack.com correctly. You can do this on any of your Linux systems with the dig command. First we ask ns1.erikturk.com:

dig @ns1.erikturk.com any ifwolfpack.com

;  DiG 9.2.4  @ns1.erikturk.com any ifwolfpack.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31627
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;ifwolfpack.com. IN ANY

;; ANSWER SECTION:
ifwolfpack.com. 86400 IN SOA ns1.erikturk.com. hostmaster.erikturk.com. 2006060705 28800 7200 604800 86400
ifwolfpack.com. 86400 IN NS ns1.erikturk.com.
ifwolfpack.com. 86400 IN NS ns2.erikturk.com.
ifwolfpack.com. 86400 IN MX 10 mail.ifwolfpack.com.
ifwolfpack.com. 86400 IN A 64.25.171.8

;; ADDITIONAL SECTION:
ns2.erikturk.com. 172661 IN A 64.25.171.9
mail.ifwolfpack.com. 86400 IN A 64.25.171.8

;; Query time: 157 msec
;; SERVER: 64.25.171.8#53(ns1.erikturk.com)
;; WHEN: Wed Jun 7 18:43:12 2006
;; MSG SIZE rcvd: 193

dig @ns1.erikturk.com any www.ifwolfpack.com

;  DiG 9.2.4  @ns1.erikturk.com any www.ifwolfpack.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60393
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;www.ifwolfpack.com. IN ANY

;; ANSWER SECTION:
www.ifwolfpack.com. 86400 IN A 64.25.171.8

;; AUTHORITY SECTION:
ifwolfpack.com. 86400 IN NS ns1.erikturk.com.
ifwolfpack.com. 86400 IN NS ns2.erikturk.com.

;; ADDITIONAL SECTION:
ns2.erikturk.com. 172626 IN A 64.25.171.9

;; Query time: 149 msec
;; SERVER: 64.25.171.8#53(ns1.erikturk.com)
;; WHEN: Wed Jun 7 18:43:32 2006
;; MSG SIZE rcvd: 113

dig @ns1.erikturk.com any mail.ifwolfpack.com

;  DiG 9.2.4  @ns1.erikturk.com any mail.ifwolfpack.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45499
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;mail.ifwolfpack.com. IN ANY

;; ANSWER SECTION:
mail.ifwolfpack.com. 86400 IN A 64.25.171.8

;; AUTHORITY SECTION:
ifwolfpack.com. 86400 IN NS ns2.erikturk.com.
ifwolfpack.com. 86400 IN NS ns1.erikturk.com.

;; ADDITIONAL SECTION:
ns2.erikturk.com. 172606 IN A 64.25.171.9

;; Query time: 147 msec
;; SERVER: 64.25.171.8#53(ns1.erikturk.com)
;; WHEN: Wed Jun 7 18:43:44 2006
;; MSG SIZE rcvd: 114

The results look as expected. Now we check ns2.erikturk.com:

dig @ns2.erikturk.com any ifwolfpack.com

;  DiG 9.2.4  @ns2.erikturk.com any ifwolfpack.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19089
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;ifwolfpack.com. IN ANY

;; ANSWER SECTION:
ifwolfpack.com. 86400 IN SOA ns1.erikturk.com. hostmaster.erikturk.com. 2006060705 28800 7200 604800 86400
ifwolfpack.com. 86400 IN NS ns1.erikturk.com.
ifwolfpack.com. 86400 IN NS ns2.erikturk.com.
ifwolfpack.com. 86400 IN A 64.25.171.8
ifwolfpack.com. 86400 IN MX 10 mail.ifwolfpack.com.

;; ADDITIONAL SECTION:
ns2.erikturk.com. 172776 IN A 64.25.171.9
mail.ifwolfpack.com. 86400 IN A 64.25.171.8

;; Query time: 79 msec
;; SERVER: 64.25.171.9#53(ns2.erikturk.com)
;; WHEN: Wed Jun 7 19:02:22 2006
;; MSG SIZE rcvd: 193

dig @ns2.erikturk.com any www.ifwolfpack.com

;  DiG 9.2.4  @ns2.erikturk.com any www.ifwolfpack.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7173
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;www.ifwolfpack.com. IN ANY

;; ANSWER SECTION:
www.ifwolfpack.com. 86400 IN A 64.25.171.8

;; AUTHORITY SECTION:
ifwolfpack.com. 86400 IN NS ns2.erikturk.com.
ifwolfpack.com. 86400 IN NS ns1.erikturk.com.

;; ADDITIONAL SECTION:
ns2.erikturk.com. 172753 IN A 64.25.171.9

;; Query time: 76 msec
;; SERVER: 64.25.171.9#53(ns2.erikturk.com)
;; WHEN: Wed Jun 7 19:02:37 2006
;; MSG SIZE rcvd: 113

dig @ns2.erikturk.com any mail.ifwolfpack.com

;  DiG 9.2.4  @ns2.erikturk.com any mail.ifwolfpack.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58414
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;mail.ifwolfpack.com. IN ANY

;; ANSWER SECTION:
mail.ifwolfpack.com. 86400 IN A 64.25.171.8

;; AUTHORITY SECTION:
ifwolfpack.com. 86400 IN NS ns1.erikturk.com.
ifwolfpack.com. 86400 IN NS ns2.erikturk.com.

;; ADDITIONAL SECTION:
ns2.erikturk.com. 172733 IN A 64.25.171.9

;; Query time: 108 msec
;; SERVER: 64.25.171.9#53(ns2.erikturk.com)
;; WHEN: Wed Jun 7 19:02:49 2006
;; MSG SIZE rcvd: 114

Looks ok, too.


8 Change ifwolfpack.com's Authoritative Name Servers

(This step should always be done after you have created the appropriate DNS records on the new name servers! Some registries will complain if they do not find records for a domain on the new name servers.)

Now we must change the authoritative name servers in the GoDaddy interface. Up to now, GoDaddy's name servers are still responsible for ifwolfpack.com, and if a client asks for details about ifwolfpack.com, GoDaddy's name servers will answer. To change this, we check the checkbox in front of ifwolfpack.com in our domain list in the GoDaddy interface and click on Set Nameservers:

On the right, the Set Name Servers box loads. Mark Custom Name Servers and replace GoDaddy's name servers with ns1.erikturk.com (Name Server 1) and ns2.erikturk.com (Name Server 2). Then click on Save Changes:

The next screen confirms your changes and tells us that it can take up to 48 hours to propagate, i.e., it can take up to 48 hours until all clients start to ask ns1.erikturk.com and ns2.erikturk.com about ifwolfpack.com instead of the GoDaddy name servers.

So after 48 hours you can do the tests from chapter 7 again, but this time you can leave out @ns1.erikturk.com and @ns2.erikturk.com because ns1.erikturk.com and ns2.erikturk.com are now authoritative.

dig any ifwolfpack.com
dig any www.ifwolfpack.com
dig any mail.ifwolfpack.com

should now show the same results as in chapter 7.


9 Links


Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.
Submitted by stevenbinion (registered user) on Thu, 2009-12-10 02:58.
This guide is very helpful. thank you so much.