Introduction

You bought a domain name and you built a website, but the two are not connected yet. Typing the domain into a browser shows nothing — or worse, a parking page from your registrar. Connecting them is a DNS change, not a file upload, and it takes about ten minutes of actual work plus some waiting.

There are two ways to make the connection, and you only need one: change the domain’s nameservers to your host’s, or keep your DNS where it is and edit the A record to point at your server’s IP address. Picking the wrong method is the most common mistake beginners make, and it usually shows up as email breaking or the site pointing at the wrong server.

What actually happens when you connect a domain

The Domain Name System (DNS) is the internet’s phone book: it translates your domain name into the IP address of the server where your website lives. When someone types your domain into a browser, their computer asks a chain of DNS servers — the root servers, then the servers for your domain’s ending (such as .com), then your domain’s authoritative nameservers — and the authoritative nameserver returns the record that says where the site is.

Your registrar is the company where you bought the domain. Your host is where your website’s files live. Nameservers are the DNS servers that hold your domain’s records, and you set them at your registrar. Connecting the domain means making sure the records those nameservers hold point at your host — either by handing DNS control to your host entirely, or by editing the records yourself.

One important distinction: pointing is not transferring. Connecting a domain to a host does not move the domain registration. Your domain stays with your registrar unless you deliberately start a transfer, which is a separate process.

Before you change anything: the pre-change worksheet

Do this first. It takes five minutes and it is your rollback plan.

1. Add the domain to your hosting account first. Most hosts require you to add the domain as an “addon domain” or “parked domain” (or select it during signup) before it will answer for it. If you point the DNS before the host knows the domain, visitors get an error page even though the DNS is correct.
2. Save your existing DNS records. Log in to wherever your DNS is currently managed — usually your registrar’s DNS panel — and take a screenshot or copy down every record: A, CNAME, MX, and TXT records, with their values. Email records (MX) matter most. If you lose them, restoring email becomes a guessing game.
3. Get the exact values from your host. Your host’s welcome email or control panel will give you either its nameservers (they look like ns1.yourhost.com and ns2.yourhost.com) or a server IP address for an A record. Use only the values your host gives you. Do not invent an IP address or copy one from an unrelated tutorial — a single wrong character can take the site or the email offline.
4. Note what else uses the domain. Does the domain already receive email? Are there subdomains in use, such as shop.yourbusiness.com or mail.yourbusiness.com? Are there TXT records for email authentication (SPF, DKIM, DMARC)? Anything that currently works through DNS needs to keep working after the change.
5. Check whether DNSSEC is turned on. DNSSEC is a security extension that signs your DNS records. If it is enabled at your registrar, changing nameservers can make the domain fail to resolve if the new DNS provider does not support it or uses different keys. If you are unsure, check your registrar’s DNS settings — and if DNSSEC is on and you do not understand it, ask your host’s support before changing nameservers.

Method 1: Change the nameservers (the simple route)

Use this method when your host manages all of your DNS — a typical shared hosting plan, most managed hosting — and you want one control panel for everything. Point the domain’s nameservers at your host once, and web, mail, and subdomains follow automatically, because the host creates the right records for you.

When to choose it: you bought hosting that includes DNS, you do not use a separate DNS service such as Cloudflare, and your email is either with the host or you are prepared to recreate the mail records on the host.

The steps:

1. Find your host’s nameservers in its welcome email or control panel (usually under General Information or Server Information). You will normally get two, such as ns1.yourhost.com and ns2.yourhost.com.
2. Log in to your registrar — the company where you bought the domain — and open the domain’s nameserver or DNS settings.
3. Replace the current nameservers with your host’s nameservers, exactly as given. Save the change.
4. Recreate any records the old DNS had that the new host does not already provide. This is the step people forget: once the nameservers change, every record now comes from the new host — including your MX records. If the old DNS had mail, custom TXT, or subdomain records the new host does not have, those stop resolving the moment the switch lands. Check your pre-change worksheet and recreate what is missing.
5. Wait for propagation, then test (see the verification section below).

What to watch out for: do not configure records in both places. Once you change nameservers, the records at your original registrar become inactive — editing them there does nothing. All DNS changes from now on happen at your host.

Method 2: Edit the DNS records (the precise route)

Use this method when your DNS lives somewhere you want to keep — Cloudflare for its CDN and security features, or your registrar’s own DNS — or when you only want to point part of the domain (for example, moving a subdomain to a new server while the main site stays put), or when your website and email sit on different providers and you want to steer each record by hand.

When to choose it: your email is with a different provider (Google Workspace, Microsoft 365, or your registrar’s mail), you use Cloudflare or another DNS service, or you only need to move the website and nothing else.

The steps:

1. Get your server’s IPv4 address from your host — the control panel or welcome email will list it. You need the exact address for your account.
2. Open the DNS panel where your domain’s DNS is currently managed (your registrar’s DNS editor, Cloudflare, or another provider). Do not change the nameservers.
3. Set the apex (the bare domain, yourbusiness.com): an A record, host @ (some panels want a blank field or the domain itself), value = your server’s IP address. Set the TTL to 300 seconds while you are testing, so mistakes clear fast.
4. Set www: a CNAME record, host www, pointing to your apex domain (yourbusiness.com). If your provider will not let you CNAME www to the apex, use a second A record for www to the same IP address instead. Note that a CNAME cannot sit on the apex itself — the apex must carry its SOA and NS records, and DNS rules do not allow a CNAME to coexist with them.
5. If your host also gave you an IPv6 address, add an AAAA record for the apex with that value.
6. Save, then raise the TTL back to something like 3600 (one hour) once you have confirmed everything works.

