DNS staleness and quick computer moves between internal networks
problem: (all of under 1 umbrella internal dns solution) when computer (using dhcp) moves 1 internal network (10.1.x.x/16) different internal network (10.100.7.x/24), gets new 10.100.7.x i.p. address retains old dns entry (proper dns name wrong [old] i.p. address). we have multiple internal networks being routed around inside of our business. have windows dns solution managing dns of our internal networks. when new computer arrives , gets loaded (o.s. , apps installed) inside i.t. office (on network “x”) , moved , placed desired department (on network “y”), computer gets proper i.p. address network “y”, retains dns entry has computers proper name old i.p. address network “x”. the computer load time roll out around 1 2 days. scavenging set no-refresh 3 days, , refresh 3 days. most (92%-96%) of our computers unaffected this, in place. problem new computers (i.t.) load different departments, , roll out (on average) 1 2 week. any suggestions on how hand...