Skip to main content
Domains

How to Point Your Domain to Your Hosting: A Nameserver Walkthrough

MMercy Chepkemoi5 November 202616 min read82 views

You have bought a domain name and signed up for hosting, but when you type your address into a browser, you see a parked page, an error or someone else's content. Nothing is broken. Your domain and your hosting simply have not been introduced to each other yet. Connecting them is called pointing your domain to your hosting, and it is usually done by changing a setting called nameservers.

This walkthrough explains how it works in plain language, shows you step by step how to point a domain to your hosting using nameservers, offers an alternative method using an A record, and helps you check propagation and fix the problems people run into most often.

Key takeaways

  • Your registrar is where you bought the domain. Your host is where your website files live. Nameservers tell the internet which DNS servers hold your domain's records.

  • There are two ways to connect a domain: change its nameservers to your host's, or keep your current DNS and edit the A record to your server's IP address.

  • Add the domain to your hosting account first, and save your existing DNS records before you change anything, especially email records.

  • Nameserver changes can take anywhere from minutes to 24 to 48 hours to be seen everywhere.

  • You do not need to transfer your domain to your host. Pointing and transferring are different things.

  • If you move to SteboHost on an annual plan, the team can handle the migration of your site, email and DNS for you at no charge.

What Does "Pointing a Domain" Mean?

Three different things work together to put a website online:

  1. The domain name (for example yourbusiness.co.ke) is the human-friendly address.

  2. DNS (the Domain Name System) works like the internet's phone book. It translates your domain name into the numeric address (IP address) of the server that holds your website.

  3. Hosting is the server that stores your site and answers visitors' requests.

When someone visits your domain, their device asks DNS where to go. For that to work, the domain has to be configured to use the DNS servers that hold the right information. "Pointing" your domain simply means making sure that information leads to your hosting.

Key Terms Explained

Term

What it means

Registrar

The company where you registered the domain and manage its settings

Nameservers (NS)

The DNS servers that are in charge of your domain. You set them at your registrar, and there are normally at least two

DNS zone

The collection of records for your domain, stored on the nameservers

A record

Points a name, such as yourbusiness.co.ke, to an IPv4 address

CNAME record

Points one name to another name, such as www to your main domain

MX record

Says which mail servers receive email for your domain

TXT record

Holds text data such as SPF, DKIM and verification codes

TTL

How long, in seconds, other servers may cache a record before checking again

Propagation

The time it takes for DNS changes to reach servers around the world

Two Ways to Point Your Domain

Method 1: Change nameservers

Method 2: Edit DNS records

What you do

Replace your domain's nameservers with your host's

Keep your current DNS and change the A record (and others) to your host's IP address

Where DNS is managed afterwards

At your host

Where it is today, such as your registrar or a DNS provider

Best for

Most people and most beginners

People who use a separate DNS service, or who must keep DNS elsewhere

Watch out for

You must recreate any existing records, especially email, in the new zone

You must keep the IP address up to date if it ever changes

If you are not sure, use Method 1. It is the simplest, and your host can manage your DNS records along with your website.

Before You Start: A Short Checklist

  • Log in to your registrar. You need access to the account that controls the domain. If you do not remember where it is registered, use a WHOIS lookup to see the registrar and the current nameservers.

  • Have your hosting details ready. Your hosting provider will give you the nameservers and the server's IP address, usually in the welcome email or your client area.

  • Add the domain to your hosting account. Most hosts need the domain set up in your account before traffic arrives. Otherwise visitors may see a default page or someone else's site on a shared server.

  • Record your existing DNS settings. Take screenshots or copy every record, especially MX, TXT and subdomain records. When you change nameservers, the old zone stops being used.

  • Plan the timing. Choose a quiet period if the domain is already running a live website or email.

  • Check DNSSEC. If DNSSEC is switched on for your domain, read the warning in Step 5 before you change anything.

Method 1: Point Your Domain by Changing Nameservers

Step 1: Add your domain to your hosting account

