How to Point Your Domain Name to a New Web Host (DNS Records Guide)

You have bought your shiny new domain name (e.g., mybusiness.co.uk) from one provider.

You have purchased a superfast hosting plan from another.

Then, when you type your domain into Chrome, expecting to see your new website. Instead, you see a generic page that says “This domain is parked” or “Site Not Found.”

The Problem: Your domain name doesn’t know where your website lives.

The Solution: You need to build a bridge between them using DNS.

Connecting a domain to a host is the digital equivalent of forwarding your post when you move house. It is a fundamental skill for any website owner, yet it scares people more than any other technical task.

In this guide, we will strip away the fear. We will explain exactly how the “Phonebook of the Internet” works, and walk you through the two methods to point your domain to your new server without breaking your email.

Understanding the “Phonebook” (DNS Explained)

Before you start clicking buttons, you need to understand what you are actually doing.

DNS stands for Domain Name System.

Computers do not understand words like google.com. They only understand numbers, specifically IP Addresses (e.g., 142.250.187.206).

Your Domain Registrar (where you bought the name) holds a “Address Book” for your domain.

• Right now: Your domain’s address book is blank (or points to a parking page).
• The Goal: We need to write the IP address of your new web host into that address book.

Once you do this, when someone types mybusiness.co.uk, the registrar looks up the number and connects them to your web host.

The Two Methods: Which One Do You Need?

There are two ways to connect your domain. Choosing the wrong one can break your professional email, so read this carefully.

Method 1: Changing Nameservers (The “All-In” Approach)

• What it does: You hand over total control of your domain’s settings to your web host.
• Best For: Beginners, new websites, and people who want their host to manage everything (Website + Email).
• Difficulty: Very Easy.

Method 2: Pointing via A Record (The “Surgical” Approach)

• What it does: You keep control at your registrar but point only the website traffic to the new host.
• Best For: People who have professional email (like Google Workspace or Office 365) set up and don’t want to break it.
• Difficulty: Medium.

Warning: If you have custom email set up (e.g., you@yourdomain.co.uk) and you use Method 1 without planning, your email will stop working instantly. If in doubt, ask your IT support or use Method 2.

Method 1: Changing Nameservers (Recommended for Beginners)

This is the most common method. It effectively says to your registrar: “I don’t want you to manage my DNS anymore. Let my Web Host handle everything.”

Step 1: Find Your New Nameservers

When you signed up for hosting, you received a “Welcome Email”. Inside, you will find two (sometimes four) lines of text that look like this:

• ns1.encode.host
• ns2.encode.host
• ns3.encode.host

OR

• ns1.bluehost.com
• ns2.bluehost.com

Copy these. These are the addresses of your new host’s “Address Book.”

Step 2: Log in to Your Registrar

Go to the company where you bought your domain (e.g., Namecheap, GoDaddy, 123-Reg).

• Namecheap: Go to “Domain List” -> Click “Manage” next to your domain.
• GoDaddy: Go to “My Products” -> “DNS” -> “Nameservers”.
• 123-Reg: Go to Control Panel -> “Change Nameservers”.

Step 3: Select “Custom DNS”

By default, your domain will be set to “Basic DNS” or “Default Nameservers.”

Change this setting to “Custom DNS” (or “Use My Own Nameservers”).

Step 4: Paste and Save

You will see two empty boxes (Line 1 and Line 2).

• Paste ns1.yourhost.com into box 1.
• Paste ns2.yourhost.com into box 2.
• Click Save (usually a green tick or a “Save” button).

Success! You have now told the internet that your web host is in charge.

Method 2: Pointing via A Record (For Email Safety)

Use this method if you have important emails set up on your domain (e.g. via Microsoft 365) and you are terrified of breaking them. By using an A Record, you only move the website, leaving the email settings untouched.

Step 1: Find Your Host’s IP Address

Log in to your new web hosting dashboard (cPanel/Site Tools).

