Connect a Domain to Your Website

Good to Know:

This page does not list prices. Registration and renewal prices change, so the search result and the checkout page show the current price for the name you choose. Nothing here is a quote or an offer.

A domain can be registered in one place, hosted in another and managed by a third. DNS is the set of instructions that connects them. Understanding two concepts, nameservers and records, is enough for most site launches.

The short answer

Use nameservers when the host manages all of your DNS. Use individual records when you need to keep email or other services with a different provider.

Follow the host's exact values. 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.

Nameservers versus DNS records

Approach	What it does	When to use it
Nameservers	Delegates the whole DNS zone to the host	The host manages the site, email and all records
A / AAAA records	Point the domain or a subdomain at an IP address	The host gives you an IP and you keep DNS elsewhere
CNAME	Aliases one name to another	A hosted service or a www subdomain
MX	Routes email to a mail provider	Email is separate from the website host
TXT	Holds verification and email authentication values	Domain verification, SPF, DKIM

Connect the domain, step by step

Get the nameserver values or the exact DNS records from the host.
Sign in to the registrar or DNS provider that controls the domain.
If you are using nameservers, replace the current values with the host's values.
If you are using records, add or edit the A, CNAME and other records the host specified.
Save the changes and note the time.
Wait for propagation, then test the domain in a private window.
Turn on HTTPS and confirm the certificate is active.

The records you are likely to edit

Record	What it does	Typical use
A	Maps a name to an IPv4 address	The main website
AAAA	Maps a name to an IPv6 address	The main website over IPv6
CNAME	Points one name to another name	www, or a hosted service
MX	Routes email to a mail server	Professional email
TXT	Stores text values	Domain verification, SPF, DKIM
NS	Delegates the zone to nameservers	Host-managed DNS

Do not delete a record you do not understand. Email and verification records often sit alongside the website records, and removing one can break a service that was working.

Propagation and caching

DNS changes are cached for a period set by the TTL. That is why a change can look instant for one person and take hours for another.

Lower the TTL before a planned migration if your provider allows it.
Do not change the records repeatedly while you wait. You will not know which version is live.
Test with a DNS lookup tool and a private browser window.
Old records can linger in local caches even after the authoritative answer changes.
If email is involved, check MX records separately from the website.

HTTPS and the www question

An SSL certificate is separate from the DNS record, although the host often issues it automatically once the domain points correctly. If HTTPS does not work after DNS is live, the certificate may still be pending.

Decide whether the canonical address is the root domain or www, then redirect the other one.
Test both versions and confirm they show the same site.
Check that the certificate covers the version you use.
Do not leave a padlock warning on the address you print.
Recheck HTTPS after any DNS or hosting change.

Troubleshooting

Symptom	Likely cause
The domain does not resolve at all	Wrong nameservers, a missing A record or propagation still in progress
The host’s default page appears	The A record points at the wrong server
Only www works, or only the root works	One of the two records is missing
Email stopped after the site went live	MX records were replaced or removed
The certificate warning persists	SSL is not issued, or DNS does not point at the host yet
An old site still appears	DNS or browser cache is serving the previous record

Launch checklist

DNS records exported or screenshotted before the change.
Nameservers or records match the host's instructions exactly.
Root and www both load, with one redirecting to the other.
HTTPS is active and the certificate matches the domain.
Email sends and receives after the change.
The site loads on a phone and in a private window.
The old domain, if any, redirects to the new one.
A reminder to recheck DNS and SSL in 24 hours.

Frequently asked questions

Do I need to transfer my domain to connect a website?

No. You can keep the domain at one registrar and host the site elsewhere. You only need to update the nameservers or DNS records.

Should I use nameservers or A records?

Use nameservers when the host manages all of your DNS. Use individual records when email or another service stays with a different provider.

How long does DNS propagation take?

It depends on the TTL and the resolver. Some changes appear in minutes; others take hours. Plan for up to 48 hours and avoid changing records repeatedly while you wait.

Why does my site show the host’s default page?

The domain is pointing at the host, but the A record or the site mapping is not correct. Check the host's exact values and confirm the domain is added to the hosting account.

Will changing DNS break my email?

It can if you replace MX records or delegate to nameservers that do not include them. Save the current records first and confirm the mail settings with your email provider.

Is an SSL certificate included with DNS?

No. SSL is separate, although many hosts issue it automatically after the domain points correctly. Check the certificate status after propagation.

Can I connect a domain before the site is ready?

Yes, but visitors will see whatever is at the destination. Use a holding page or keep the DNS pointed at a parking page until the site is ready.

General information:

A guide, not a guarantee. This page is general information to help you compare options. It is not legal, financial or tax advice, and it is not a promise that a name is available, that a price will hold, or that a registry rule will stay the same. Confirm current details in the search tool before you register.

Last reviewed: 2026-10-19. This page describes current practice and general information. Prices and registry policies can change.

How to connect a domain to a website