Dns record is not correct on clients machine, however it is correct on dns server

Posted on 2008-11-04
Medium Priority
Last Modified: 2012-05-05
 HI everyone,
       This is a strange issue i have on our new deployed domain controller. I run it under test envirment at local site (canada) first and it has ip address (give by DHCP), after everything is ok, I sent it to another city (usa) and change the ip address of it to IP).
       However after one night, my canada clients report they can not ping this server, the dns record still show the ip address on that machine is I tried ipconfig /flushdns to let the client get new address but it is not working. I test it on all our canada dns servers and usa clients, they all can ping it and dns record on them is correct. Only the canada clients can not get the correct dns record.
      all our server is windows 2003. I do not know what else i can try to correct this problem. Please advise a direction.
Thanks a lot
Question by:shirenliang
  • 4
  • 2
LVL 12

Expert Comment

ID: 22876386
Can you ping the server by it's new IP?
Manually delete the DNS record for the server and recreate it.
Allow dns to propagate changes and then check.
Hope this helps

Author Comment

ID: 22876487
If i ping the server by it ip address, it is working. if i ping musa-fs-2, it said the host not response.
I tried to delete the dns record from USA dns server, after i delete it. Ping musa-fs-2 on that server it give the ip address back. Then i recreate a A record for and then ping musa-fs-2, it go back However canada client still get same resulte before and after i delete then dns record on USA dns server.
LVL 12

Accepted Solution

RobinHuman earned 1500 total points
ID: 22876680
Have you forced a dns replication from the server that is showing the correct info?
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

LVL 19

Expert Comment

ID: 22876846
Since you have several changes and so many things going on, suggest removing all the DNS records for this machine in both Forward and Reverse Lookup Zones. Go to the properties of the NIC and on the advanced tab, ensure that "Register this connection in DNS" is checked. Reboot the machine. When back up, from the command prompt: ipconfig /registerdns.

See if you can get a clean record out there.

Author Comment

ID: 22876877
Hi RobinHuman,
   Thanks for your quick help. How to do a forced dns replication under windows?
    If i do a flushdns, where the come from for our client computer? i thought if we do a flushdns the user will have nothing on their machine and forced to lookup dns server for dns record.


Author Comment

ID: 22878499
Try to deleted all dns and replicate it, it is not working.
I found a interest thing.
  if i ping musa-fs-2.mallory.musa, the ip address is correct (
However if i ping musa-fs-2 the ip address is not right. (
What will cause this? Is there a way to make sure they have same ip address?

Author Closing Comment

ID: 31513078
Thanks to give me a direction. I finished to add an A record to Canada Site Dns to force it to our USA server. It looks to me a dns forward query issue.

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

Question has a verified solution.

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

by Batuhan Cetin Within the dynamic life of an IT administrator, we hold many information in our minds like user names, passwords, IDs, phone numbers, incomes, service tags, bills and the order from our wives to buy milk when coming back to home.…
Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
Integration Management Part 2
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?

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