How to Connect Your Domain to Your Website (Nameservers and DNS Records)

The Short Answer

Connecting a domain to your website means telling the internet which server should answer when someone types your domain. You do this one of two ways: point your domain's nameservers at your host, or leave your registrar's nameservers in place and add DNS records that point to your host. Either works; which you use depends on where you want to manage DNS.

The change itself is simple. The only thing that catches people out is propagation — the delay before it takes effect everywhere.

First, the Vocabulary

Registrar — where you bought the domain (Namecheap, EuroDNS, Dynadot). Our registrar rankings cover the options.

Host — where your website's files actually live. See our best web hosting guide.

Nameservers — the DNS servers that hold the authoritative records for your domain and answer "where does this domain point?"

DNS records — the individual instructions. The two that matter for connecting a site are the A record (points a domain to an IP address) and the CNAME (points a name to another name). Our DNS explained guide goes deeper.

Method 1: Point Your Nameservers at Your Host

Your host gives you two or more nameservers (often something like ns1.yourhost.com). You log into your registrar, replace the default nameservers with your host's, and save.

From then on, your host manages all DNS for the domain. This is the simplest method for beginners because the host handles the records for you — and many builders and managed hosts, like 10Web or Bluehost, configure everything automatically once the nameservers point their way.

Use this when: you want your host to manage DNS and you do not need registrar-side email or other records.

Method 2: Keep Registrar DNS and Add Records

Leave the registrar's nameservers in place and add records manually:

• An A record for your root domain (the "@" or blank host) pointing to your host's IP address.
• A CNAME for "www" pointing to your root domain.

This keeps DNS management at your registrar, which is convenient if you also run email or other services there and want everything in one panel.

Use this when: you want to manage DNS at the registrar, or you route the domain through a CDN.

The Step-by-Step

1. Get the target from your host — either its nameservers (Method 1) or the server IP address (Method 2). 2. Log into your registrar and open the domain's DNS or nameserver settings. 3. Apply the change — swap the nameservers, or add the A and CNAME records. 4. Wait for propagation. DNS changes can take anywhere from a few minutes to 24-48 hours to reach every network worldwide, though most complete within an hour or two. 5. Verify. Once propagated, your domain loads your site. Add SSL and force https — our SSL certificate guide explains how.

Common Pitfalls

Impatience. If the site does not load immediately, that is usually propagation, not a mistake. Give it time before changing anything else.

Editing DNS in two places. If you switch nameservers to your host (Method 1), records you add at the registrar no longer apply. Manage DNS in one place only.

Forgetting email. If you move nameservers to a new host, your MX (mail) records move too. If you use email on the domain, re-create the MX records at the new host or your mail stops. Setting up email? Spaceship's email hosting is an example of a tidy registrar-side option.

Not doing www and root. Configure both the root domain and the www version so visitors reach you either way.

If You Are Starting from Scratch

If you have not registered the domain yet, do that first — our tutorial on registering your first domain walks through it — then come back here to connect it. And if you are still choosing a name, our how to choose a domain name guide is the place to begin.

The Bottom Line

Connecting a domain to a site is a five-minute task followed by a waiting game. Pick one method — nameservers for simplicity, registrar DNS records for control — apply it in one place, and let propagation finish. Then add SSL, confirm both www and root resolve, and you are live.

For keeping the connection private on the networks you manage your registrar and host from, our sister site vpntex.com covers the VPN side.