My company has about 150 remote sites that connect to company HQ via vpn. Each site has a router that is managed by a third party. This third party has set up nating on the routers so that, for example, a computer at a site has an internal IP of 10.61.198.178, and the site router nats it to another internal IP of 172.16.20.10 . And so while the 10.61.198.178 address is unique to the device at that site, the 172.16.20.10 is used across the board for all 150 sites. This is problematic when trying to push updates to computers at these sites because the dns records for all 150 sites are going to be 172.16.20.10 and the update does not know where to go. Previously, I had manually entered in 150 A records into DNS for the unique IP addresses at each site and that worked - updates were able to be pushed. A couple of days ago though, all of the records reverted to 172.16.20.10 across the board - I have no idea why. I do have a dns backup with the A records I created, but I don't know what will happen if I import them back into DNS. I'm afraid that may hose our network. So I guess the question is two-fold:
1. Is there a way for the A records to not randomly revert to the generic IP address? Is there a reason why this would occur when the records had been in place for several weeks?
2. Is there a way to re-import the A records for just these sites without overwriting DNS records for the entire network?