Complete Step-by-Step Guide
How to Point a Domain to a New Host: Step-by-Step
Change your nameservers or DNS records the right way — with zero downtime and no lost email
📋 What’s in this guide
- How Domain Pointing Works
- Two Methods: Nameservers vs. DNS
- Before You Start: What to Gather
- Method 1: Changing Nameservers
- Method 2: Updating DNS Records
- How to Protect Your Email
- DNS Propagation Explained
- How to Verify Everything Worked
- Common Registrar Walkthroughs
- Troubleshooting & Common Errors
- Your Pre-Switch Checklist
You’ve signed up with a new hosting provider, your files are uploaded, and your new site is ready to go. There’s just one thing left: making your domain name actually point to it. And if you’ve never done this before, the process can feel surprisingly mysterious.
Nameservers. A records. CNAME records. Propagation. These terms get thrown around constantly, and nobody explains what they actually mean or which one you need to change. This guide does exactly that — in plain English, with real step-by-step instructions, so you can point your domain to your new host without breaking your email, without hours of downtime, and without guessing.
Whether you’re switching from one host to another, setting up a domain you bought separately, or just trying to understand what’s going on under the hood — this guide covers all of it.
1. How Domain Pointing Actually Works
Before you change anything, it’s worth understanding the system you’re working with. When someone types your domain name into a browser, a multi-step lookup process kicks off — all in a fraction of a second.
🌐 How a Domain Gets Resolved to Your Server
Here’s the key insight: your domain name is separate from your hosting. You might have bought your domain at Namecheap and your hosting at SiteGround — they don’t automatically know about each other. “Pointing” your domain means updating the DNS settings at your domain registrar to tell the internet which servers your website lives on.
There are two different places this lookup can happen. The registrar checks your domain’s nameservers — and those nameservers hold all the individual DNS records (like your A record, MX records, CNAME records, etc.). When you “point a domain to a new host,” you’re updating one or both of these layers.
2. Two Methods: Nameservers vs. DNS Records
This is the decision that trips most people up. There are two distinct ways to point your domain to a new host, and which one you choose has significant consequences — especially for your email. Let’s break them down clearly.
Method 1: Change Your Nameservers (Recommended)
Your nameservers are like the “headquarters” for all your domain’s DNS settings. When you change your nameservers to your new host’s servers, all DNS management moves to your new host. Your new host’s control panel handles everything — your website records, email records, subdomains, all of it.
Best for: people moving both their website AND their email to the new host, or who want to manage all DNS in one place.
Watch out for: if you have existing email (like Google Workspace or Microsoft 365) set up at your old host, changing nameservers will wipe those email records unless you carefully recreate them at the new host first.
Method 2: Update Individual DNS Records (A Record / CNAME)
Instead of changing where all DNS is managed, you keep your current nameservers (and all the existing DNS records) exactly where they are. You just update the specific record that controls where your website points — typically the A record for your root domain and a CNAME for www.
Best for: people who want to move their website to a new host without touching their email. This is the safest method if you have working email at your current registrar or DNS provider.
Watch out for: you need login access to wherever your DNS is currently managed (usually your registrar), and you need to know your new host’s IP address.
| Factor | Change Nameservers | Update A Record / CNAME |
|---|---|---|
| Complexity | Low — one change, host manages the rest | Medium — manual record editing |
| Email risk | Higher — can break email if not careful | Low — email records untouched |
| DNS managed by | Your new host | Your registrar / current DNS provider |
| Propagation time | 24–48 hours (sometimes up to 72) | As little as 15 min, usually <1 hour |
| Best when | Moving everything to new host | Moving website only, keeping email |
- No custom email, or a brand new site? Use Method 1 — change your nameservers. It’s simpler and lets your new host manage everything in one place.
- Have working email you can’t afford to break? Use Method 2 — update the A record only. Your email records stay completely untouched.
3. Before You Start: What to Gather
Don’t start making changes until you have all of this in hand. Five minutes of preparation now prevents hours of troubleshooting later.
From Your New Hosting Provider
- Nameservers — Usually two, formatted like ns1.newhost.com and ns2.newhost.com. Find these in your hosting welcome email or control panel under “Account Info” or “DNS Settings”.
- Server IP address — A number like 185.220.101.45. You’ll need this if you’re updating the A record instead of nameservers. Usually found in the same place as nameservers.
- CNAME value for www — Sometimes hosts want you to point www to a hostname rather than an IP. Check your host’s documentation.
From Your Current Setup
- Login credentials for your domain registrar — The company where you purchased your domain (GoDaddy, Namecheap, Google Domains/Squarespace, Cloudflare, etc.).
- Your current MX records — If you have email, write down your MX records before making any changes. You’ll need them to restore email at the new host if you switch nameservers. Go to mxtoolbox.com, enter your domain, and save the results.
- Any other DNS records you’re using — TXT records for email verification (SPF, DKIM, DMARC), CNAME records for subdomains, etc. Take a screenshot of your full DNS zone before changing anything.
Before touching a single setting, log in to wherever your DNS is currently managed and take a full screenshot of all your existing DNS records. This is your safety net. If anything goes wrong, you have a reference to restore everything exactly as it was. This takes 30 seconds and has saved countless migrations.
4. Method 1: Changing Your Nameservers
This is the most common method for moving to a new host. You’ll make this change at your domain registrar — the company where you bought your domain — not at your old or new hosting company.
Get your new host’s nameservers
Log in to your new hosting account and find the nameservers assigned to your account. They typically look like this:
ns1.siteground.com ns2.siteground.com
Common locations: your hosting welcome email, the control panel under “Account Details,” “Hosting Info,” or in a “Getting Started” section. If you can’t find them, search your host’s help docs for “nameservers” or ask support — they’re always happy to provide them.
Screenshot your current DNS records
Before changing anything, log in to your registrar and navigate to the DNS management area for your domain. Take a screenshot of every record you see — A records, MX records, TXT records, CNAME records, all of it. Pay special attention to MX records if you have email.
Recreate critical DNS records at your new host (if needed)
If you have email (Google Workspace, Microsoft 365, Zoho, etc.) and you’re switching nameservers, you need to add those MX and TXT records to your new host’s DNS zone before switching nameservers. Log in to your new hosting control panel, find the DNS Zone Editor (in cPanel: Zone Editor or DNS Zone Manager), and add each email-related record. See Section 6 for details on protecting your email.
Log in to your domain registrar and find the nameserver settings
Go to your registrar’s website and find your domain management area. The setting you’re looking for is usually labeled “Nameservers,” “DNS Nameservers,” or “Name Servers.” See Section 9 for exact paths at GoDaddy, Namecheap, Cloudflare, and Google Domains.
Replace the current nameservers with your new host’s nameservers
Most registrars show two nameserver fields. Delete the existing values and enter your new host’s nameservers exactly as provided — no trailing dots, no extra spaces, no http://. Save the change.
Before: ns1.oldhost.com ns2.oldhost.com After: ns1.newhost.com ns2.newhost.com
Wait for propagation and verify
Nameserver changes typically take 24–48 hours to fully propagate worldwide, though many users see the change in as little as 1–4 hours. While you wait, do not keep refreshing your own browser — your ISP’s DNS cache can hold old records for hours. Instead, use a propagation checker (see Section 7) to monitor progress from multiple locations.
5. Method 2: Updating DNS Records
Use this method when you want to point only your website to a new host while keeping your email and other DNS records exactly where they are. You’ll make changes in whichever DNS provider currently controls your domain — usually your registrar.
Understanding the Records You’ll Change
| Record Type | What It Controls | Example Value |
|---|---|---|
| A Record | Points your root domain (yourdomain.com) to an IP address | 185.220.101.45 |
| CNAME Record | Points a subdomain (www) to another hostname | yourdomain.com or @ |
| AAAA Record | Same as A record but for IPv6 addresses | 2001:db8::1 |
Get your new host’s IP address
Log in to your new hosting account and find the server IP address assigned to your hosting plan. This is usually displayed prominently in your control panel or welcome email. It will look like a series of numbers: 185.220.101.45. If you’re using a host that provides a hostname instead of an IP (like some managed WordPress hosts), you may need to use a CNAME record instead.
Log in to your DNS provider and find the DNS records
This is wherever your nameservers currently point. For most people, this is their domain registrar. Look for sections labeled “DNS Management,” “Advanced DNS,” “DNS Zone,” or “Manage DNS.”
Update the A record for your root domain
Find the A record where the Host (or Name) is @ or blank or your bare domain name. This controls where yourdomain.com points. Edit it and replace the existing IP address with your new host’s IP address.
Type Host Value (old) TTL A @ 203.0.113.50 3600 Change the Value to your new host's IP: A @ 185.220.101.45 3600
Update the CNAME record for www
Find the CNAME record where the Host is www. This controls where www.yourdomain.com points. The value should be your root domain (yourdomain.com or just @ depending on your registrar) — this tells www to follow wherever the A record points. Alternatively, some hosts prefer you to point www directly to their hostname.
Type Host Value TTL CNAME www yourdomain.com 3600
Lower your TTL first (optional but smart)
TTL stands for Time To Live — it’s how long DNS resolvers cache your records before checking for updates. If your TTL is set to 3600 (1 hour), it means even after you update your A record, visitors using cached DNS may reach your old server for up to an hour. If you plan ahead, lower your TTL to 300 (5 minutes) a day before making the switch, then restore it to 3600 after propagation is complete.
Save and wait for propagation
A record changes propagate much faster than nameserver changes — often within 15–60 minutes, though the full worldwide rollout can take up to a few hours. Your email will continue working without any interruption throughout this process.
When updating your A record, don’t delete it and create a new one — edit the existing record in place. Deleting an A record can cause your domain to temporarily return no result at all, which is worse than pointing to the wrong server. Find the existing A record and change its value.
6. How to Protect Your Email During the Switch
This is the section most guides skip — and it’s the reason people panic after switching hosts. If you have a custom email address (like [email protected]) set up through Google Workspace, Microsoft 365, Zoho, or your old host, you need to handle this carefully.
If You’re Changing Nameservers
Changing nameservers moves all DNS control to your new host. Your old email records don’t automatically transfer — they get replaced by whatever your new host’s default DNS zone looks like. Before flipping the switch, you need to add your existing email DNS records to your new host’s DNS zone.
The records to recreate are:
- MX records — Tell the internet which servers handle email for your domain. You’ll have 1–3 of these. Get them from mxtoolbox.com before changing anything.
- SPF record (TXT) — Tells email servers which servers are allowed to send email on your behalf. Critical for deliverability.
- DKIM record (TXT) — A cryptographic signature that proves your email is legitimate. Usually a long TXT record under a subdomain like google._domainkey.
- DMARC record (TXT) — Defines what to do with email that fails SPF/DKIM checks.
Type Host Value Priority MX @ ASPMX.L.GOOGLE.COM 1 MX @ ALT1.ASPMX.L.GOOGLE.COM 5 MX @ ALT2.ASPMX.L.GOOGLE.COM 5 MX @ ALT3.ASPMX.L.GOOGLE.COM 10 MX @ ALT4.ASPMX.L.GOOGLE.COM 10 SPF TXT record: TXT @ v=spf1 include:_spf.google.com ~all
If You’re Only Updating the A Record
Good news: you don’t need to do anything for email. Your MX records, SPF records, DKIM records, and DMARC records are all separate DNS records that you’re not touching. They stay exactly as they are. Email continues without a hiccup.
Before changing anything, send a test email to your custom address and confirm it arrives. After the switch is complete and propagation is done, send another test email. If email breaks, you have your DNS screenshot to reference and can restore the missing records quickly.
7. DNS Propagation Explained
After you make your DNS changes, you won’t see them take effect instantly — and neither will everyone else in the world at the same time. This is DNS propagation, and it confuses almost everyone the first time they encounter it.
Why Propagation Takes Time
The internet doesn’t have one central DNS server that everyone queries. Instead, there are thousands of DNS resolvers (run by ISPs, Google, Cloudflare, and others) scattered around the world, and they all cache DNS records for a period of time defined by the TTL (Time To Live) value. When you update your DNS, each resolver continues serving the old record until its cache expires — then it fetches the new record.
Propagation Timelines
| Change Type | Typical Time | Maximum |
|---|---|---|
| A Record update (low TTL, e.g. 300s) | 5–30 minutes | 1 hour |
| A Record update (default TTL, e.g. 3600s) | 30 min – 2 hours | 4 hours |
| Nameserver change | 1–24 hours | 48–72 hours |
| MX Record change | 15 min – 4 hours | 24 hours |
| TXT Record change | 15 min – 2 hours | 24 hours |
How to Check Propagation Progress
Don’t rely on your own browser — it’s almost certainly caching old records. Use these tools instead to check propagation from dozens of locations around the world simultaneously:
- whatsmydns.net — The most popular tool. Shows your A record, MX record, and nameservers from locations worldwide. Green checkmarks mean the update has reached that location.
- dnschecker.org — Similar to whatsmydns but with a different server network. Good to cross-reference.
- Google Admin Toolbox (toolbox.googleapps.com/apps/dig/) — Especially useful for checking email (MX) records.
Even after propagation is complete, your browser may still show the old site because your operating system or ISP has cached the old DNS record. To force a fresh lookup: clear your browser cache, try a different browser, use incognito/private mode, or check your site from your phone on mobile data (which uses different DNS resolvers than your home WiFi).
8. How to Verify Everything Worked
Once propagation is underway (or complete), here’s how to confirm your domain is pointing correctly and everything is working as expected.
Verify Your Website Is Loading
- Open your site in an incognito/private browser window (bypasses browser cache)
- Check both yourdomain.com and www.yourdomain.com — both should load your new site
- Check that HTTPS works — the padlock should appear in the address bar
- Navigate through a few pages to confirm there are no broken links or missing assets
Verify with Command Line (Advanced)
If you’re comfortable with the terminal, dig and nslookup give you authoritative DNS information that bypasses local caching:
# Check A record (Mac / Linux) dig yourdomain.com A # Check nameservers dig yourdomain.com NS # Check MX records (email) dig yourdomain.com MX # Windows equivalent nslookup yourdomain.com
The IP address in the answer section of dig yourdomain.com A should match your new host’s IP address. If it still shows the old IP, propagation hasn’t reached your network yet.
Verify Your SSL Certificate
After pointing to a new host, you’ll need to ensure SSL is set up there. Most hosts provision a free Let’s Encrypt certificate automatically once the domain is pointing correctly. If you see a browser warning about an invalid certificate after propagation is complete, log in to your new hosting control panel and look for an “SSL” section to activate or reissue the certificate.
Verify Email Is Still Working
Send a test email to your custom domain address (from Gmail or another external email) and confirm it arrives. Then send a test reply out from your custom address and confirm it’s received. If email is broken, check your MX records using mxtoolbox.com and compare against your pre-switch screenshot.
9. Common Registrar Walkthroughs
Every registrar’s interface is different. Here are the exact navigation paths for the most popular ones.
GoDaddy
To change nameservers: Log in → My Products → Domains → click your domain → DNS → Nameservers → Change → select “Enter my own nameservers” → enter new nameservers → Save.
To update DNS records: Log in → My Products → Domains → click your domain → DNS → scroll to Records → find the A record → click the pencil/edit icon → update the value → Save.
Namecheap
To change nameservers: Log in → Domain List → click Manage next to your domain → find the Nameservers section → change the dropdown from “Namecheap BasicDNS” to “Custom DNS” → enter your nameservers → click the green checkmark to save.
To update DNS records: Log in → Domain List → Manage → Advanced DNS tab → find your A record under Host Records → click the edit icon → update the IP → Save.
Cloudflare
Note: If your domain is on Cloudflare, Cloudflare acts as both your registrar and your DNS. You’ll almost never need to change nameservers away from Cloudflare — instead, update the A record directly in Cloudflare’s DNS tab.
To update DNS records: Log in → select your domain → DNS → Records → find the A record with name “@” → click Edit → update the IPv4 address → Save. Make sure the Proxy Status (orange cloud) is set how you want it — “Proxied” means traffic routes through Cloudflare’s network; “DNS only” means it goes directly to your server.
Google Domains / Squarespace Domains
To change nameservers: Log in → My Domains → click your domain → DNS → at the top, you’ll see “Google Domains nameservers” — switch to “Custom name servers” → enter your new host’s nameservers → Save.
To update DNS records: Log in → My Domains → DNS → scroll to “Custom records” → find your A record → click the pencil icon → update the value → Save.
Registrar interfaces change frequently. If these paths don’t match what you’re seeing, search your registrar’s help center for “change nameservers” or “edit DNS records” — they all have documentation. Alternatively, search “[registrar name] change nameservers 2026” and you’ll find up-to-date screenshots.
10. Troubleshooting & Common Errors
Something didn’t go as planned? Here are the most common problems and exactly how to fix them.
“Site Can’t Be Reached” After the Switch
The most common cause is simply that propagation isn’t complete yet. Check whatsmydns.net to see if the new IP is showing up. If it is showing the new IP but the site still won’t load, the issue is likely on your new host — confirm that your domain is actually added to your hosting account (in cPanel, look for it under “Addon Domains” or “Domains”), and that your website files are in the correct directory.
SSL Certificate Warning (“Not Secure”)
After pointing to a new host, SSL needs to be provisioned there. Log in to your new hosting control panel and look for an SSL section. Most hosts have an “AutoSSL” or “Let’s Encrypt” option that will issue a free certificate within a few minutes once the domain is pointing correctly. If provisioning fails, it’s usually because propagation isn’t complete yet — the certificate authority needs to be able to reach your domain at the new host to verify it.
Email Stopped Working
If you changed nameservers, your MX records may not have transferred. Check your MX records at mxtoolbox.com and compare them to your pre-switch screenshot. Add any missing MX records, SPF records, and DKIM records to your new host’s DNS zone editor. Changes to MX records can take up to 24 hours to propagate, so be patient after adding them.
www Works But the Root Domain Doesn’t (or Vice Versa)
This means only one of your records was updated correctly. Check both your A record (for the root domain, @) and your CNAME or A record for www separately. Common cause: updating www but forgetting the root, or vice versa. Make sure both are pointing to the correct IP or hostname.
Domain Still Showing Old Site After 48 Hours
If whatsmydns.net shows the new IP everywhere but you’re still seeing the old site, it’s a local caching issue. Try: clearing your browser cache and cookies, opening a private/incognito window, checking on a different device or network, or flushing your OS DNS cache (on Mac: sudo dscacheutil -flushcache; on Windows: ipconfig /flushdns).
Registrar Won’t Let You Change Nameservers
Two likely causes: (1) your domain is locked — look for a “Domain Lock” or “Transfer Lock” setting and disable it first, then try again; or (2) your domain registration expired — renew it before making any changes. Some registrars also prevent nameserver changes for 60 days after initial registration or an account change.
11. Your Pre-Switch Checklist
Run through this before making any DNS changes. Everything on this list takes minutes to do and prevents hours of potential problems.
Before Making Any Changes
- Confirm your new hosting account is active and your site files are uploaded and working
- Get the nameservers OR server IP address from your new host (have these ready)
- Log in to your domain registrar and confirm you have access
- Screenshot your entire DNS zone (every single record)
- Check and record your current MX records at mxtoolbox.com
- Decide: changing nameservers or updating A record only?
- Lower your TTL to 300 on the A record if you want faster propagation (do this 24 hours before)
If Changing Nameservers
- Add all email-related records (MX, SPF, DKIM, DMARC) to new host’s DNS zone first
- Confirm your domain is added to your new hosting account
- Update nameservers at your registrar to your new host’s nameservers
- Monitor propagation at whatsmydns.net
If Updating A Record Only
- Get the new host’s server IP address
- Edit (not delete) the existing A record for @ and update the IP
- Update the CNAME record for www if needed
- Monitor propagation at whatsmydns.net
After Propagation Is Complete
- Confirm site loads on both yourdomain.com and www.yourdomain.com
- Confirm HTTPS / SSL is working (padlock in browser)
- Send and receive a test email to your custom domain address
- Test contact forms and any other dynamic functionality
- Restore your TTL to 3600 if you lowered it
- Keep your old hosting account active for 7–14 days as a backup, then cancel
Your Domain Is in
the Right Place Now.
Pointing a domain to a new host looks intimidating the first time, but once you understand the difference between nameservers and DNS records, the whole process becomes logical and manageable. The most important habits are simple: screenshot your DNS before changing anything, protect your email records, and use propagation tools instead of refreshing your browser compulsively.
Most switches go completely smoothly. And for the ones that don’t, every problem has a clear cause and a clear fix — usually a missing record or a cache that just needs time to clear.
If you’re switching hosts entirely, check our guide on migrating your website files and database too — DNS is only half of the picture.
Your domain, your host, your rules.
Make the change with confidence.