?
Solved

Changing IP address of a nameserver steps

Posted on 2007-08-10
11
Medium Priority
?
530 Views
Last Modified: 2010-08-05
I am moving my Microsoft DNS servers to new boxes with new IPs.

I have changed the ip addresses for the name servers at my registrar. These changes have not propagated yet.

I changed the ip from 64.251.8.16 to 75.121.6.5

I have added all the DNS records to the new machines using DNS DUMP.

When I look at the nameserver properties for any of the records they show, the nameserver and the original ip.

Right Click on Zone > view properties > select Name servers tab

So I see ns1.mydnsmachine.com 64.251.8.16

Do I have to change the 64.251.8.16 manually, or will this change when the changes I made propagate.
0
Comment
Question by:juliandormon
  • 6
  • 5
11 Comments
 
LVL 29

Expert Comment

by:Jan Springer
ID: 19675936
If I understand the question correctly,  you dumped the existing zone files and ported them to the new nameserver.

On the new nameserver, you need to manually update the NS records.
0
 

Author Comment

by:juliandormon
ID: 19676851
Ok so manually change the ip address?
The domsins are the same. ns1.mydnsmachine.com stays the same. Right?
0
 
LVL 29

Expert Comment

by:Jan Springer
ID: 19676924
If the nameservers have the same fully qualified domain name and the only thing that has changed is the IP address for those hosts, then in your forward zone:

ns1         IN             A           75.121.6.5
ns2         IN             A           new2.ip.addr

and in your in-addr.arpa zone for the inverse:

6.5.121.75.in-addr.arpa.           IN           PTR            ns1.domain.com.
new2.ip.addr.in-addr.arpa.         IN           PTR            ns2.domain.com.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
LVL 29

Expert Comment

by:Jan Springer
ID: 19676962
A note of interest:

If the hostnames of the nameservers along with the IPs are different at the registrar, in addition to adding the address and pointer records for the new hosts, you will need to change all of the NS records (where applicable) to identify the new authoritative nameservers.
0
 

Author Comment

by:juliandormon
ID: 19680119
Thank s Jesper,
This is starting to make sense.
NOw when I do a DNS report at DNSstuff.com, the report says that I have mismatched glue.
The parent servers are showing the old IP and my DNS is now showing the new IP.

I switched the nameservers over 48 hours ago, will the parent servers catch up via propogation or am I missing something else? Do I need to update the parent somehow?

ERROR: Your nameservers report glue that is different from what the parent servers report. This will cause DNS servers to get confused; some may go to the IP provided by the parent servers, while others may get to the ones provided by your authoritative DNS servers. Problem record(s) are:

ns2.righthookmedia.net.:
Parent server (l.gtld-servers.net) says A record is 64.251.8.16, but
authoritative DNS server (64.251.8.6) says it is 75.121.6.5
0
 
LVL 29

Expert Comment

by:Jan Springer
ID: 19683944
It appears that ns1.righthookmedia.net and ns2.righthookmedia.net are the name servers for this domain.

At the registrar level, are the IPs bound to the new nameservers?

If the nameserver fully qualified domain name has not changed, you need to change the "A" record associated with them, increase the serial number and restart your DNS server.

Can  you verify that information and also let me know if ns1 and ns2 used to be the hostnames for the nameservers for this domain?
0
 

Author Comment

by:juliandormon
ID: 19684110
Thanks! That is right.
righthookmedia.net has nameservers:
ns1.righthookmedia.net
ns2.righthookmedia.net

ns1.righthookmedia.net at the registrar points to 64.251.8.6
ns2.righthookmedia.net at the registrar points to 75.127.67.179 (the new box)

A records at 64.251.8.6 machine are:
Host (A) 64.251.8.6
ns1 64.251.8.6
ns2 75.127.67.179 (this is the new DNS machine)

These records are identical on the 75.127.67.179.

I have incremented both serials on both machines and restarted the DNS server on both.
0
 
LVL 29

Expert Comment

by:Jan Springer
ID: 19684220
Have you setup NS2 on the old machine with the new IP also?

And, does the registrar ask for the IP address with the hostname?  Because, the registrar currently shows the old IP with NS2.
0
 

Author Comment

by:juliandormon
ID: 19684604
Hi Jesper,
In regard to question 1:
I just recreated the records on the old ns2.righthookmedia.net machine. So this is reporting properly now.

In regards to the second question:
I think your asking what are the nameservers listed for righthookmedia.net.
They are ns.righthookmedia.net
and ns2.righthookmedia.net
The registrar does not ask for the ip addresses when filling this in, so I guess they resolve the IPs.

How are you finding what IPs they are resolving to?
0
 
LVL 29

Accepted Solution

by:
Jan Springer earned 2000 total points
ID: 19684808
when I do a 'whois righthookmedia.net' the nameservers in the return data are:

nserver:                         ns1.righthookmedia.net 64.251.8.6
nserver:                         ns2.righthookmedia.net 64.251.8.132

however, when I do a dig to see the name servers for your domain, I am seeing the response:

ns1.righthookmedia.net. 9269    IN      A       64.251.8.6
ns2.righthookmedia.net. 9272    IN      A       75.127.67.179

So, it appears that the only thing left to do is fix the glue at your registrar binding the name servers to the new IPs.
0
 

Author Comment

by:juliandormon
ID: 19695789
Thanks Jesper.
I am awaiting the glue to change.
I called my registrar and the have escalated this to a level 2 tech to see why this has not propagated yet.
Haven't heard anything yet. I think it's their problem.
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Most DNS problems are VERY easily troubleshot and identifiable if you can follow the steps a DNS query takes. I would like to share the step-by-step a DNS query takes from the origin to the destination. _____________________________________________…
There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…
Loops Section Overview

850 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question