Domains and DNS
Swapping NS moves every record to a new DNS host. Adding CNAME www is one row. Most Bizzit connects need the row, not the swap.
Sibling to nameservers-versus-records: this URL is the mistake-in-progress. A host wizard says "use our NS." You comply. Mail dies. The site still was one CNAME away. Someone mid-wizard with new NS values in the clipboard. Put the clipboard down. Open records. Add CNAME. Stop.
You usually do not change nameservers to put a domain on Bizzit. Upgrade to Pro at $12 a month and CNAME the web hostname to slug.bizzit.io at the DNS host you already use. A nameserver change is a zone move and will break mail if MX is not copied.
Who this is for
Someone mid-wizard with new NS values in the clipboard. If that is not you, a different Bizzit guide will fit better, do not force this URL.
The actual answer
Sibling to nameservers-versus-records: this URL is the mistake-in-progress. A host wizard says "use our NS." You comply. Mail dies. The site still was one CNAME away. Put the clipboard down. Open records. Add CNAME. Stop. 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
Cancel the NS wizard. Screenshot MX. Add CNAME. Wait TTL. Test both.
- Abort an NS change you started by habit
- Stay on current nameservers
- Add CNAME only
- Verify MX still matches the screenshot
- Load the site after TTL
What not to do
Do not mix a transfer, an NS change, and a CNAME on the same afternoon. Do not invent glue records. 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
If a future live flow requires our nameservers, that screen will say so. Until then, records-first is the honest default.
Limits
Do not mix a transfer, an NS change, and a CNAME on the same afternoon. Do not invent glue records.
Limits and caveats
Do not mix a transfer, an NS change, and a CNAME on the same afternoon. Do not invent glue records.
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
The registrar requires NS to use email?
Then you already picked a bundled DNS host. Add CNAME there. Still not a reason to NS-swap a second time.
Child nameservers?
Empty cell. Glue is not a SKU we document.
TTL after NS change?
NS changes can take longer than a single record. Another reason not to do it for a website CNAME.
Pro without DNS access?
You need whoever logs into the DNS host. That may be your registrar or a friend. We cannot click it.