If you have purchased new web hosting but your domain is still connected to your old hosting provider, your website will not automatically appear on the new server. You need to connect the domain to the new hosting account, and one of the simplest ways to do that is by changing the domain nameservers.
This guide explains How to Point Domain to New Hosting (Nameserver Change Guide) step by step, including what nameservers are, how to find them, how to change them at popular domain registrars, what happens to email, how long DNS propagation takes, and what to check if your website does not work after the change. The basic process is similar across many hosting companies, although the exact dashboard labels can differ.
What Does Pointing a Domain to New Hosting Mean?
When you purchase a domain and hosting from different companies, they are two separate services. Your domain name is the address visitors type into their browser, while your web hosting is where your website’s files, database, images, and other resources are stored. DNS acts like an Internet address book, connecting a human-readable domain name with the technical destination used by computers.
For example, imagine that you bought example.com from one registrar but purchased hosting from another company. The domain may still be using DNS settings associated with the old provider. Even though your website has been uploaded to the new server, visitors can continue being sent somewhere else because the domain has not yet been directed to the new hosting environment. Pointing the domain to new hosting tells DNS which provider should answer queries for that domain.
Changing nameservers is commonly used because it lets the new hosting or DNS provider manage the domain’s DNS zone. Once the correct nameservers are active, records such as the website’s A record can be managed through the new DNS provider. This is why understanding How to Point Domain to New Hosting (Nameserver Change Guide) is important when migrating a website.
Domain, Hosting, and Nameservers Explained
Think of your website as a physical shop. The domain is the shop’s street address, the hosting server is the building where the shop actually exists, and DNS is the system that tells people where to find it. If you move the shop to another building but keep giving customers the old address, they will obviously arrive at the wrong place. Changing the DNS configuration is essentially updating the Internet’s directions.
Your domain registrar is the company where you manage the domain registration. Your hosting provider supplies the server where your website runs. Nameservers tell the wider DNS system which servers are authoritative for your domain’s DNS information. When you replace the old nameservers with those supplied by your new provider, DNS resolvers gradually begin using the new DNS authority.
This distinction is especially useful for beginners because people often think buying hosting automatically connects a domain. Sometimes it does, particularly when the domain and hosting are purchased together from the same provider. But when they are purchased separately, you generally need to connect them manually. Some providers offer nameserver changes, while others allow you to keep your existing DNS provider and simply change an A record instead.
What Are Nameservers and How Do They Work?
Nameservers are DNS servers responsible for telling DNS resolvers where the authoritative DNS information for a domain can be found. A hosting company may provide values that look something like ns1.examplehost.com and ns2.examplehost.com. These are examples only; you should always use the exact nameservers supplied by your hosting provider.
When somebody enters your domain into a browser, the browser does not simply guess which server contains your website. DNS resolution takes place behind the scenes. The DNS hierarchy eventually leads the resolver to the authoritative nameservers for your domain, which can then provide records such as the IP address associated with your website.
This is why changing nameservers can effectively move DNS management from one provider to another. The domain registration itself does not necessarily move. You are simply changing which nameservers are authoritative for the domain. That distinction is important because changing nameservers is not the same as transferring your domain registration.
Nameservers vs DNS Records
Nameservers and DNS records are related, but they are not the same thing. Nameservers determine which DNS provider is authoritative, while individual DNS records provide specific instructions about services associated with your domain.
Common DNS records include:
| Record | Main purpose |
|---|---|
| A | Points a hostname to an IPv4 address |
| AAAA | Points a hostname to an IPv6 address |
| CNAME | Creates an alias to another hostname |
| MX | Specifies mail servers for email |
| TXT | Stores text-based verification and email/security information |
| NS | Identifies authoritative nameservers |
If you change nameservers, the DNS zone managed by the new provider becomes important. Existing DNS records at the previous provider may not automatically transfer. Namecheap specifically warns that changing nameservers replaces the current DNS configuration, which can affect websites, email services, and custom DNS records.
Things to Check Before Changing Nameservers
Before starting How to Point Domain to New Hosting (Nameserver Change Guide), do not immediately delete your old DNS settings. First, make sure your new hosting account is ready and your website files have been uploaded correctly. If you are migrating an existing WordPress website, confirm that the database, media files, themes, plugins, and configuration are working on the new server before sending visitors there.
You should also check whether your domain uses email services such as Google Workspace, Microsoft 365, or another provider. Email depends heavily on DNS records, particularly MX, TXT, SPF, DKIM, and DMARC records. When nameservers change, those records need to exist correctly in the new DNS zone. Hostinger also recommends reviewing MX, SPF, DKIM, and DMARC records when changing nameservers if email is handled by a different provider.
Back Up Your Existing DNS Records
This is one of the most important steps. Before changing nameservers, make a list or screenshot of your current DNS records.
Pay particular attention to:
- A records
- CNAME records
- MX records
- TXT records
- SPF records
- DKIM records
- DMARC records
- Any custom subdomains
Why does this matter? Imagine changing the nameservers and then discovering that your website works but your business email has stopped receiving messages. The problem may not be the hosting server at all; it could simply be that the required MX records were not recreated in the new DNS zone. Taking a few minutes to document the old configuration can save hours of troubleshooting later.
How to Find Your New Hosting Nameservers
Your new hosting company normally provides the nameserver values inside your hosting dashboard, setup email, documentation, or account information. The exact location depends on the provider. For example, Hostinger’s current instructions say users can find the nameservers through the hosting account and use those values when connecting a domain registered elsewhere.
You might see something similar to:
Nameserver 1: ns1.examplehost.com
Nameserver 2: ns2.examplehost.comDo not copy these example values into your domain settings. They are only illustrations. Always use the exact nameservers shown by your current hosting provider.
Some hosting companies provide two nameservers, while others may provide three or more. If your registrar displays four fields but your host supplies only two nameservers, Hostinger’s guidance says you can generally enter the supplied nameservers and leave unused fields empty.
How to Point Domain to New Hosting Step by Step
Now let’s go through the actual process. The following method works conceptually for most domain registrars, although buttons and menu names may be different.
Step 1 — Log In to Your Domain Registrar
First, log in to the company where your domain is registered. This could be a domain registrar or another service that manages your domain.
Open your Domain Management, My Domains, Domain List, or similar section. Select the domain you want to connect to your new hosting account.
Make sure you are editing the correct domain. If you manage multiple websites, it is surprisingly easy to change the DNS settings for the wrong domain. Before saving anything, double-check the domain name and confirm that the domain is active and not expired or suspended. Hostinger similarly recommends confirming domain ownership, active status, and access to DNS settings before connecting a domain.
Step 2 — Open Nameserver Settings
Look for an option such as Nameservers, DNS Settings, Manage DNS, or Change Nameservers.
The exact interface differs between registrars. For example, Hostinger’s current guide describes a nameserver-management workflow, while Namecheap places the setting under its domain management interface.
You may see your current nameservers displayed like:
Current Nameserver 1: old-ns1.example.com
Current Nameserver 2: old-ns2.example.comAt this point, do not change anything until you have confirmed the new nameservers from your hosting provider.
Step 3 — Replace Old Nameservers
Select the option to use Custom Nameservers or Custom DNS, depending on your registrar.
Remove the old nameservers and enter the new values supplied by your hosting company.
For example:
Nameserver 1: ns1.newhost.example
Nameserver 2: ns2.newhost.exampleAgain, these are placeholders, not actual nameservers.
Make sure you copy the nameservers exactly. A small spelling mistake can prevent DNS resolution. If your hosting provider supplies two nameservers, use those two. If it supplies additional nameservers, follow the provider’s specific instructions rather than inventing additional values.
Step 4 — Save and Verify the Change
Click Save, Update, Apply, or the equivalent button. Some registrars may ask you to confirm the change through another screen or security verification.
After saving, do not panic if your website does not immediately open from every device. DNS changes are distributed through a global network of resolvers and caches, so different users may temporarily receive different results.
Your job now is to verify that the nameserver change was accepted and that the new DNS provider contains the correct records. The change itself may be quick, but propagation can take considerably longer depending on caching and the provider involved. Current guidance from Namecheap says nameserver changes can take up to 24–48 hours worldwide, while Hostinger says propagation can take up to 24 hours in its general nameserver guidance.
What Happens After Changing Nameservers?
After you change the nameservers, DNS resolvers gradually learn that your domain’s authoritative DNS servers have changed. During this period, some visitors may reach the new server while others may temporarily reach the old server or receive cached DNS information.
This can feel confusing because you might test the website on your computer and see the new version, while a friend in another location still sees the old website. That does not necessarily mean that the migration failed. DNS caching means different networks can update their information at different times.
The most important thing is to keep both the old and new hosting environments stable during the transition whenever possible. If the old hosting account contains your live website, do not immediately delete it after changing nameservers. Give the DNS transition enough time to settle and verify that your website, SSL certificate, forms, subdomains, and email services are functioning correctly.
DNS Propagation: How Long Does It Take?
DNS propagation refers to the period during which DNS information changes become visible across different DNS resolvers and networks. There is no single magical moment when every Internet user switches at exactly the same second.
Current provider documentation gives practical ranges rather than one universal number. Hostinger says nameserver propagation may take up to 24 hours, while Namecheap says nameserver changes may take up to 24–48 hours worldwide and can often complete sooner.
During propagation, you might experience:
- Website working on one network but not another.
- Old website appearing temporarily.
- New website appearing on your mobile connection but not Wi-Fi.
- DNS-checking services showing different results at different times.
- Email behavior changing temporarily if mail-related DNS records were affected.
Avoid repeatedly changing the nameservers because the website has not appeared immediately. Constant changes can make troubleshooting more difficult. Instead, confirm that the nameservers are correct, verify the DNS zone at the new provider, and allow sufficient time for caches to update.
Nameserver Change vs A Record: Which Should You Use?
There are two common ways to connect a domain to new hosting: change the nameservers or change the A record.
Changing nameservers transfers DNS authority to the new nameserver provider. This is often convenient when you want the new hosting company to manage your DNS. Hostinger describes nameserver changes as an option when you want DNS managed by Hostinger, while its documentation also describes using an A record when you prefer to keep DNS managed elsewhere.
Changing only the A record can be useful when you already use a DNS provider such as Cloudflare and do not want to move the entire DNS zone. In that setup, you keep the existing nameservers but update the relevant DNS record so the domain points toward the new hosting server.
| Method | Best for | Main consideration |
|---|---|---|
| Change Nameservers | Beginners and complete DNS management migration | Existing DNS records must be recreated correctly |
| Change A Record | Users keeping DNS with another provider | Requires correct DNS record management |
| CNAME | Specific hostname/subdomain configurations | Not suitable for every root-domain setup |
Cloudflare’s current documentation confirms that using Cloudflare as the authoritative DNS provider requires the domain’s nameservers to point to the nameservers assigned by Cloudflare.
Common Problems After Changing Nameservers
One common problem is simply entering the wrong nameserver. If even one value is copied incorrectly, DNS may not resolve as expected. Always copy the values directly from the new hosting provider’s dashboard rather than relying on an old tutorial or random website.
Another frequent issue is missing DNS records. If you change nameservers, the new DNS provider becomes responsible for the DNS zone. If your email provider needs MX records or your verification service requires TXT records, those records need to be present in the new zone. Namecheap explicitly warns that nameserver changes replace the existing DNS configuration, which is why backing up DNS records beforehand is so important.
SSL can also cause confusion after a hosting migration. Your new server needs a valid SSL certificate for the domain. If the DNS is pointing correctly but HTTPS displays an error, check the SSL configuration at the new host rather than assuming the nameserver change itself is broken.
Another possibility is that the domain is behind Cloudflare or another DNS service. In that case, changing nameservers at the registrar may not be the appropriate action if you want to keep the existing DNS architecture. Instead, you may only need to update the relevant DNS record.
How to Check Whether Your Domain Is Pointing Correctly
After changing the nameservers, verify the result instead of relying only on your browser. Check the domain’s current NS records and confirm that they match the nameservers supplied by your new DNS or hosting provider.
You can also test the website using different networks. For example, compare your normal broadband connection with a mobile hotspot. If one network shows the new site and another shows the old site shortly after the change, DNS caching may still be in progress.
For a more technical check, use DNS lookup tools to inspect the NS, A, and other relevant records. If the NS records have updated but the A record is wrong, your domain may still fail to reach the new website. If the NS records have not changed at all, the registrar-side update may not have been completed or may still be propagating.
Cloudflare’s documentation also recommends verifying the nameserver update at the registrar when a domain remains pending or does not become active as expected.
How to Point Domain to New Hosting Without Losing Email
This deserves special attention because website migrations and email migrations are not necessarily the same thing. Your website may be hosted with one company while your email is handled by Google Workspace, Microsoft 365, Zoho, or another provider.
If you change nameservers, make sure the new DNS zone contains the correct MX records for your email provider. You may also need SPF, DKIM, and DMARC records for email authentication. Hostinger’s current documentation specifically warns that changing nameservers can affect email records and recommends reviewing these records when using a different email provider.
A safe migration therefore looks something like this: first document the existing DNS records, then configure the new DNS zone, verify your website’s records, verify email records, and only then change the nameservers. This approach reduces the chance of a website migration turning into an unexpected email outage.
How to Point Domain to New Hosting: Quick Checklist
If you want the shortest possible version of How to Point Domain to New Hosting (Nameserver Change Guide), use this checklist:
- Buy and activate your new hosting plan.
- Upload or migrate your website to the new server.
- Find the exact nameservers provided by your new host.
- Log in to your domain registrar.
- Open the domain’s nameserver settings.
- Replace the old nameservers with the new ones.
- Save the changes.
- Verify the new nameservers.
- Check A, CNAME, MX, TXT, SPF, DKIM, and DMARC records as needed.
- Wait for DNS propagation.
- Test the website, HTTPS, subdomains, and email.
- Keep the old hosting active until you are confident the migration is complete.
This process is simple once you understand what each component does. The biggest mistake is treating a nameserver change like a simple website setting when it can also affect email and other DNS-dependent services.
Conclusion
Learning How to Point Domain to New Hosting (Nameserver Change Guide) is an essential skill if you manage websites, WordPress sites, blogs, or small-business websites. The basic process is straightforward: prepare your new hosting account, find the correct nameservers, update them at your domain registrar, verify your DNS records, and allow time for propagation.
The important part is preparation. Do not change nameservers blindly, especially if your domain handles email, subdomains, verification records, or other services. Make a copy of your existing DNS records before switching and recreate the necessary records at the new DNS provider. Nameserver changes can take time to become visible everywhere, so temporary differences between networks are normal during propagation.
Once the new nameservers are active and your DNS records are correct, visitors should gradually reach your website on the new hosting server. After everything works correctly, you can safely complete the old hosting cancellation or migration process.
FAQs
1. How long does it take to point a domain to new hosting?
The nameserver update itself can be submitted quickly, but DNS propagation takes longer. Current hosting-provider documentation commonly gives a range of up to 24–48 hours, although many changes become visible sooner.
2. Will changing nameservers delete my website?
No. Changing nameservers does not delete the website files stored on your old hosting account. However, it changes where DNS directs visitors. Your new hosting account must already contain the website if you want visitors to see the new version.
3. Will changing nameservers affect my email?
It can. If your email depends on DNS records and those records are not correctly configured at the new DNS provider, email can stop working. Before changing nameservers, copy your MX, SPF, DKIM, DMARC, and other important DNS records and recreate them where necessary.
4. Can I point my domain to hosting without changing nameservers?
Yes. You can often keep your existing nameservers and change the domain’s A record to the IP address of the new hosting server. This is useful when you want to keep DNS management with your current provider, such as Cloudflare.
5. What should I do if my domain still shows the old website?
First, verify that the new nameservers are correct. Then check the DNS zone at the new provider and make sure the A or relevant website records point to the new server. If everything is correct, the difference may simply be DNS caching, so allow sufficient propagation time before making additional changes.