How to Point a Domain to Your Web Host

You have bought a domain and signed up for hosting, but visiting your address shows a parking page or nothing at all. The missing link is DNS: you need to tell the internet where your site lives. Here is how to point a domain to hosting, using either nameservers or individual DNS records, plus how to check that it worked and what to do if it has not.

What “pointing” a domain really means

Your domain registrar holds the registration. Your host holds the files. DNS (the Domain Name System) is the directory that links the two. When you point a domain, you are editing that directory so that requests for your address go to your host’s server.

There are two main ways to do it:

1. Change the nameservers so the host manages all of your DNS records.
2. Keep the registrar’s nameservers and edit individual records, mainly the A record, to hold your host’s IP address.

Either works. Which is better depends on where you want to manage DNS day to day.

Before you start

Gather these details:

• Login for the registrar where the domain is registered.
• Your host’s nameservers or server IP address. They are usually in the welcome email or the hosting dashboard.
• A list of existing DNS records, especially MX records if you use email on the domain. Take a screenshot before changing anything.

If a live website or email already runs on the domain, plan the change for a quiet time and make sure the new hosting is ready first. Upload and test your site on the new server before switching, otherwise visitors will land on an empty page.

Method 1: Change the nameservers

This is the simplest option for beginners, because the host’s dashboard then handles everything.

1. Log in to your registrar and open the domain’s management page.
2. Find the section labelled “Nameservers” or “DNS”. You may need to choose “custom nameservers”.
3. Replace the existing entries with the nameservers your host provided. They usually look like ns1.hostname.example and ns2.hostname.example. Most hosts give two, sometimes more.
4. Save the changes.
5. In your hosting account, make sure the domain has been added (as the primary or an add-on domain) so the server knows to respond to it.

Because the host now controls DNS, any records you need, such as email, must be recreated in the host’s DNS zone. This is where people lose email: they switch nameservers and forget the MX records. Recreate them first if you can.

Method 2: Edit the A record

If you would prefer to stay with your registrar’s DNS, or your email and website are with different providers, edit records instead.

1. Open the DNS management page at your registrar.
2. Locate the A record for the root domain (often shown as “@”). It currently points to a parking page IP address.
3. Change the value to the IP address your host gave you.
4. Check the “www” entry. It is typically a CNAME pointing to the root domain, or a second A record with the same IP. Make sure it resolves to the same place.
5. Leave MX, TXT and other records alone unless your host tells you to alter them.
6. Save.

An A record maps a name to an IPv4 address. If your host also provides an IPv6 address, you can add an AAAA record, but it is optional for a basic setup.

Pointing to a service rather than an IP

Website builders and some platforms ask you to add a CNAME record instead, which maps one name to another name. Follow their instructions exactly: the host will list the type, the name and the value to enter. Some platforms do not allow CNAMEs at the root, so they supply alternative methods.

Method 3: Use your host’s own tool

Many hosting companies offer a “connect domain” wizard or can configure DNS for you when you buy both services together. If you have bought the domain from the same company, pointing it may already be done automatically. Check the dashboard before editing anything manually.

How long does it take?

Changes are not instant everywhere. DNS information is cached by internet providers and devices for a period set by the record’s TTL (time to live). Nameserver changes at the registry level can take longer to spread than a simple A record edit. In practice, many changes appear within minutes to a few hours, but you should allow up to 24 to 48 hours for a full rollout.

To make things smoother when you are planning a migration, lower the TTL on your current records a day or two before the change. Then switch, and raise the TTL again afterwards.

How to check that it worked

• Visit the domain in a private browser window. Test both the root and the www version.
• Use a DNS lookup tool. Many free websites will show the A record and nameservers currently returned for your domain.
• Use the command line. Running nslookup yourdomain.co.uk on Windows, or dig yourdomain.co.uk on macOS and Linux, shows the IP address it resolves to.
• Flush your local cache if your own computer still shows the old site. You can also try a mobile phone using mobile data, which has a different cache.

If the lookup shows your host’s IP but the browser shows an error, the DNS is fine and the issue is on the server side, such as the domain not being added to the hosting account.

Common problems and fixes

Symptom	Likely cause	What to try
Still shows the old site	Cache or propagation	Wait, clear cache, test on another network
“Server not found”	Wrong nameservers or typo	Re-check values, remove stray spaces
Host’s default page appears	Domain not added to the account	Add the domain in the hosting dashboard
Site works on www only	Missing root A record or redirect	Add an A record for “@” or set a redirect
Email stopped	MX records lost during nameserver change	Recreate MX records from your screenshot
Security warning in browser	No SSL certificate yet	Issue one once DNS resolves

That last point matters: most hosts can only issue a free SSL certificate after the domain points at them. Once DNS resolves, see our guide on how to install an SSL certificate.

A short checklist for a smooth switch

1. Build and test the site on the new host first.
2. Document existing DNS records.
3. Lower TTL a day ahead if you can.
4. Update nameservers or A records.
5. Verify using lookups and different networks.
6. Confirm email still works.
7. Enable SSL and force HTTPS.
8. Keep the old hosting active for a few days in case you need to roll back.

Website FAQ: Common Questions About Domains and DNS

FAQs

Should I use my host’s nameservers or edit the A record?

If you only have a website and want simplicity, nameservers are easier. If your email or other services depend on DNS records you want to control directly, editing records at your registrar gives finer control.

Will pointing my domain cause downtime?

Not if the new server is ready first. During propagation some visitors see the old site and some the new, so keep both working until the change has settled.

Do I need to transfer the domain to my host?

No. Pointing and transferring are different. A transfer moves the registration; pointing only changes where the domain sends visitors.

Why does my domain work on some devices but not others?

Different networks cache DNS for different lengths of time. Waiting a little or flushing the cache usually resolves it.

Conclusion

To point a domain to hosting, change the nameservers or edit the A record, confirm the domain is added in your hosting account, and then wait for DNS to settle. Keep notes of your existing records, protect your email settings, and test from more than one device. Once it resolves, move on to SSL and backups.