There are two ways to point your domain to your hosting: change the nameservers at your registrar to the ones your host gives you, or keep your current DNS and add records (an A record for the bare domain and a CNAME or A record for www) that point to your host's server. Changing nameservers hands all DNS to your host and is simplest. Adding records gives you finer control and is safer when email or other services already run on the domain.
This guide explains both methods, when to use each, and how to check your changes worked.
Method 1 vs method 2 at a glance
| Change nameservers | Add A / CNAME records | |
|---|---|---|
| Where you make the change | At your registrar | At your current DNS provider |
| Who manages DNS afterwards | Your hosting provider | Your current DNS provider |
| Effect on email and other records | All records must exist at the new host first | Only the records you change are affected |
| Best for | New domains, or moving everything to one provider | Domains with existing email or services elsewhere |
| Typical timing | Can take longer to propagate | Often quicker, depending on TTL |
If you're not sure what nameservers are, read what are nameservers and when should you change them first.
Method 1 - Change the nameservers
Use this when your hosting provider will manage all your DNS, typically when your website and email are with the same host, or when the domain is new and has nothing on it yet.
Step 1 - Get the nameserver names from your host
Your host gives you two or more nameservers, which look something like:
ns1.your-host.example
ns2.your-host.example
(These are placeholders; use the exact names your host provides.)
Step 2 - Recreate existing records first
If the domain already has email, verification records or subdomains, add all of them at the new host before you switch. Once the nameservers change, only the records at the new provider count. Check MX, TXT (SPF, DKIM, DMARC, verification) and any CNAMEs.
Step 3 - Update nameservers at your registrar
Log in to the account where the domain is registered, find the nameserver or DNS settings for the domain, replace the existing nameservers with your host's, and save. For a .co.za domain, the registrar submits the change to the registry.
Step 4 - Wait and check
Nameserver changes can take a while to be seen everywhere, because resolvers cache the old nameservers. Check progress with:
dig NS example.co.za +short
When the answer shows your new host's nameservers, DNS for the domain is being served by them.
Method 2 - Add A and CNAME records
Use this when you want to keep DNS where it is: for example, email runs on another provider, or your DNS provider has features you rely on.
Step 1 - Get the target from your host
Your host tells you what to point at: an IP address for A records, and sometimes a hostname for CNAME records. App platforms often give you a hostname for www and an IP address for the bare domain.
Step 2 - Update the records
At your current DNS provider, edit or add:
example.co.za. 300 IN A 203.0.113.10
www.example.co.za. 300 IN CNAME example.co.za.
- The A record on the bare domain (
@) points to your host's IP address. - The www record can be a CNAME to the bare domain or to a hostname your host provides, or another A record with the same IP.
- Leave MX and TXT records alone unless you're moving email too.
Remove any old A or AAAA records on the same names that point to your previous host, otherwise visitors may be sent to either server at random.
Step 3 - Check it worked
dig example.co.za A +short
dig www.example.co.za +short
Both should return your new host's address (or, for www, the CNAME target followed by the address).
After DNS points to your host
Add the domain in your hosting account
Your host must know which site to serve for your domain. On a control panel like Plesk, you add the domain to your subscription; on an app platform, you add a custom domain to the app. If you skip this, you'll see a default or error page even though DNS is correct.
Issue an SSL certificate
Free Let's Encrypt certificates need your domain to resolve to the server before they can be issued, so do this once DNS is live. Then make sure http:// redirects to https://. Learn more at letsencrypt.org.
Choose www or non-www
Pick one as your main address and redirect the other to it, so search engines see a single version of your site.
Troubleshooting
- The old site still shows. Your device or ISP has cached the old record. Wait for the TTL to expire, try another network (such as mobile data), or flush your local DNS cache.
- "Site not found" or a default page. DNS is correct but the domain hasn't been added to your hosting account.
- Email stopped working after changing nameservers. The MX records weren't recreated at the new DNS provider. Add them there.
- SSL certificate won't issue. Check that both the bare domain and
wwwresolve to the new server, and that no CAA record blocks your certificate authority.
For a full reference on record types, see DNS records explained. If you're moving an existing site, follow how to move your website to a new host so visitors don't notice the switch.
Frequently asked questions
Should I change nameservers or just the A record?
If everything (website, email, DNS) will be with one host, change nameservers for simplicity. If email or other services run elsewhere, or you're happy with your current DNS provider, just update the A and CNAME records.
How long does it take for my domain to point to my new host?
Record changes are often visible within minutes to hours, depending on the TTL of the old record. Nameserver changes tend to take longer. Allow up to a day or two before assuming something is wrong.
Will changing my nameservers affect my email?
It can. Once nameservers change, the new DNS provider answers for all records, including MX. Recreate your email records at the new provider before switching, and email carries on working.
Can I point my domain to hosting with a different company?
Yes. Your domain registrar and hosting provider don't have to be the same. You just point DNS at the hosting provider using either method above.
At NewHost, domains registered or transferred with us use NewHost DNS by default and are managed in the same dashboard as your apps and sites. Register a domain on the domains page, or explore web hosting and Next.js hosting.