leehinde
- Make DNS change.
- Drum fingers waiting for DNS to propagate.
Just to clarify, do you mean:
- Change the nameservers (from WF -> OS) at the domain name registrar?
- Change the DNS records (
A, MX, etc.) at WF (or OS) to point to OS?
If #1, I'd suggest creating A, MX, etc. records at OS (https://my.opalstack.com/dns/). These (at first) will match what's already set at WF. But when you make these DNS records, set a low TTL. I think 300 is the lowest OS allows. Once you do this, you can update the nameservers, at your registrar, to point to OS.
You'll know the nameserver propigation has completed (at least for you) if you run dig domainname.com a and see the lowered TTL value that you set in the OS CP.
Do this now.
- That way the nameserver propagation will take place over the next few days (since you can't control the
TTL at the registrar, because Internet Rules 101).
- And it won't break anything in the mean time (as long as you've set the right DNS information at OS.)
Then when you're ready to "throw the switch track lever" for your live apps (WF -> OS), you do that in the OS Control Panel (https://my.opalstack.com/dns/) by updating the A, MX, etc. records to point to the corresponding OS IPs.
And since you lowered the TTL days earlier (to 300), that switch should only take 5 min. at most (300 seconds).
Bonus: If something goes wrong, switching BACK to WF will also only take around 5 min. (worst case).
Granted: Not all DNS servers respect TTL values. But that's a universal to matter which way you go.
If #2: You already know all of this ;-)
I hope this helps.
