Menu
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. Some users are rookies and they'll not refresh the DNS cache manually and I know we'll lose a lot of them in the first weeks after this change.
Is there anyway to force this DNS cache to refresh so it'll be transparent for our final users?
519
You use the ipconfig /registerdns command to manually force an update of the client name registration in DNS. The computer is turned on. A member server is promoted to a domain controller.
Open the Start Menu and start typing command prompt until you see it in the results. 2. Type ipconfig /flushdns when the prompt loads and hit Enter on the keyboard. The DNS Cache database on your computer is now clear.
There isn't really a method to force DNS propagation, but we can force our local PC to update it. Or even, we can simply change our local DNS servers. This way there is a big chance to force the new DNS to update.
Type ipconfig /renew in the command prompt and press the Enter/Return key on your keyboard. Wait a few seconds for a reply that the IP address has been re-established. Type ipconfig /flushdns in the command prompt and press the Enter/Return key on your keyboard.
As far as I know, a forced update like this is not directly possible. 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.
Here's a guide for less painful DNS changes.
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.
69
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
