Create your domain in the new server and set everything ready.Go to the previous server and delete the account corresponding to that domain.
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.
The Reverse Lookup tool will do a reverse IP lookup.
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?
As far as I know, a forced update like this is not directly possible.Please note that in general, your ISP must setup and maintain these Reverse DNS records (i.e. If you're running Samba as Active Directory Domain Controller, you also have to administer a DNS server.If you discover problems or missing features, please open a bug report/feature request at https://bugzilla.samba.org/.Even though the internal DNS and the BIND DLZ modules are new, they both support all basic requirements for Active Directory and more.You will already find general information on the internal DNS and the BIND DLZ module and documentation about Bind as DNS Backend in the Wiki.