• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 69
  • Last Modified:

Rogue A Records in DNS

Hi there, hope someone can help :)

We have a domain which is fine with a mixture of 2003, 2008 and 2012 servers in, and we have a child domain which had 2 2003 servers in, last week we introduced 2 new 2012 R2 domain controllers (domain functional level is 2003 so knew it would be fine).

However it just seems a bit of a coincedence that all of a sudden we are getting over 100 rogue A DNS records with the same IP address which is taking down 100 machines off the network. The minute they are deleted it works fine, I think its an issue with replication across the domain controllers but i'm not 100%.

They appeared yesterday and have reappeared this morning, your assistance would be greately appreciated.

Thanks
0
Terellion
Asked:
Terellion
  • 3
  • 3
1 Solution
 
MaheshArchitectCommented:
Run windows update on 2012 R2 and install all recommended updates
Windows 2012 R2 have many issues and they have got fixed with April 2014 and next update rollup
Then reboot the server and check if again you face any issues
0
 
TerellionAuthor Commented:
Yep done that before I promoted them to be domain controllers and still the same :(
0
 
MaheshArchitectCommented:
Ensure that dns zone is set to dynamic update only
Are you using DHCP server on 2008 R2 server? try to enable dhcp name protection in dhcp console
can you please post screen shot of corruption
0
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

 
TerellionAuthor Commented:
Hi there, looks like we have cracked it, when all the desktops were built they had been given a certain IP, when it had been shipped to the site the user added the new IP but never removed the original so hundreds of machines all had the same IP. The 2003 DC's didn't pick this up but the min we added the 2012 DC it seemed to pick up on this and register all the IP's for each machine. We have now removed them all and looks to be sorted. Thanks for your help though :)
0
 
MaheshArchitectCommented:
Great
The things can get weired with simple \ little mistakes
0
 
TerellionAuthor Commented:
The reason above resolved the issue
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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