Look for a section called “Server Information” or “Account Details.”

You need the Shared IP Address. It will look like: 185.33.22.10. Copy this.

Step 2: Go to Your Registrar’s DNS Zone

Log in to your registrar (Namecheap/GoDaddy) and find “Advanced DNS” or “DNS Management”.

Do not change the Nameservers (leave them as Default).

Step 3: Edit the “@” Record

Look for a list of records. You want to find the one where:

• Type: A Record
• Host: @ (This symbol means “the root domain”, i.e., mybusiness.co.uk)
• Value/Target: (This will be an old IP address or “Parked”).

Click Edit on this record.

Delete the old IP address and paste your NEW Host’s IP address (from Step 1).

Click Save.

Step 4: Check the “www” Record (CNAME)

You also want www.mybusiness.co.uk to work.

Look for a record where:

• Type: CNAME
• Host: www
• Value: @ (or your domain name).

If this exists, you are good. It basically says “Whatever happens to the main domain (@), do the same for ‘www’.”

The Waiting Game: Understanding Propagation

You clicked save. You typed in your domain. And… nothing changed. Or maybe you see an error.

Do not panic. You are experiencing DNS Propagation.

The “Village Gossip” Analogy

Imagine you move house. You tell the Post Office your new address.

• Hour 1: Only the local Post Office knows.
• Hour 4: The main sorting centre finds out.
• Hour 24: Postmen in other cities finally get the updated list.

The internet works the same way. There are thousands of DNS servers across the world (ISPs). They cache (remember) your old address for a few hours to save time. It takes time for the news of your move to spread from your Registrar to Virgin Media, BT, Sky, and AT&T.

How long does it take?

• Usually: 1 to 4 hours, but could be as quick as 15–20 minutes.
• Maximum: Up to 48 hours.

How to Check Propagation

Do not just keep refreshing your browser (your computer caches the old site too).

Use a tool called Whatsmydns.net.

1. Type in your domain.
2. Select “A” or “NS” from the dropdown.
3. Click Search.

You will see a map of the world.

• Red Cross: That country still sees the old host.
• Green Tick: That country sees the new host.

When most of the map is green, your migration is complete.

Troubleshooting: Common Issues

1. “My Email Stopped Working!”

Cause: You used Method 1 (Nameservers) but didn’t recreate your email accounts on the new host, OR you forgot to copy your MX Records (for Google/Microsoft email).

Fix:

• If using host email: Log in to your new cPanel and create the email accounts immediately.
• If using Google/Microsoft: Log in to your new host’s “DNS Zone Editor” and add the “MX Records” provided by Google/Microsoft.

2. “I Can’t See the New Site, but My Friend Can”

Cause: Your local computer or Wi-Fi network remembers the old IP address (Local Cache).

Fix:

• Try looking at your site on your phone (turn off Wi-Fi, use 4G/5G).
• If it works on 4G, the problem is your computer.
• Action: Clear your browser cache or Flush your DNS.

3. “Not Secure” / SSL Error

Cause: You pointed the domain, but the new host hasn’t issued an SSL certificate yet.

Fix:

• Wait 1 hour. Most modern hosts automatically detect the DNS change and issue a Let’s Encrypt certificate.
• If it takes longer, log in to your hosting panel and click “Force HTTPS” or “Re-issue SSL.”

Summary Checklist

1. [ ] Choose: Nameservers (Easy) or A Record (Advanced)?
2. [ ] Copy: Get the Nameservers or IP Address from your new host.
3. [ ] Paste: Update settings at your Domain Registrar.
4. [ ] Wait: Allow 1–4 hours for propagation.
5. [ ] Test: Use Whatsmydns.net to confirm the world sees the new site.
6. [ ] Secure: Ensure SSL is active on the new host.

Congratulations! You have successfully navigated the most technical aspect of setting up a website. Your domain and hosting are now talking to each other, and you are ready to launch.

Have you struggled with DNS? Let us know in the comments