DNS entry keeps reverting back to old value

A DNS entry for a server keeps reverting back to its old value in the Forward Lookup Zone.  I'm using a microsoft DNS server on a Windows Server 2008 platform.  I have a WAN with an AD on each end.  The entry gets changed on both when I update one side, but for some reason it keeps going back to the old value (the IP address of the AD/DNS server) after several hours.

Any idea on what might be causing this or how I can troubleshoot?
larryAsked:
Who is Participating?
 
larryAuthor Commented:
Unfortunately all of the suggestions didn't pan out.  I ended up setting the DNS entry as read only which prevents it from changing back.  I know that isn't the ideal solution, but it worked.
0
 
Darius GhassemCommented:
What is the old value? The server's will update their own IP address. Can you explain a little more exactly what you are doing when you mean when you update one side? What are you updating?
0
 
larryAuthor Commented:
The old value (value of the AD/DNS server) is 10.1.2.41 and I'm trying to update the server (an Exchange server) to 10.1.2.43.  

I update it by going into the DNS Manager > Foward Lookup Zone and go into the properties of the Host (A) record of the server to change it back to 10.1.2.43.  Several hours later it goes back to 10.1.2.41.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Darius GhassemCommented:
What is the IP address of the Exchange server? If the server has 10.1.2.41 in it's TCP\IP setting as it's IP address it is going to update that record with that IP address. You can't just go in DNS and update the record because the record will updated by the system.
0
 
larryAuthor Commented:
I just confirmed that the IP Address of the Exchange server is 10.1.2.43, which is what it should be.  It is running in a VMWare environment if that has anything to do with it.
0
 
Darius GhassemCommented:
So, the IP address is the correct IP address, right? Click Advance in the TCP\IP settings make sure there isn't two IPs there. Run a ipconfig /flushdns then ipconfig /registerdns on the Exchange system. Make sure you only have one NIC not two.
0
 
larryAuthor Commented:
I initially had it configured with two IP addresses, but changed quite some time ago.  The other IP address it had was 10.1.2.44, though.

I went ahead and flushed the dns and registered it.  I probably won't know until tomorrow if it worked.  Do you know of any other way it could be getting changed?
0
 
Darius GhassemCommented:
Does the change replicate to other DNS server? A record are updated 98% of the time by their host others are updated manually so it is one of the two in your case you are manually updating the record but it is changing back which usually means a device is updating the record.
0
 
larryAuthor Commented:
Yes, it does replicate to the other DNS server.  Is there a DNS log that I can use to figure out where the change is coming from?  Hopefully the flushdns and registerdns did the trick, but if not I would like to know where the change is coming from.  I did a registry search on the 10.1.2.43 machine for 10.1.2.41, and the only entries that came up were the DNS server as expected.
0
 
Darius GhassemCommented:
We will see how it goes.
0
 
larryAuthor Commented:
Unfortunately it didn't go so well.  I rebooted the mail server and it went back to 10.1.2.41.  Is there any way I can put a lock on that entry in the DNS server?  
0
 
Darius GhassemCommented:
Do a ipconfig /all and post. How many NICs are you running? Do you have RAS running?
0
 
larryAuthor Commented:
Just one, and RAS isn't running.  I turned off "Register this connection's address in DNS" under the IP properties, so hopefully that will prevent it from changing... if the change is coming from that server.
0
 
Darius GhassemCommented:
Let's see if that fixes it but you really want it checked.
0
 
larryAuthor Commented:
I totally agree, if you or anyone else reading this has any ideas on how to troubleshoot this problem I would love to hear it.  I scanned the registry on both servers and was unable to find anything that might be causing this to happen.  It's pretty frustrating because every time it changes my users are unable to access the Exchange server until I change it back.
0
 
Darius GhassemCommented:
When the IP changes can you ping my name? If you can't ping by name then there has to be a setting some where holding this IP address.
0
 
LynetteArntsenCommented:
check wins server?
0
 
chulamin2Commented:
ipconfig /registerdns on the errant machine. Worked for me. Permanently updated the entry on the DNS servers.
0
 
MathiauCommented:
did you have the IP still reserved in a DHCP server....
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.