When I RDP or use a protocol to access a PC by name,it takes me to a totally different PC

hi guys

All of our PC records in DNS are showing as Static in the timestamp. So now, when I use a person's PC name to connect to them, it takes me to a totally different PC. Is that related?

Last week, someone at work deleted a DNS zone. We exported the DNS records from another server before they updated too and salvaged them by re-importing them using the DNSCMD.exe command. But now, all records have static timestamps.

Do I need to do something with DNS record aging etc? If so, what would you recommend?

Thanks for helping
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
It very likely is DNS, if you use DHCP and the DHCP system can't update records.  For any devices that use DHCP, delete their static records. As DHCP renews, the records will get created properly.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cliff GaliherCommented:
You can always force. DHCP renew to speed it up too. But that'd require touching each machine.
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
Ping the remote system by name, then try IPCONFIG /flushdns, ping it again and see if it returns the correct address.
Introducing the "443 Security Simplified" Podcast

This new podcast puts you inside the minds of leading white-hat hackers and security researchers. Hosts Marc Laliberte and Corey Nachreiner turn complex security concepts into easily understood and actionable insights on the latest cyber security headlines and trends.

ste5anSenior DeveloperCommented:
Depending on the situation: already the name registration (DNS,AD) from the destination machine could have failed. Maybe you need to rerun /REGISTERDNS on the destination machine. This can also indicate a replication (timing) issues in a larger AD/DNS environment.
YashyAuthor Commented:
Thanks for responding guys. Cliff - if I delete an entry that is not a server, it won't affect the user's access to network content? Last week, when our colleague deleted the entries, people had issues accessing our Fileserver content by name. That's why I thought deleting their entries will cause issues. If I delete, perhaps I should restart the DHCP services and DNS services in order for the entries to populate quickly?
Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
Per your question above, if you remove an A record from DNS, you can always re-establish that record by going to the system in question and running IPCONFIG /registerdns.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

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.