Nameservers are the servers that hold the official DNS records for your domain. When someone types example.co.za, the internet asks the registry which nameservers are responsible for that domain, then asks those nameservers where the website and email live. Change your nameservers and you change who controls all of your DNS in one step, which is powerful and occasionally dangerous.
This guide explains what nameservers do, how they differ from individual DNS records, and when you should (and should not) change them.
How nameservers fit into DNS
Every domain lookup follows a short chain of questions:
- Your device asks a resolver (usually run by your ISP, or a public resolver) for
www.example.co.za. - The resolver asks the root servers who handles
.za, then asks the.zaservers who handles.co.za. - The
.co.zaregistry answers with the nameservers set forexample.co.za. - The resolver asks those nameservers for the actual record, for example the A record for
www. - The answer is cached for as long as the record's TTL (time to live) allows.
So the registry only stores one thing about your DNS: which nameservers to ask. Everything else, including your website address, your mail servers and verification records, lives on those nameservers. For a fuller tour of record types, see DNS records explained.
Nameservers vs DNS records
People often mix these up, so here is the difference in one table.
| Nameservers | DNS records | |
|---|---|---|
| Where they are set | At your domain registrar (sent to the registry) | On whichever nameservers are active |
| What they control | Which DNS provider is authoritative | Where each service points (web, email, verification) |
| Typical change | Moving DNS to a new provider | Pointing a site to a new server, adding email |
| Impact | Replaces the whole DNS zone at once | Affects only that one record |
| Propagation | Can take up to 24-48 hours | Usually follows the record's TTL |
A useful rule: change records when you move one service, change nameservers when you move who manages DNS.
What a nameserver change actually does
When you switch nameservers, the old provider's zone stops being used. Every record you had there, including MX records for email, SPF and DKIM TXT records, and any subdomains, simply disappears from the internet's point of view unless you have recreated them at the new provider first.
This is the most common reason email "suddenly stops working" after a website move. The website was set up at the new host, the nameservers were switched, and nobody copied the MX records.
When you should change nameservers
Changing nameservers makes sense when:
- You are moving everything to one provider. If your hosting, email and domain management will all live at the same place, letting that provider run DNS keeps things simple.
- Your current DNS provider is unreliable or hard to use. A clean dashboard where you can see and edit every record is worth a lot.
- You want a specialised DNS service. Some teams use a dedicated DNS or CDN provider for features like traffic steering or DDoS protection.
- You are taking control back. If a previous developer or agency set the nameservers to their own account and you cannot log in, moving nameservers to a provider you control fixes the problem permanently.
When you should NOT change nameservers
Leave the nameservers alone when:
- You only want to point your website somewhere new. Change the A or CNAME record instead. Your email and other records stay untouched. How to point your domain to your hosting walks through both approaches.
- Email is hosted elsewhere and you are not sure of the settings. Switching nameservers without the MX, SPF, DKIM and DMARC values will interrupt email.
- You need a zero-risk change during business hours. A record-level change is smaller and easier to roll back.
How to change nameservers safely
Follow this checklist and a nameserver change is usually uneventful.
- Export or screenshot your current zone. List every record: A, AAAA, CNAME, MX, TXT, SRV and CAA. Do not forget subdomains like
mail,autodiscoverorshop. - Recreate every record at the new DNS provider. Check the MX priority values and the exact TXT strings.
- Compare the two zones. You can query the new nameservers directly before switching:
# Ask the new nameserver directly (replace with your provider's nameserver)
dig @ns1.new-dns-provider.example example.co.za MX +short
dig @ns1.new-dns-provider.example example.co.za TXT +short
- Update the nameservers at your registrar. Most providers ask for at least two nameservers.
- Monitor for a day or two. Check website, inbound email and outbound email. Some resolvers cache the old nameservers until their TTL expires.
- Keep the old zone for a week. Do not delete it until you are sure nothing still depends on it.
To see which nameservers a domain uses right now:
dig example.co.za NS +short
On Windows you can use nslookup -type=NS example.co.za.
Nameservers and .co.za domains
For .co.za domains the change is submitted by your registrar to the registry. The registry can check that the new nameservers respond correctly for your domain, so set up the zone at the new provider before you submit the change. If the new nameservers do not answer for the domain yet, the update may be rejected or delayed.
Ownership and nameservers are separate things. Changing nameservers does not transfer the domain, and transferring a domain does not have to change the nameservers. If you want to move the registration itself, see how to transfer a .co.za domain.
How NewHost handles nameservers
Domains registered or transferred to NewHost use NewHost DNS by default, and you manage every record in the dashboard at app.newhost.co.za. If you would rather keep DNS with another provider, you can point individual records at your NewHost app or website instead of changing nameservers. You can also search and register domains and see the options on our domains page.
Frequently asked questions
How long does a nameserver change take?
Often within a few hours, but allow up to 24-48 hours. Resolvers cache the old nameserver information, so different people may see the old and new DNS for a while. Keep both zones identical during that period.
Will changing nameservers affect my email?
Only if the new DNS zone is missing your email records. Copy the MX, SPF, DKIM and DMARC records to the new provider before switching, and email carries on as normal.
How many nameservers do I need?
At least two, ideally on separate networks, so your domain still resolves if one is unavailable. Your DNS provider will give you the names to use.
Can I use my own custom nameservers, like ns1.example.co.za?
Yes, these are called vanity or private nameservers. They need glue records at the registry and nameservers that actually serve your zone, so they are mostly used by hosting companies and agencies rather than individual businesses.
Is changing nameservers the same as transferring my domain?
No. Nameservers decide who answers DNS questions; the registrar holds the registration. You can change either without changing the other.
Want DNS, hosting and domains in one dashboard? Register or transfer your domain with NewHost and manage every record yourself, or contact us and we will help you plan the move.