Lately, I was asked for advice about why DNS records in Active Directory were not updated with the current IP-address during the reinstallation of PC’s.We could not reproduce the problem with this approach.BUT here's an Idea and something I do from time to time.
The ACL of an automatically set up DNS record always includes an entry like this: In the case of our customer however, the following happened: After the object is deleted, the SID cannot be dissolved anymore (picture 2).
When the object is set up anew, the “old” SID remains in the ACL of the DNS records and the new one is not included (picture 3). Computer objects will not be only reset and not deleted anymore.
This resets the password of the object and makes it possible for the next PC joined with this name to use the already existing computer object.
The SID of the original object remains and the authorization on the DNS record stays valid -.
Also, I don't know how to save a Zone Record and recreate it using WHM or any other tool.
I do know that when I deleted a hosting account today and recreated it, the original Zone Record seemed to be propagated instantly to a DNS resolver up the line from my computer. I'm moving my web application to another server and in the next few days I'll refresh the DNS to point to the new IP location.Unfortunately some browsers and SOs keep a DNS cache that will make users point to the old IP location./proc/sys/net/ipv4/ip_forward iptables -t nat -A PREROUTING -d [OLD_IP] -p tcp --dport 80 -j DNAT --to-destination [NEW_IP]:80 iptables -t nat -A PREROUTING -d [OLD_IP] -p tcp --dport 443 -j DNAT --to-destination [NEW_IP]:443 iptables -t nat -A POSTROUTING -j MASQUERADE So if the issue is you just created a website and your clients or any given ISP DNS is cached and doesn't show new site yet.Yes all the other stuff applies ipconfig reset browser etc.If that is the case, it is deleted and a new computer object is set up when joining the PC to the domain.