To point a domain to your hosting, make one of two DNS changes. Method A: change the domain’s nameservers to your host’s nameservers, which hands all DNS to the host. Method B: keep DNS at the registrar and edit the A record to point at your host’s IP address, add a CNAME for www, and keep your MX records for email. Then wait for propagation (up to 24–48 hours, usually faster) and verify by loading the site. Registrar control panels differ, so the labels below are generic.
A domain and a web host are two separate things — if that distinction is new, our explainer on domain name vs web hosting sets it up. “Pointing” the domain simply means editing its DNS so the name resolves to the server holding your site. There are two standard ways to do it, and you only need one. Choosing between them is mostly about where you want your DNS records to live.
Method A: change the nameservers
Changing nameservers is the simplest route and the right one when a single provider runs your whole site. You delegate all of the domain’s DNS to your host, which then manages every record for you.
- Get your host’s nameservers. They look like
ns1.examplehost.comandns2.examplehost.comand are listed in your hosting account or welcome email. - Log in at your registrar and find the domain’s nameserver settings (often under “DNS”, “Nameservers” or “Manage domain”).
- Replace the existing nameservers with the ones your host gave you, then save.
- Wait for propagation and verify (see below).
The catch with Method A is that the host’s DNS now controls everything, including email. If your mailboxes are hosted elsewhere, make sure the host’s DNS includes the correct MX records or email will stop arriving. For the wider mechanics of nameserver delegation, see what a name server is and our guide on changing nameservers.
Method B: edit the A record (and friends)
Method B keeps DNS at the registrar and points only the parts you choose. It is the better option when you want some records to stay where they are — commonly email — while sending just the website to a new host.
- Get your host’s IP address (for the A record) from your hosting account.
- Open the DNS / zone editor at your registrar.
- Set the A record for the bare domain (host
@) to your host’s IP address. - Add the
wwwversion — usually a CNAME pointingwwwat your root domain (or a second A record to the same IP). - Leave the MX records alone so email keeps working, unless your host’s instructions say otherwise.
- Save, wait for propagation and verify.
| Method A: nameservers | Method B: A record | |
|---|---|---|
| What you change | The domain’s nameservers. | Individual DNS records at the registrar. |
| Who manages DNS | Your host. | You, at the registrar. |
| Best when | One provider runs the whole site. | You want to keep some records (e.g. email) put. |
| Effort | Lowest — one change. | A few records to set correctly. |
| Email risk | Must replicate MX at the host. | Existing MX stays untouched. |
Records in plain English
An A record maps your name to an IPv4 address (an AAAA record does the same for IPv6). A CNAME makes one name an alias of another — how www usually follows the bare domain. MX records say which mail servers handle your email. Pointing a website touches the A record (and CNAME); leaving email working means leaving MX correct. See how domain name resolution works for the lookup behind these.
Propagation, verification and common mistakes
Propagation is the wait while the change spreads across the internet. Allow up to 24–48 hours, though it is frequently much faster — minutes to a few hours. The delay exists because resolvers cache the old records until their time-to-live expires. Make the change once and be patient; repeatedly re-editing records only resets the clock.
To verify, load the domain in a fresh browser or a private window once propagation has had time, and check the live records with an online DNS-lookup tool — the nameservers or A record should now show your host’s values. If the correct page loads and the records match what your host provided, you are done.
The four classic mistakes
1. A typo in the IP address — one wrong digit in the A record and nothing loads. 2. Forgetting the www CNAME or A record, so the bare domain works but www. does not (or vice versa). 3. Breaking email by deleting or omitting MX records when switching nameservers. 4. Not waiting for propagation and assuming it failed. Check every value against your host’s instructions, then give it time.
Registrar UIs differ — the concepts do not
Every registrar labels things slightly differently — “DNS management”, “Zone editor”, “Advanced DNS”, “Nameservers”. The underlying actions are the same everywhere: swap nameservers, or edit A/CNAME/MX records. If you cannot find a setting, search your registrar’s help for “nameservers” or “DNS records” and the generic steps above will map onto their screen.
★ Key takeaways
- Method A: change nameservers to your host — simplest, hands all DNS to the host (replicate MX so email survives).
- Method B: keep DNS at the registrar and set the A record to the host’s IP, add a CNAME for www, leave MX alone.
- Propagation can take up to 24–48 hours but is usually faster; make the change once and wait.
- Avoid the classics: a mistyped IP, a missing
wwwrecord, broken MX, and not waiting before troubleshooting.
Frequently asked questions
Should I change nameservers or edit the A record?
Both work. Changing nameservers to your host’s nameservers is simplest — it hands all DNS to the host, which manages the records for you, and is ideal when one provider runs the whole site. Editing the A record keeps DNS at the registrar and points only the website at the host’s IP, which is better when you want to keep some records (such as email) elsewhere. Pick one method; do not mix them for the same purpose.
How long does DNS propagation take?
DNS changes can take up to 24 to 48 hours to propagate worldwide, though in practice it is often much faster — sometimes minutes to a few hours. The delay happens because resolvers around the internet cache the old records until their time-to-live expires. Make the change once and wait; repeatedly editing records only resets the clock and adds confusion.
How do I verify the domain is pointing to my hosting?
Wait for propagation, then load the domain in a fresh browser or private window. You can also check the live DNS records with an online DNS-lookup tool to confirm the nameservers or A record now show your host’s values. If the right page loads and the records match what your host gave you, the domain is pointing correctly.
Will pointing my domain to hosting break my email?
It can if you are not careful. If you change nameservers to your host, make sure the host’s DNS includes the correct MX records for your email, or email will stop arriving. If you keep DNS at the registrar and only edit the A record, your existing MX records are untouched. Always confirm MX is correct before and after the change.
What are the most common mistakes when pointing a domain?
The usual culprits are a mistyped IP address in the A record, forgetting the CNAME (or second A record) for the www version so only the bare domain works, deleting or omitting the MX records and silently breaking email, and not waiting for propagation before deciding something is wrong. Double-check each value against what your host provided and give the change time to take effect.
Sources & further reading
- ICANN — Internet Corporation for Assigned Names and Numbers (DNS and domain administration)
- IANA — Root Zone Database (which registry operates each extension)
- Related: tlddomain.us home, how to change domain nameservers, domain name vs web hosting, what is a name server?, how domain name resolution works, what is DNS?, how to register a domain name