How To Run Your Own Name Servers With ISPConfig And GoDaddy

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

How To Run Your Own Name Servers With ISPConfig And GoDaddy

Version 1.0
Author: Falko Timme <ft [at] falkotimme [dot] com>
Last edited 06/08/2006

This tutorial shows how you can run your own name servers for domains that you register with GoDaddy. Of course, this works with every other registrar as well, although the procedure might differ a little bit.

To do this, you need two servers with two different public IP addresses and with ISPConfig installed, and of course a GoDaddy account.

1 Current Situation

Our current situation is as follows: we have

  • ISPConfig server #1: IP address 64.25.171.8; this one will be our primary name server.
  • ISPConfig server #2: IP address 64.25.171.9; this one will be our secondary name server.
  • a GoDaddy account with the already registered domains erikturk.com and ifwolfpack.com. Both are currently using GoDaddy's name servers (e.g. park27.secureserver.net and park28.secureserver.net).

2 Our Goal

This is what we want to achieve:

  • Create DNS records for ns1.erikturk.com and ns2.erikturk.com.
  • ISPConfig server #1 will be ns1.erikturk.com.
  • ISPConfig server #2 will be ns2.erikturk.com.
  • Create DNS records for ifwolfpack.com on ns1.erikturk.com and ns2.erikturk.com.
  • Change ifwolfpack.com's authoritative name servers from Godaddy's name servers to ns1.erikturk.com and ns2.erikturk.com.

3 Create ns1.erikturk.com And ns2.erikturk.com

Our domain erikturk.com is already registered, but now we want to create the DNS records ns1.erikturk.com and ns2.erikturk.com that point to our ISPConfig servers #1 and #2.

Please note: It is important that your browser allows pop-up windows, otherwise the GoDaddy interface will not work as expected!

We log in to our GoDaddy account:

Click on My Account:

Then go to Manage Domains:

You should see a list of the domains you registered with GoDaddy. As you see, erikturk.com and ifwolfpack.com are in this list. Click on erikturk.com:

In the menu that opens on the right, click on the + sign in front of Total DNS Control:

Then go to Total DNS Control And MX Records:

Select Launch Total DNS Control Manager:

In the window that pops up you can see the existing DNS records for erikturk.com. Click on Add New A Record:

Enter ns1 as Host Name (do not enter ns1.erikturk.com, just ns1!) and 64.25.171.8 as IP address (this is the IP address of our ISPConfig server #1). You don't need to change the TTL value. Click on Continue then:

Confirm by clicking on Add:

Back on the list of DNS records, a window will pop up saying that it will take approx. 24 - 48 hours until the new DNS record propagates over the internet. Click on OK.

Now we do the same procedure again for ns2.erikturk.com, but this time we enter 64.25.171.9 as IP address as ns2.erikturk.com should point to our ISPConfig server #2:

You can close the window with the DNS records now. Now we must register ns1.erikturk.com and ns2.erikturk.com as name servers, i.e., we must tell GoDaddy that we want to use these two servers as name servers. Back in the main GoDaddy interface, click on the + in front of Domain Host Summary:

Click on Click here to see details or to modify:

In the new form we enter ns1 and ns2 and their respective IP addresses and click on Save Changes:

The next screen confirms your changes:

Our name servers ns1.erikturk.com and ns2.erikturk.com have been created and registered. It takes approx. 24 - 48 hours until our changes propagate over the internet, but normally it works the next day. You should wait until then before you proceed.

Please note: the steps from this chapter have to be done only once. You don't have to do them again if you want to use ns1.erikturk.com and ns2.erikturk.com for other domains than ifwolfpack.com, too.

You can use the dig command on one of your Linux systems to check the status of ns1.erikturk.com and ns2.erikturk.com. After our changes have propagated, the output should look like this:

dig ns1.erikturk.com

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

;; QUESTION SECTION:
;ns1.erikturk.com. IN A

;; ANSWER SECTION:
ns1.erikturk.com. 3600 IN A 64.25.171.8

;; Query time: 312 msec
;; SERVER: 145.253.2.75#53(145.253.2.75)
;; WHEN: Wed Jun 7 17:39:07 2006
;; MSG SIZE rcvd: 50

dig ns2.erikturk.com

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

;; QUESTION SECTION:
;ns2.erikturk.com. IN A

;; ANSWER SECTION:
ns2.erikturk.com. 3600 IN A 64.25.171.9

;; Query time: 106 msec
;; SERVER: 145.253.2.75#53(145.253.2.75)
;; WHEN: Wed Jun 7 17:39:09 2006
;; MSG SIZE rcvd: 50

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 BMD Media Web Design (not registered) on Tue, 2012-11-06 06:27.

This helped a lot, thanks!

 The screenshots can be updated, but still easy to understand (even better than a lot of Co-Lo and Datacenters Troubleshooting pages lol. 

Submitted by cdmlb (not registered) on Fri, 2010-05-14 03:44.

What is the point of even having your DNS servers if you still need to register ifwolfpack.com with godaddy?

I would think just registering your DNS servers with godaddy and registering ifwolfpack.com with your own DNS servers would be good enough.

The whole point of having your own DNS server is to register domains with your DNS server and with no one else's.

So you are still using godaddy are the DNS server if you need to register the domain with them, pointing to your own DNS server, and re-registering the domain with your own DNS servers.

It defeats the purpose, and you still endup having to pay for two domains and not just one.

Just use godaddy as your DNS server, and just point each domain you register anyways with godaddy to your web server.

If you are like using IIS with like windows server, each website has a host header name to identify what domain was visited and the correct website appears even do all domains point to the same webserver ip address.

I wish some one would show us or tell us what steps need to be taken to have our own DNS servers, we register the DNS servers on the internet prob with the ROOT server(s), and after that all the domains we would want would just be registered on our own DNS servers, and no one elses.

There has to be a way to pay for one domain, and have all other domains you want on your own servers and accessed from any place in the world, instead of paying for each domain.

How does it actualy all work, you go the ROOT server .
afther that you got the com ca org servers
after that you got the domain servers
after tht it hits the webserver

Are all websites in the entire world registered on every DNS server in the world, I don't think so, it's registered in at least 1 or 2 DNS servers only, that's it.

Thanks for putting up with me.

Submitted by Anonymous (not registered) on Tue, 2010-03-02 23:45.

Hi there,

Just wondering...

Isn't it enough to add the Own Name Servers in the Host Summary ?

Do Own Name Servers need to be added as A Records in Total DNS Control as well ?

Thanks...

Submitted by peterspoon (registered user) on Thu, 2007-08-09 17:03.
Hi, godaddy.com's domain management interface has been strongly modified, so maybe would be nice to update the how-to too. Some of the options and links are now in totally different places. Regards Piotr
Submitted by manuel (not registered) on Thu, 2009-12-31 13:36.

Hi ,

the ip adress in godaddy is the internal ip or the router ip ?

can tou help me ?

Thanks!

 

Submitted by Anonymous (not registered) on Tue, 2009-01-13 06:51.
Godaddy changes the interface nearly every day, half the time I cannot see the Login area, but the principles stay the same, forget that, if anyone figures out Apache James with a dynamic IP or DynDns you got money!