Updating dns server
(Why this was the case, you can read below.) I asked the customer to describe the imaging process to me a little more detailed..
The customer checks, if a computer object with the PC’s name already exists, before joining the PC into the domain.
If that is the case, it is deleted and a new computer object is set up when joining the PC to the domain.
The new computer object however also has a new SID.
You might be able to reduce the DNS downtime by reducing the TTL (Time-To-Live) value of the entries before changing them, if your name server service provider allows that. A fair warning, though - not all name servers between your client and the authoritative (origin) name server will enforce your TTL, they might have their own caching time.
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 -.
/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.
Also, I don't know how to save a Zone Record and recreate it using WHM or any other tool.