Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Rogue A Records in DNS

Posted on 2015-01-25
6
64 Views
Last Modified: 2015-01-30
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
Comment
Question by:Terellion
  • 3
  • 3
6 Comments
 
LVL 36

Expert Comment

by:Mahesh
ID: 40568967
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
 

Author Comment

by:Terellion
ID: 40569049
Yep done that before I promoted them to be domain controllers and still the same :(
0
 
LVL 36

Expert Comment

by:Mahesh
ID: 40569487
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
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

Accepted Solution

by:
Terellion earned 0 total points
ID: 40570110
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
 
LVL 36

Expert Comment

by:Mahesh
ID: 40570125
Great
The things can get weired with simple \ little mistakes
0
 

Author Closing Comment

by:Terellion
ID: 40579382
The reason above resolved the issue
0

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Domain Service Not Responding 14 30
Certificate error in RDP Servers 5 31
Change default Permissions for windows services 9 16
time esx vm's to reboot 4 23
This article will review the basic installation and configuration for Windows Software Update Services (WSUS) in a Windows 2012 R2 environment.  WSUS is a Microsoft tool that allows administrators to manage and control updates to be approved and ins…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

829 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