Nameservers explained: how to point your domain to your hosting

You have bought a domain name and paid for hosting, but when you type your address into a browser, nothing appears, or you see a parking page. The missing link is almost always the nameservers. This guide gives you nameservers explained in simple terms, then walks you step by step through pointing your domain to your hosting.

What a nameserver actually does

Computers find each other using numbers called IP addresses, but people prefer names like yourshop.co.ug. The Domain Name System (DNS) is the internet's address book that turns names into numbers.

A nameserver is a server that holds the DNS records for your domain. When someone in Gulu or Mbarara types your web address, their device asks: "Which nameservers are responsible for this domain?" It then asks those nameservers: "What is the IP address of the website, and where should email go?" The nameservers reply, and the browser connects to your hosting server.

So there are two separate pieces:

• The registrar: the company where you registered and renew the domain. The registrar records which nameservers your domain uses.
• The DNS host: whoever runs those nameservers and stores the records. Very often this is your web hosting company, but it can also be your registrar or a service such as Cloudflare.

Nameservers vs DNS records

People often mix these up, so it helps to see the difference clearly.

• Nameservers answer the question "who is in charge of this domain's records?" They usually come in pairs, such as ns1.example-host.com and ns2.example-host.com, so that if one is unavailable the other still answers.
• A record: points a name to an IPv4 address, for example yourshop.co.ug to your hosting server.
• CNAME record: points one name to another name, often used for www.
• MX record: tells the world which server receives email for your domain.
• TXT record: holds text such as SPF and DKIM settings that help your emails avoid spam folders, or verification codes for Google and Microsoft.

When you change nameservers, you are moving the entire address book to a new place. When you change an A record, you are editing one line inside the address book.

Two ways to point a domain to hosting

You have two common options. Pick one, not both.

Option 1: change the nameservers (simplest)

You set your domain to use your hosting company's nameservers. The host then manages all the DNS records automatically, including the website, email and SSL verification. This is the easiest choice if your website and email are with the same hosting company.

Option 2: keep the nameservers and edit records

You leave the nameservers at your registrar or another DNS provider and only change specific records: an A record for the website and, if needed, MX records for email. This suits people who use different providers for different services, for example a website on one host and email on Google Workspace, and who are comfortable editing DNS.

Step by step: changing your nameservers

The exact screens differ from registrar to registrar, but the process is nearly always the same.

1. Find your hosting nameservers. They are usually in the welcome email from your host, or in your hosting client area. Copy them exactly, including every dot.
2. Log in to your registrar. This is where you paid for the domain. For a .ug or .co.ug domain, it is the accredited registrar you bought it from.
3. Open the domain's management page. Look for "Manage domain", "DNS" or "Nameservers".
4. Choose custom nameservers. Many registrars default to their own nameservers. Switch to "use custom nameservers".
5. Enter the new nameservers. Paste the first in Nameserver 1 and the second in Nameserver 2. Add a third or fourth only if your host gave you more.
6. Save the changes. Some registrars send a confirmation email or ask for a code.
7. Wait for propagation. The change spreads across the internet gradually (more on this below).

Before you switch, check whether you already have working email on the domain. If your email is hosted somewhere else, make sure the new DNS host has the correct MX records, or your email will stop arriving.

Understanding propagation time

After you change nameservers, internet providers around the world do not all see the change instantly. Each one keeps a cached copy of DNS information for a period known as the TTL (time to live). Until that copy expires, some people see the old setup and others see the new one.

In practice, changes often show within a few hours, but it can take up to 24 to 48 hours in some cases. During that time:

• Your site may load for you on MTN data but not yet on a friend's Airtel connection, or the other way round.
• Email may arrive at the old server for a short while, so do not close the old email account immediately.
• Avoid making several changes in a row. Make one change and give it time.

How to check that it worked

You do not have to guess. Use these simple checks:

1. Online DNS checkers: websites such as whatsmydns.net let you look up your domain's nameservers and A record from many locations at once.
2. Command line: on Windows, open Command Prompt and type nslookup -type=ns yourdomain.co.ug. On macOS or Linux, use dig ns yourdomain.co.ug.
3. WHOIS lookup: a WHOIS search shows which nameservers the registry has on record for your domain.
4. Browser test: open your site in a private window, or on mobile data with Wi-Fi switched off, to avoid your own cached copy.

Once the new nameservers show up, install or confirm your free SSL certificate in your hosting control panel so the site loads securely on https.

Common mistakes and how to fix them

• Typos in the nameserver: a single wrong letter breaks everything. Copy and paste instead of typing.
• Changing records at the wrong place: if your nameservers point to your host, editing DNS records at the registrar does nothing. Edit records where the nameservers point.
• Forgetting email: moving nameservers without recreating MX records cuts off email. List your existing records before switching.
• Expired domain: if the domain has lapsed, no DNS change will work. Renew it first.
• Domain lock confusion: a registrar lock prevents transfers, not nameserver changes, but some registrars ask you to confirm by email. Check your inbox and spam folder.

Frequently asked questions

Do I need to transfer my domain to change nameservers?

No. You can keep the domain at your current registrar and simply point its nameservers to your hosting. Transfers are a separate process.

Why does my site work on my phone but not on my laptop?

This is usually propagation or caching. Your laptop or Wi-Fi provider still remembers the old address. Wait, clear your browser cache, or restart the router.

Can I use Cloudflare with my hosting?

Yes. You point your nameservers to Cloudflare, then add an A record in Cloudflare that points to your hosting server's IP address. Remember to add your email records there too.

How many nameservers do I need?

At least two. Most hosts provide two, and some provide four. Use all the ones your host gives you.

Conclusion

Nameservers sound technical, but the idea is simple: they tell the internet where your domain's address book lives. Copy the right nameservers, change them once at your registrar, wait patiently and check with a DNS tool. If you host with Baasa Cloud, our support team can confirm the correct nameservers and check your records for you, so your website and email come online smoothly.