DNS changes are fast on our side and slow everywhere else, because internet providers remember old answers for as long as the record's TTL allows. This checklist avoids the gap.
A day or two before
- Write down the current records: names, types, values and TTL. A screenshot of the domain's page is enough.
- Lower the TTL of the records you will change to
300(five minutes). Wait at least as long as the old TTL so the short one is everywhere.
On the day
- Bring the new place up first. The new server or email service should already work before you point anything at it.
- Change the records. In the console: open the domain under DNS, then DNS Hosting, Edit the record and Save record. It shows Live within seconds.
- Check from outside. From a terminal:
dig +short www.yourcompany.comornslookup www.yourcompany.com. Or use an online DNS checker that queries from several countries.
After
- Keep the old place running for a day, for visitors who still have the old answer.
- Raise the TTL back to
3600once everything is stable.
Moving the whole domain to Gewape Cloud DNS
Copy every record into the console first, then change the nameservers at your registrar to ns1.gewapecloud.com, ns2.gewapecloud.com and ns3.gewapecloud.com. See Add a domain.
Email changes
MX and SPF mistakes lose mail silently. After changing them, send a test message from an outside address (for example Gmail) and check it arrives.