So here's a weird one...
I'm managing a Windows AD environment. For whatever reason, when it was built, DNS was not integrated with AD. A month or so ago I went ahead and integrated DNS with AD and all was well, or so I thought.
Now I'm looking in my main Forward Lookup Zone and I'm seeing that the vast majority, but not all, of our A records are static. Most of these records belong to workstations that are assigned their IP addresses by DHCP (also on a Windows server). As a result, we have many different A records for the same IP addresses.
Some of these records belong to machines that have been offline for years, so I'm guessing that this issue pre-dates the AD integration, but I can't say for certain. At the same time, some of the machines are brand new, so it is apparently ongoing. But I have to admit, I have no idea when it actually started happening... I just never noticed it before.
Does anybody have any idea:
A) How this might have happened
B) How to fix it (I think I saw something about a line command to convert a single record)
C) How to prevent it from continuing
Other points of interest:
-All clients are Windows 7 or Windows XP (embedded)
-Domain controllers are mostly 2012R2, with a couple of 2008R2 stragglers that I haven't decommissioned yet
-Single AD site topology
-Domain and Forest Functional Level is 2008R2
-There are only two admins, myself included, and neither of us are creating these static records
Many thanks in advance!