Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 267
  • Last Modified:

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.
0
Iggy79
Asked:
Iggy79
  • 5
  • 3
1 Solution
 
Chris HInfrastructure ManagerCommented:
Have you checked your reverse records?  Make sure you don't have an incorrect PTR record in there for your subnet.

Found this hotfix.  Shot in the darK?
http://support2.microsoft.com/kb/2508835
0
 
Iggy79Author Commented:
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.
0
 
Chris HInfrastructure ManagerCommented:
On NS01, are forwarders set up?  Is there a public name server listed above your domain server?
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
Iggy79Author Commented:
NS01 Config
I have attached a screen shot of NS01
0
 
Chris HInfrastructure ManagerCommented:
Right click NS01, click properties and then check the fowarders tab.  Please paste that screenshot.
0
 
Iggy79Author Commented:
Here is the screen shoot.NS01 Forwarders
0
 
jkaiosIT DirectorCommented:
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.
0
 
Iggy79Author Commented:
This issue was resolved but removing all the static IP settings on the NIC and reapplying them.  not sure why this solved the issue as I put in all the same values that it had previous.
0
 
Iggy79Author Commented:
I solved it myself.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now