In your hosting control panel or client area, add the domain you want to use. This creates the site folder and DNS zone on your host's server. If you are unsure how to do this on your plan, SteboHost support can help.

Step 2: Get your hosting nameservers

Find the nameservers in your welcome email or client area. They usually look like ns1.yourhost.com and ns2.yourhost.com, and some hosts give three or four. Always use the ones shown on your own account, and copy them exactly. [Add SteboHost's nameservers here before publishing.]

Step 3: Save your existing DNS records

Open the DNS settings at your current provider and note every record. Pay special attention to:

  • MX records, which control where email goes

  • TXT records, such as SPF, DKIM, DMARC and domain verification codes

  • Subdomain records, such as shop.yourdomain.com or mail.yourdomain.com

  • CNAME records for third-party services

If you use Google Workspace, Microsoft 365 or another mail provider, you will need to recreate these records in your new DNS zone, or your email will stop working when the nameservers change. See business email for how SteboHost handles email.

Step 4: Optional but smart: preview your site before the switch

You can check that your site is ready on the new server before pointing the domain, by temporarily mapping the domain to the server's IP address in your computer's hosts file. This only affects your own device.

# Windows: C:\Windows\System32\drivers\etc\hosts
# macOS and Linux: /etc/hosts
203.0.113.10   yourdomain.com www.yourdomain.com

Replace 203.0.113.10 with your host's real server IP address, save the file with administrator rights, and visit your domain. When you are done, remove the line, otherwise your computer will keep going to the server directly.

Step 5: Change the nameservers at your registrar

Log in to the registrar where the domain is registered and open the domain's settings. The option may be called Nameservers, DNS, Manage DNS or Domain settings. Choose the option to use custom nameservers. Depending on the registrar, the wording is often something like "Custom DNS" or "I'll use my own nameservers".

Then:

  • Remove the old nameservers

  • Enter the new nameservers from your host, one per field and exactly as given

  • Enter at least two

  • Save your changes

Important cautions:

  • DNSSEC. If DNSSEC is turned on at your registrar, it can make your domain fail to resolve after the change if the new DNS provider does not support it or has different keys. Turn it off or remove the DS record before you change nameservers, unless your new provider has told you how to move it.

  • Custom nameservers with your own domain. If you want nameservers such as ns1.yourdomain.com, you must first create glue records at the registrar. Most people do not need this.

  • Transfers in progress. Some registrars do not allow nameserver changes while a domain transfer is under way.

  • Beware of fake emails. Only change nameservers after you or your host start the process, not because of an unsolicited email asking you to "update your nameservers".

If your domain is a .co.ke or another local extension registered through an accredited registrar, the process is the same: make the change in the registrar's control panel.

Step 6: Wait for propagation, and check progress

DNS information is cached by servers around the world, so changes do not appear everywhere instantly. Often it works within minutes to a few hours, but allow up to 24 to 48 hours. See the next section for how to check.

Step 7: Test your website, SSL and email

Once your domain resolves to the new server:

  • Open your site on both the www and non-www versions, and on a phone using mobile data, to avoid your own cache.

  • Check HTTPS. A free certificate is normally issued once the domain points to the server. SteboHost provides free SSL on every domain, with certificates issued and renewed automatically. If you see a certificate warning right after the switch, give it a little time.

  • Check your email. Send and receive test messages and confirm your MX records are correct in the new zone.

  • Check subdomains and third-party services that rely on DNS records.

  • Set up redirects to your preferred version (www or non-www, HTTPS only).

Method 2: Point Your Domain by Editing DNS Records

Use this method if you manage DNS somewhere else and want to keep it there. You leave the nameservers alone, and edit the records instead.

  1. Get your server's IP address from your hosting welcome email or control panel.

  2. Log in to your current DNS provider (your registrar or a DNS service).

  3. Edit or create the A record for the root domain. The host or name is usually @, and the value is your server's IP address.

  4. Handle the www version. Either create an A record for www with the same IP, or a CNAME record for www pointing to your main domain.

  5. Remove conflicting records, such as old A records, parking records or forwarding rules that point somewhere else.

  6. Keep your MX and TXT records unless you are also changing your email provider.

  7. Choose a sensible TTL. A lower TTL, such as 300 seconds, makes later changes take effect faster.

  8. Save and wait, then check the result.

A few notes: you cannot normally use a CNAME record on the root domain, only an A record (or an ALIAS or ANAME if your DNS provider offers it). If your host gives you an IPv6 address, add an AAAA record too, and remove old AAAA records if you are not using IPv6, because a stale one can send visitors to the wrong place.

Pointing Only a Subdomain

To send just one subdomain, such as shop.yourdomain.com, to your hosting while the main domain stays elsewhere, create an A record (or a CNAME, if your host provides a target name) for that subdomain in your existing DNS. You do not need to change the nameservers.

How Long Does Propagation Take?

There is no single answer, because it depends on caching. Many changes are visible within minutes. Nameserver changes can take longer, because resolvers may cache the old nameserver information, in some cases for up to 48 hours. Lowering the TTL on your records a day or two before a planned change helps record edits spread faster, but it does not control how long nameserver information is cached.

During propagation, some visitors may reach the old server and others the new one. Avoid making changes to your site on both servers at once, and keep the old hosting active until you are sure everything has moved.

How to Check That Your Domain Points to the Right Place

From a terminal (macOS, Linux, or Windows with a suitable tool), replace example.com with your domain:

dig NS example.com +short
dig A example.com +short
dig MX example.com +short

On Windows, nslookup gives similar answers:

nslookup -type=ns example.com
nslookup example.com

You should see your host's nameservers and your server's IP address. You can also use a free global DNS checker website, such as whatsmydns.net, to look up the NS or A record and see results from locations around the world.

If your own computer still shows the old site, clear its DNS cache and try a private window or another device:

ipconfig /flushdns
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

The first command is for Windows and the second for macOS.

Troubleshooting Common Problems

  • I still see the old website. Propagation has not finished, or your computer or browser has cached the old address. Wait, flush your cache, use a private window, or check from your phone on mobile data.

  • I see a parked page, a default page or someone else's site. The domain points to the server, but it has not been added to your hosting account, or it is pointing to the wrong IP address. Add the domain to your account and check the A record.

  • "Server not found" or DNS error. The nameservers are wrong or misspelled, only one nameserver was entered, or DNSSEC is blocking resolution. Check with a DNS lookup and correct the settings.

  • My email stopped working. You changed nameservers and did not recreate your MX and TXT records in the new zone. Add them back right away.

  • The www version does not work. The www record is missing. Add a CNAME or A record for www.

  • Certificate warning or "not secure". The SSL certificate is not yet issued because the domain has not fully propagated, or you are visiting a different address from the one on the certificate. Wait, then check again. Our guide to free SSL and forcing HTTPS covers the rest.

  • Redirect loop after pointing through a CDN or proxy. The proxy's SSL mode and your server's HTTPS redirect are conflicting. Use a full end-to-end SSL mode in the proxy.

  • My registrar will not let me change nameservers. Check for a transfer in progress, a lock on the domain, or missing account verification, and contact the registrar.

Special Cases

Your domain is registered with your host

If you registered your domain and your hosting with the same company, the nameservers are often set for you automatically. You can still check them in your account and adjust them if needed.

You use Cloudflare or another DNS service

If your DNS lives at a third-party service, set the nameservers to that service, and create the A record to your host's IP address there. Choose an SSL mode that matches your server's certificate.

Your email is hosted elsewhere

If you use Google Workspace, Microsoft 365 or another email provider, make sure the DNS zone that is actually active contains their MX, SPF, DKIM and DMARC records. See our guide to email migration if you are changing email at the same time.

You want to move the domain, not just point it

Pointing a domain keeps it registered where it is. If you would rather have the registration and hosting in one place, you can transfer your domain. Do not start a transfer and a nameserver change at the same time, because some registrars block one while the other is in progress.

Security Tips

  • Turn on two-factor authentication at your registrar.

  • Keep the domain locked against unauthorised transfers, and turn on auto-renewal.

  • Use WHOIS privacy to keep your personal details out of public records.

  • Be suspicious of any message that pressures you to change nameservers or share your registrar password.

  • Keep a copy of your DNS records somewhere safe.

Quick Checklist

  • Domain added to the hosting account

  • Hosting nameservers copied exactly

  • Existing DNS records saved, especially MX and TXT

  • DNSSEC checked

  • Nameservers updated at the registrar and saved

  • Propagation checked with DNS lookups

  • Website, www version and HTTPS tested

  • Email sending and receiving tested

  • Old hosting kept active until everything is confirmed

Why Point Your Domain to SteboHost

Connecting a domain should be straightforward, and with SteboHost it is:

  • Free migration on annual plans. SteboHost's team moves your site, databases, email and DNS from your current host at no charge, so you do not need to do the technical work yourself.

  • Domains made simple. Register your domain with free WHOIS privacy and renewal prices shown before you pay, and check checkout for any active promotion on a .co.ke domain.

  • Managed DNS so you can control your records from one place. See managed DNS.

  • Free SSL issued and renewed automatically on every domain.

  • Business email with SPF, DKIM and DMARC configured automatically. See business email.

  • 24/7 infrastructure monitoring and a 99.9% uptime SLA, so your site stays reachable once it is live. See monitoring.

  • Local support on +254 703 610 464, and billing in KES by M-Pesa, card or bank transfer.

Current plan and renewal prices are shown before you buy. Compare plans and pricing, explore SteboHost web hosting, or browse the knowledge base for more guides.

Conclusion

Pointing your domain to your hosting comes down to a few clear steps: add the domain to your hosting account, copy your host's nameservers, save your existing DNS records, update the nameservers at your registrar and wait for propagation to finish. Then test your website, HTTPS and email. If you prefer to keep DNS where it is, edit the A record instead. Either way, a little care with email records and DNSSEC saves most of the stress.

Would you rather have a specialist do it? Contact the team or call +254 703 610 464, and SteboHost will help you get your domain connected.

Frequently Asked Questions

How long does it take for nameservers to update?

Often a few minutes to a few hours, but it can take up to 24 to 48 hours for the change to be visible everywhere, because DNS information is cached around the world. During this time, some visitors may still see the old site.

Do I need to change nameservers or edit an A record?

Either works. Changing nameservers hands DNS management to your host and is the simplest choice for most people. Editing the A record keeps DNS where it is, which suits people who use a separate DNS service. Choose one method and keep your records consistent.

Will changing nameservers affect my email?

It can. When you change nameservers, your domain starts using the DNS zone at the new provider, so your MX and TXT records must exist there too. Save your existing records first and recreate them in the new zone, otherwise your email may stop working.

Can I use my domain before propagation is finished?

You can test your site early by mapping the domain to your server's IP address in your computer's hosts file, which only affects your own device. For visitors, the site becomes reachable as propagation completes, so it is best to keep the old hosting active until the switch is finished.

Why do I see a default page or the wrong website after pointing my domain?

The domain is reaching the server, but the server does not know which site to show for it. Make sure the domain has been added to your hosting account, and that your A record points to the correct IP address for your account.

What are glue records and do I need them?

Glue records are needed only if you use nameservers that belong to your own domain, such as ns1.yourdomain.com. They let the internet find those nameservers in the first place. Most people use their host's nameservers and do not need glue records.

Do I need to transfer my domain to point it to my hosting?

No. You can keep your domain registered where it is and simply point it to your hosting by changing nameservers or DNS records. A transfer moves the registration itself and is a separate process. It can be convenient to have domain and hosting under one roof, but it is optional.

#Domains#Nameservers#DNS#Hosting#DNS Propagation#Website Setup#A Record
M

Written by Mercy Chepkemoi

SteboHost engineering and operations team. We write practical guides on hosting, domains, email and security for African businesses — based on what we see in the field, not marketing copy.

Ready to get started?

Browse our hosting plans or contact our team for help choosing the right one.