How does DNS work for a .co.za domain? When someone types yourbusiness.co.za, their device asks the Domain Name System which server holds your website or email, and DNS replies with an IP address in a fraction of a second. The lookup moves from the root of the internet to the .za zone, then to the .co.za registry, then to the nameservers your domain is set to use, which hold your actual records. Change those nameservers or records and you change where your website and email live. This guide explains each step in plain language and shows you what to set.
DNS in one paragraph
DNS (the Domain Name System) is the internet's address book. It translates names people can remember, like yourbusiness.co.za, into the numeric IP addresses computers use to find servers. Your domain's nameservers hold a set of records: A records for your website, MX records for email and TXT records for verification and email security. Whoever controls those records controls where your traffic goes.
Who runs DNS for .co.za domains?
Three parties are involved, and it helps to know who does what:
- ZADNA (the .za Domain Name Authority) is the statutory body that oversees the .za country code domain space, including policy for second-level domains such as .co.za, .org.za and .net.za.
- ZACR (the ZA Central Registry) operates the .co.za registry. It keeps the master database of every .co.za name and which nameservers each one uses.
- Your registrar is the company you register the domain with. It submits your details and nameservers to ZACR on your behalf and gives you a panel to change them. When you register a .co.za domain with us, that is our role.
You never deal with ZADNA or ZACR directly for normal changes. Everything happens through your registrar and your DNS host, which are often the same company. If you are new to registrars, our guide on what a domain name registrar is explains the role.
How does DNS work, step by step?
Here is what happens in the moment between typing your address and seeing your homepage:
- The browser checks its memory. If the device looked up your domain recently, it uses the saved answer and skips the rest.
- A resolver takes the question. If not, the request goes to a recursive resolver, usually run by the visitor's internet provider or a public DNS service.
- The root servers point to .za. The resolver asks a root server, which replies with the servers responsible for the .za zone.
- The .za servers point to .co.za. Those servers refer the resolver to the .co.za registry servers run by ZACR.
- The registry names your nameservers. The .co.za servers do not know your website's address. They know which nameservers your domain uses, for example ns1.yourhost.co.za, and send the resolver there.
- Your nameservers answer. Your authoritative nameservers look up the A record and return the IP address of your web server.
- The answer is cached. The resolver and the browser keep the answer for the time set in the record's TTL (time to live), so the next visit is faster.
Email follows the same path, except the sending server asks for your MX record instead of the A record. That is why your website and email can live with different companies on the same domain.
How does DNS work with nameservers and records?
Nameservers
Nameservers decide who answers for your domain. They are set at the registry through your registrar. Changing them hands control of all your records to a different DNS host in one go. You usually change nameservers when you move hosting provider. Our guide to DNS NS records shows how they are set.
DNS records
Records decide where each service points. They live on whichever nameservers you use. Changing one record moves one service, such as your website or your mail, without touching anything else. You change records when you add email or connect a tool.
The DNS records your .co.za domain uses
Most small business domains only need a handful of record types. This table shows what each does with a typical example.
| Record | What it does | Example |
|---|---|---|
| A | Points a name to an IPv4 address, usually your web server | yourbusiness.co.za to 102.x.x.x |
| AAAA | Same as A, for IPv6 addresses | yourbusiness.co.za to an IPv6 address |
| CNAME | Makes one name an alias of another | www to yourbusiness.co.za |
| MX | Tells other servers where to deliver your email | mail.yourhost.co.za, priority 10 |
| TXT | Holds text for verification and email security (SPF, DKIM, DMARC) | v=spf1 include:yourhost.co.za ~all |
| NS | Lists the nameservers that answer for the domain | ns1.yourhost.co.za |
Each record type has its own guide on our blog if you want more detail. Start with what a DNS A record is, since it is the one that connects your website.
DNS hosting: who should hold your records?
DNS hosting is the service that runs your authoritative nameservers. For most businesses the simplest choice is to use the DNS that comes with your domain or hosting. With us, nameserver management is included free with every .co.za registration, and if your website or email is hosted with us, the records are created for you in Plesk. You only need separate DNS hosting if you want advanced features such as traffic routing across several servers or a specialist security service in front of your site.
What matters more than the provider is control. Make sure the domain is registered in your business name, that you can log in to the registrar panel, and that more than one person in the company knows where DNS is managed. Our domain name registration includes that panel for every extension, not just .co.za.
How does DNS work when you change hosting or email?
- Moving your website to a new host: change the nameservers to the new host, or keep your DNS where it is and update only the A record.
- Setting up email on your domain: add the MX records and SPF, DKIM and DMARC TXT records from your email host. Our guide to email hosting with your own domain covers each step.
- Verifying a tool: Google Search Console and many other services ask you to add a TXT record to prove ownership.
- Adding a subdomain: create an A or CNAME record for names such as shop.yourbusiness.co.za.
How long do DNS changes take on a .co.za domain?
Record changes on your own nameservers usually show up within minutes to a few hours, because the old answer only lives in caches for as long as its TTL. Nameserver changes take longer, often a few hours and occasionally up to 24 to 48 hours, because the registry and resolvers around the world must pick up the new delegation. This spreading period is called propagation, and our article on what DNS propagation is explains how to check progress.
Tip before any move: a day ahead, lower the TTL on your A and MX records to a short value such as 300 seconds. When you make the switch, visitors pick up the new address far sooner. Raise the TTL again once everything is stable.
Common DNS mistakes and how to avoid them
- Changing nameservers without copying records. The new DNS host starts empty. If you do not recreate MX and TXT records first, email stops arriving.
- Two SPF records. A domain may only have one SPF TXT record. Merge services into a single record.
- Letting the domain lapse. If a .co.za expires, its DNS stops answering and both website and email go offline. Turn on auto renewal and check the dates on our domain pricing page.
- Losing access to the registrar account. Keep the login and recovery email under company control, not with a former developer.
- Editing records at the wrong place. Changes only work at the DNS host your nameservers point to. Check the NS records before editing.
If something is not resolving and you cannot see why, contact our team with the domain name and we will check the delegation and records for you.



