Problem: (All of this is under 1 umbrella internal DNS solution) When a computer (using dhcp) moves from one internal network (10.1.X.X/16) to a different internal network (10.100.7.X/24), it gets a new 10.100.7.X I.P. address but retains its old DNS entry (proper DNS name but wrong [old] I.P. address).
We have multiple internal networks being routed around inside of our business. We have a Windows DNS solution managing DNS for all of our internal networks. When a new computer arrives and gets loaded (O.S. and apps installed) inside the I.T. office (on network “X”) and is then moved and placed into the desired department (on network “Y”), the computer gets the proper I.P. address for network “Y”, but it retains the DNS entry that has the computers Proper Name with its old I.P. address from network “X”.
The computer load time to roll out is around 1 to 2 days. Scavenging is set to No-refresh 3 days, and Refresh 3 days.
Most (92%-96%) of our computers are unaffected by this, as they are already in place. This is only a problem for the new computers that we (I.T.) load for the different departments, and we roll out (on average) 1 to 2 a week.
Any suggestions on how to handle this problem?