What you did not touch: MX, existing TXT records (SPF, DKIM, DMARC), and any other subdomains all keep resolving exactly as before, because you only changed the A and www records. That is the main advantage of this method — it is surgical.

What to watch out for: if your server’s IP address ever changes, you must update the A record yourself — the host will not do it for you. And do not mix methods: do not change nameservers and edit A records at the same time. Pick one approach.

Which method should you choose?

Your situation	Choose	Why
Host includes DNS, email with the host, simple site	Change nameservers	One step, one control panel, host creates the records
Email with Google Workspace, Microsoft 365, or another provider	Edit DNS records	Keeps your MX records untouched
Using Cloudflare or another DNS service	Edit DNS records	Keeps the CDN and security features in place
Only moving a subdomain, or website and email on different providers	Edit DNS records	Moves only what you intend to move
Beginner, host-managed everything	Change nameservers	Fewest decisions and fewest records to get wrong

If you are still unsure, follow your host’s instructions: the host’s setup guide or welcome email will normally tell you which method it expects.

Propagation: why the site does not appear instantly

DNS changes are not instant. Servers around the world cache old records until their time-to-live (TTL) expires, so a change can look instant for one person and take hours for another. Nameserver changes usually take effect within a few hours but can take up to 48 hours to be visible everywhere; A record changes are often visible within minutes to a few hours, depending on the TTL.

Practical advice while you wait:

• Do not change the records repeatedly. You will not know which version is live, and each change restarts the waiting.
• Test properly. Use a private or incognito browser window so your browser’s cache does not show you the old site. Clear your browser cache, or test from a different device or network.
• Check with a global DNS checker. A free tool such as whatsmydns.net lets you look up your domain’s A or NS records from locations around the world, so you can see whether the change has spread or is still in progress.

Verifying the connection

Once propagation has had some time, check these in order:

1. The domain loads the site. Open the bare domain and the www version in a private window. Both should show your site.
2. HTTPS works. The browser should show the padlock with no security warning. SSL is separate from DNS — the host usually issues the certificate automatically once the domain points correctly — but it may take a short while after the DNS change. If the padlock is missing after a few hours, check your host’s SSL settings. Our SSL certificate guide explains what to check.
3. Email still works. Send yourself a test email and reply to it. If mail stops after a nameserver change, the MX records were almost certainly not recreated on the new host — check them against your pre-change worksheet.
4. Subdomains still work. Visit any subdomain you use, such as shop or mail, and confirm it still resolves.

Troubleshooting: the common failures

“The domain points to the wrong site.” The domain is usually added to the wrong hosting account, or the A record points at the wrong IP. Check the domain is added to the correct hosting account and that the IP address matches the one your host gave you, character for character.

“Email stopped working after I changed nameservers.” The new DNS zone does not have your MX records. Recreate them from your pre-change worksheet, exactly as they were, including any SPF, DKIM, and DMARC TXT records. Email will not fix itself — the records must exist in the new zone.

“It works on my phone but not my laptop” (or vice versa). Different networks and devices cache DNS for different lengths of time. This is almost always propagation, not an error. Wait, and test from a network you have not used recently.

“It has been more than 48 hours and nothing works.” At this point it is not propagation. Re-check the nameservers at your registrar (typos are common), confirm the domain is added to the hosting account, and check whether DNSSEC is interfering. If everything looks right, contact your host’s support with the domain name and the values you set.

“I changed my mind — how do I undo it?” Put the old nameservers back at your registrar, or restore the old A record values in your DNS panel. Then wait for propagation again — rollback takes the same time as the original change, usually within a few hours and up to 48 hours.

Frequently asked questions

How long does it take to connect a domain to a website?
The change itself takes about ten minutes. Propagation — the time for DNS servers worldwide to pick it up — is usually within a few hours, and can take up to 48 hours.

Do I need to transfer my domain to my host?
No. Pointing a domain and transferring a domain are different things. Pointing tells the internet where the site lives; transferring moves the registration itself. You can point a domain at any host while keeping the registration where it is.

Nameservers or A record — which is better?
Neither is better in general. Nameservers are simpler when the host manages all your DNS. A records are better when you need to keep email or other services with a different provider, or when you use a DNS service such as Cloudflare.

Will changing nameservers break my email?
It can, if the new DNS zone does not have your MX records. That is why you save the existing records before changing anything and recreate the mail records on the new host immediately after the switch. If you use the A record method instead, email is untouched.

The bottom line

Connecting a domain is a DNS decision, not a technical marathon: add the domain to your host, save your existing records, then choose one method — nameservers if the host runs all your DNS, A records if you need to keep email or other services where they are. Make the change once, do not fiddle with it while propagation runs, and verify the site, the padlock, and your email before calling it done. And keep that pre-change worksheet — it is the difference between a five-minute rollback and a lost afternoon.