FAQ: How to setup our WHM server to use only one single IP

[taotoon]

Notes:

1. We don't care who want to tracert to our WHM server or Client DNS.
Just a trick to let client use their nameservers.

2. Some registry don't allow to use same IP for both nameservers such as Network Solutions Inc. In this case, assign 2 IPs for them.

3. OpenSRS does allow same IP or setup only one nameserver.

4. I don't know the side effect of using one nameserver or same IP for both nameservers.
Anyone know these effect please tell me thanks for advance.

[B][COLOR=Red]How to setup our WHM server to use only one single IP[/COLOR][/B]

Why we need two or three IPs for our WHM server and two nameservers ? 
We can use only one single IP for all. To do these follow the steps below.

Example:     server.WHMdomain.com   111.111.111.111
             ns1.WHMdomain.com      111.111.111.111
             ns2.WHMdomain.com      111.111.111.111


[B]1. Edit nameservers for the WHM server[/B]

You login to domain management page, the web that you purchased the domain
name. Then assign the private nameservers by point to the same IP. Nowadays
it takes 15 minutes to active.

Example:      ns1.WHMdomain.com     111.111.111.111
              ns2.WHMdomain.com     111.111.111.111


[B]2. Allow Sharing Nameserver IPs[/B]

These step let you host any domains on the main IP ( shared IP ).
You login to WHM and goto [U]Main >> Server Setup >> Tweak Settings[/U].
Scroll down to [U]System[/U] section and enable [U]Allow Sharing Nameserver IPs[/U].

 
[B]3. Edit a DNS zone[/B]

You login to WHM and goto [U]Main >> DNS Functions >> Edit a DNS Zone[/U].
Edit DNS zone as the example below. In these example, our WHM server
use the IP 111.111.111.111 

; Modified by Web Host Manager
; Zone File for WHMdomain.com

$TTL 14400
@ 14400 IN SOA  ns1.WHMdomain.com. you55.gmail.com. (
                                   ...
                                   ...
                                                    )
 
WHMdomain.com.            14400 in  NS     ns1.WHMdomain.com. 
WHMdomain.com.            14400 in  NS     ns2.WHMdomain.com. 
ns1                       14400 in  A      111.111.111.111
ns2                       14400 in  A      111.111.111.111
server                    14400 in  A      111.111.111.111
WHMdomain.com.            14400 in  A      111.111.111.111
localhost.WHMdomain.com.  14400 in  A      127.0.01
WHMdomain.com.            14400 in  MX     0  WHMdomain.com. 
mail                      14400 in  CNAME  WHMdomain.com. 
www                       14400 in  CNAME  WHMdomain.com. 
ftp                       14400 in  CNAME  WHMdomain.com. 


----------------------------------------------------------------------------


[B][COLOR=Red]How to setup client private nameservers by use only one main shared IP[/COLOR][/B]

This guide will show you how to setup client private nameservers for their
domains, such as ns1.johndoe.com and ns2.johndoe.com for domain johndoe.com


[B]1. Tell your client to edit the nameservers[/B]

Client should login to his domain management page, the web that he purchased
the domain name. Then assign the private nameservers by point to the same IP.
Tell him to use a single main share IP for both nameservers. Nowadays it takes
15 minutes to active.

Example:      ns1.johndoe.com    111.111.111.111
              ns2.johndoe.com    111.111.111.111


[B]2. Edit a DNS zone[/B]

You login to WHM and goto [U]Main >> DNS Functions >> Edit a DNS Zone[/U].
Edit DNS zone as the example below. In these example, client use the
dedicated IP 222.222.222.222

; Modified by Web Host Manager
; Zone File for domain2.com

$TTL 14400
@ 14400 IN SOA  ns1.WHMdomain.com. you55.gmail.com. (
                                   ...
                                   ...
                                                    )
 
johndoe.com.              14400 in  NS     ns1.WHMdomain.com. 
johndoe.com.              14400 in  NS     ns2.WHMdomain.com. 
ns1                       14400 in  A      111.111.111.111
ns2                       14400 in  A      111.111.111.111
johndoe.com.              14400 in  A      222.222.222.222
localhost.johndoe.com.    14400 in  A      127.0.01
johndoe.com.              14400 in  MX     0  johndoe.com. 
mail                      14400 in  CNAME  johndoe.com. 
www                       14400 in  CNAME  johndoe.com. 
ftp                       14400 in  CNAME  johndoe.com. 


----------------------------------------------------------------------------

 

[chirpy]

Just to add to this:

Do bear in mind that is a very bad idea to have both your NS served on the same server, whether using the same IP address or not. Your authoratitive DNS zones should always be on completely different servers, preferably in different NOC's and different upstream network providers. If you do not do this and your server goes down (compared to using separate DNS servers):

1. Email sent to the server will be lost (whereas with separate DNS servers it will be queued on the senders server)

2. Web sites will come up as non-existent (where with separate DNS servers it come up as temporarily unreachable)

3. Because of 2, your hosted sites could be delisted from search engines

These may not sound serious, but if you're hosting customers, they won't thank you for losing email or having their sites disappear when there's something you could have done to prevent it. If you don't have a second server, there are plenty of providers of secondary DNS services.

 

[taotoon]

I agree.
I am on small VPS small website.

Can I use master DNS of datacenter ?
When update DNS zone, it look like sync to master DNS.