Domains and DNS
Nameservers decide who answers DNS. Records are the answers. Pointing a Bizzit site is usually a CNAME, not a nameserver swap we invent.
A nameserver change moves the entire zone. A CNAME changes one hostname. People break email by swapping NS to "connect the site." We typically want a record, not a hijack of the zone. Someone whose registrar support said "just use our nameservers" while they only needed www. Screenshot NS and MX before you touch either.
Connecting a domain to Bizzit Pro is usually a DNS record: CNAME the web host to slug.bizzit.io. Nameservers are a different control. Do not change nameservers unless our live connect flow tells you to. Pro is $12 a month. Free stays on you.bizzit.io. Do not mix MX into the web job.
Who this is for
Someone whose registrar support said "just use our nameservers" while they only needed www. If that is not you, a different Bizzit guide will fit better, do not force this URL.
The actual answer
A nameserver change moves the entire zone. A CNAME changes one hostname. People break email by swapping NS to "connect the site." We typically want a record, not a hijack of the zone. Screenshot NS and MX before you touch either. 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
Stay on current nameservers. Add CNAME. Wait TTL. Test web and mail separately.
- Screenshot nameservers
- Screenshot MX
- Add only the web CNAME we document
- Wait TTL
- Test https and hello@
- Skip an NS change you do not understand
What not to do
Do not point NS at a random host "because WordPress tutorials did." Do not flatten mail. 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
We are not your mailbox. Google Workspace MX plus web CNAME is a documented pattern. NS replacement is not the default story.
Limits
Do not point NS at a random host "because WordPress tutorials did." Do not flatten mail.
Limits and caveats
Do not point NS at a random host "because WordPress tutorials did." Do not flatten mail.
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
When would I change nameservers?
If you move the whole DNS product to another DNS host. That is optional and easy to get wrong. The Bizzit default is a record.
Glue records?
Empty cell. We do not document glue as a SKU.
DNSSEC?
Not a named Bizzit SKU on this page. Do not enable it as theater without knowing the host.
Apex NS vs www CNAME?
www CNAME is the easy web path. Apex needs your host's alias tools. We do not invent flattening.