Domains and DNS
TTL is how long the internet remembers the old answer. Drop it before the cutover if you can. After you change the CNAME, you still wait.
Sibling to dns-ttl-and-propagation: this URL is the pre-move ritual. A 86400 TTL on Friday means a Monday surprise. Lower first, wait one old TTL, then switch. We do not sell a "propagation accelerator." Someone moving Saturday morning with a 24-hour TTL they never lowered. Propagation is not a SKU. It is math plus caches you do not control.
If you can, lower the DNS TTL on the web hostname a full old-TTL before you CNAME it to slug.bizzit.io. Then change the record on Bizzit Pro at $12 a month and wait the new TTL. Do not edit MX for a website move.
Who this is for
Someone moving Saturday morning with a 24-hour TTL they never lowered. If that is not you, a different Bizzit guide will fit better, do not force this URL.
The actual answer
Sibling to dns-ttl-and-propagation: this URL is the pre-move ritual. A 86400 TTL on Friday means a Monday surprise. Lower first, wait one old TTL, then switch. We do not sell a "propagation accelerator." Propagation is not a SKU. It is math plus caches you do not control. The short version is still the one in the box at the top of this page. The rest of the article exists so you do not have to guess the limits.
Do this in order
Note current TTL. Set a lower one. Wait. Change CNAME. Wait again. Test from a phone off Wi-Fi.
- Read the current TTL on www
- Lower it if the host allows
- Wait at least the old TTL
- Add CNAME to slug.bizzit.io
- Wait the new TTL
- Test https and mail separately
What not to do
Do not lower MX TTL as a side effect if you did not mean to. Do not print during the wait. Do not call remaining cache "Bizzit being down." That is the usual way a useful page turns into a doorway, a fake comparison, or a brief Cipher cannot honor.
How this shows up on Bizzit
Custom domain is Pro. The slug is already live without this ritual.
Limits
Do not lower MX TTL as a side effect if you did not mean to. Do not print during the wait. Do not call remaining cache "Bizzit being down."
Limits and caveats
Do not lower MX TTL as a side effect if you did not mean to. Do not print during the wait. Do not call remaining cache "Bizzit being down."
If a sentence would require a competitor SKU we have not verified, or a statistic we did not measure, it does not belong here.
What to do after you read this
If this page answered the query, open Create with the nouns from your own business, not a slogan. If it did not, you are probably in the wrong cluster: go back to the blog hub or Domains and DNS. Do not spin a second URL for a synonym. One intent per page is the whole point of this library.
Tools that actually do this job
These are public pages. Use them when the job is this job. They are not a second product you have to buy.
Questions people actually ask
How low can TTL go?
Whatever your DNS host allows. We will not invent a number.
Can I skip lowering?
Yes, and you wait longer after the change. That is the trade.
Apex TTL too?
If you also move @, that record has its own TTL. Flattening is still not a SKU we invent.
CDN flush?
Empty cell. We have not named a purge product.