Iggy79
asked on
Windows DNS Server Not Returning Correct Resolve
I have a public DNS server our company uses for itself and a few customers. I have not had any issues with the server till today. Here is what we have
NS01
Windows Server 2008 R2
Primary DNS Server
NS02
Windows Server 2008 R2
Secondary DNS Server
History of issue:
3 days ago we changed an “A” Record for support.mydomain.com as we had a web server change. This server also has a ticket system on it that receives emails so we have a “MX” record that points to the same as the A record.
In the DNS Manager all records look correct.
The Secondary DNS Server has synced with the primary and has all the same records.
But we are still getting emails to the old server. We thought it was simply a propagation issue but come to find out our NS01 is returning the old record even though it has been updated. When we go to mxtoolbox and check NS01 gives us the old record but NS02 gives us the correct one. This is extremely odd as how could NS02 have the right one sense it gets it from NS01? We have tried the following
Clear Cash
Update Server Data Files
Scavenge Stale Resource Records.
All from the GUI in DNS Manager.
We have followed all of the Technet check lists and troubleshooting guides and we are not getting anything to work. Please help.
NS01
Windows Server 2008 R2
Primary DNS Server
NS02
Windows Server 2008 R2
Secondary DNS Server
History of issue:
3 days ago we changed an “A” Record for support.mydomain.com as we had a web server change. This server also has a ticket system on it that receives emails so we have a “MX” record that points to the same as the A record.
In the DNS Manager all records look correct.
The Secondary DNS Server has synced with the primary and has all the same records.
But we are still getting emails to the old server. We thought it was simply a propagation issue but come to find out our NS01 is returning the old record even though it has been updated. When we go to mxtoolbox and check NS01 gives us the old record but NS02 gives us the correct one. This is extremely odd as how could NS02 have the right one sense it gets it from NS01? We have tried the following
Clear Cash
Update Server Data Files
Scavenge Stale Resource Records.
All from the GUI in DNS Manager.
We have followed all of the Technet check lists and troubleshooting guides and we are not getting anything to work. Please help.
ASKER
I do have a PTR for support.mydomain.com and it points to the correct IP address.
This also does not explain why I am getting correct resolves from NS02 but not from NS01. I have also checked the Windows Event log and I cannot find anything that looks like it is a red flag.
This also does not explain why I am getting correct resolves from NS02 but not from NS01. I have also checked the Windows Event log and I cannot find anything that looks like it is a red flag.
On NS01, are forwarders set up? Is there a public name server listed above your domain server?
Right click NS01, click properties and then check the fowarders tab. Please paste that screenshot.
try to ping the IP Address and see if that correctly resolves it to the correct name, using the -a switch:
ping -a 108.163.194.124
if it doesn't resolve correctly, then there is possibly a problem (sometimes duplicate) with your Reverse DNS Lookup records.
ping -a 108.163.194.124
if it doesn't resolve correctly, then there is possibly a problem (sometimes duplicate) with your Reverse DNS Lookup records.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I solved it myself.
Found this hotfix. Shot in the darK?
http://support2.microsoft.com/kb/2508835