Link to home
Start Free TrialLog in
Avatar of canuckconsulting
canuckconsultingFlag for United Kingdom of Great Britain and Northern Ireland

asked on

DNS Issue - incorrect IP shown for host

We have a situation where one of our Windows 2012 servers (SERVER_A) had the wrong address for another Windows 2012 server (SERVER_B).  It was wildly wrong with the leading octet being wrong.  The DNS server was reporting the correct address for SERVER_B and, after flushing DNS SERVER_A is now fine.

My question is how could this happen?  I've checked the hosts file on SERVER_A and nothing relevant there.



User generated image
Avatar of bbao
bbao
Flag of Australia image

when it reports incorrectly again, run IPCONFIG /DISPLAYDNS to how the incorrect IP was resolved and cached.

BTW, did you try a reverse check against the incorrect IP ever reported? was its domain name related to your business?
Avatar of canuckconsulting

ASKER

Following your advice, that ip address is the DNS server for the hosting company our virtual server is located on.  Now below I logged back on to SERVER_A and tested the connection to it's DC, verifying it is set correctly to BBCDC07.  The IP address shows correctly via DNS but when I ping it I get the same ip address i was getting in my first post.  Something very screwy is going on but I'm unsure how to dig deeper.

User generated image
Here's the results of the DisplayDNS you mentioned:

User generated image
Have you tried to flush the DNS cache on the server that is not resolving the correct ip

[code]ipaddress /flushdns[/code]
Yes, that was the third command shown in my first post.  As noted, it resolved the first issue but not the issue shown in my previous post.
You mentions a VM in your question. How many NIC adapters are on that server? And are all of the reporting back to your DNS server.

Also is the ip you are see one from your ISP?
SOLUTION
Avatar of bbao
bbao
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
yo_bee - On both the DC and the client machine I only see a single network adapter as below:

User generated image

Bing CISM / CISSP - Thanks for the info and I'm very embarrassed to have botched my masking!

Pinging an unknown host results in "could not find host" as shown below.  I think this behaviour is correct.

User generated image
How did you perform the DNS health check?  Unfortunately I have limited experience with DNS so am struggling with the basics.  If i could reproduce your health check perhaps I could interpret and highlight the issues with management to justify getting some external help.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Do you use WINS? Ping will use the result returned from local cache if cached or from your WINS/DNS servers. Whichever service replies quicker wins. Is the server multi homed (has multiple NIC's)? If it is, make sure only the IP you want registering an address is set to register its record in DNS.
DrDave242 - Yes, our internal AD domain is named  bb*****td.com.  Your conclusion re an external DNS being unsuccessfully queried for an internal address makes sense to me but I don't see how it happened.  Below shows the four DNS servers configured on SERVER_A.  The last two DNS servers are unaware of local addresses but time out instead of return the 12.x.x.161.  
User generated image
Learnctx - No, WINS is not configured and we only have one nic on SERVER_A.

User generated image
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for the help guys; I hope the point distribution is fair.