Pointing a domain to a new hosting provider usually means changing where the domain’s DNS records are managed, or updating the nameservers so traffic reaches the new hosting environment. In most cases, the goal is simple: keep the domain name the same, but make the website, email, and other services resolve to the new platform without unnecessary downtime.
If you are moving a site to a new hosting account, a managed hosting platform, or a control panel such as Plesk, the key is to update DNS carefully and in the right order. A domain can continue to work during the transition if you preserve the existing records, allow time for DNS propagation, and verify the new hosting setup before making the final switch.
What it means to point a domain to a new hosting provider
When you point a domain to a new host, you are telling the internet which server should answer requests for that domain. This can be done in two main ways:
- Changing nameservers to the new hosting provider’s nameservers.
- Updating DNS records at the current DNS provider so the domain points to the new server IP address.
The right method depends on how your domain and DNS are managed. Some hosting providers ask you to change nameservers, while others let you keep DNS elsewhere and only update A, AAAA, CNAME, and MX records.
For most website migrations, the safest approach is to confirm the new hosting account is ready first, then update DNS once the destination site has been tested.
Before you change anything
Prepare the new hosting environment before you alter DNS. This helps avoid broken websites, mail delivery issues, or temporary downtime.
Check the new hosting account
Make sure the destination hosting account is active and the site is accessible through the temporary server URL, IP address, or preview link provided by the platform. If you use Plesk or a similar control panel, confirm that:
- the domain is added to the subscription or hosting account;
- the correct document root is set;
- the website files are uploaded;
- databases have been imported;
- SSL certificate installation is ready or pending;
- email accounts are created if you will host mail on the new provider.
Lower the TTL in advance
TTL, or Time To Live, controls how long DNS resolvers cache a record before checking again. If you can edit DNS before the migration, reduce the TTL for key records such as A, AAAA, and MX to a lower value, for example 300 seconds. Do this at least a few hours before the switch, ideally 24 hours ahead.
A lower TTL can help the change take effect more quickly, although some resolvers may still cache data for longer than expected.
Back up the existing DNS records
Copy all current DNS records before making changes. This is especially important if the domain also uses email, subdomains, verification records, or third-party services. Save records such as:
- A and AAAA records
- CNAME records
- MX records
- TXT records for SPF, DKIM, DMARC, and verification
- SRV records if used for specific services
- NS records if you are managing delegated subdomains
Missing a single record can cause problems later, especially for email and automated services.
Choose the correct method: nameservers or DNS records
There is no single correct answer for every domain transfer or hosting move. The best method depends on whether you want the new provider to manage your DNS completely or only host the website.
Option 1: Change nameservers
This method delegates DNS management to the new provider. After the change, all DNS settings are managed in the new hosting platform or registrar panel if they provide DNS hosting.
Use this approach if:
- the new hosting provider offers a full DNS service;
- you want all records managed in one place;
- you are comfortable recreating all DNS entries on the new side.
Be careful: if the new DNS zone does not include every existing record, email, subdomains, or external services may stop working.
Option 2: Update A and related records only
This method keeps DNS management where it already is, but points the domain to the new server by changing the destination IP address. For a website migration, this is often the least disruptive option.
Use this approach if:
- you want to keep email DNS records unchanged;
- you are only moving the website to a different host;
- your DNS is managed by a registrar, CDN, or third-party DNS provider.
In many cases, you only need to update the A record for the root domain and the CNAME record for www, along with any AAAA records if IPv6 is in use.
How to point a domain to a new hosting provider step by step
1. Find the new server address or nameservers
Your new hosting provider will give you either:
- a server IP address for DNS record updates; or
- nameserver values such as ns1 and ns2 for a full DNS delegation.
Copy these details exactly as provided. A small typo can prevent the domain from resolving correctly.
2. Decide whether email stays on the old provider
If your email is currently delivered through the old host, decide whether to move it now or later. If you leave mail on the current provider, do not remove or replace the MX records. If you are moving mail to the new provider, update the MX records only after the new mailboxes and DNS authentication records are ready.
For a clean website-only migration, keep the existing MX records unchanged.
3. Update DNS at the registrar or DNS host
Log in to the place where your DNS zone is managed. This is not always the same as the domain registrar. Then do one of the following:
- If changing nameservers: replace the current nameservers with the new provider’s nameservers.
- If keeping DNS where it is: edit the A record for the root domain and set it to the new server IP. Update the www record if needed, usually by pointing it to the root domain or to the same IP.
If you use IPv6, check the AAAA record too. If the new host does not support IPv6, remove the old AAAA record to avoid sending traffic to the wrong server.
4. Recreate all required records on the new DNS zone if needed
If you switched nameservers, add the full set of DNS records to the new DNS zone before the domain starts relying on it. Include all necessary records for the website and services:
- A / AAAA for the website host;
- CNAME for www and any subdomains;
- MX for mail delivery;
- TXT for SPF, DKIM, DMARC, verification, and third-party tools;
- CAA if your certificate policy uses it;
- SRV if your services require it.
In a Plesk environment, DNS records may be managed directly inside the control panel if DNS service is enabled for the subscription. If DNS is hosted elsewhere, update the external zone instead of the Plesk panel.
5. Update the website files and database on the new host
DNS only tells visitors where to go. It does not move your site content. Before or after the DNS change, make sure the site exists on the new host:
- upload the website files;
- restore the database;
- update application config files if the database credentials changed;
- check file permissions and ownership;
- verify any hard-coded URLs or absolute paths.
If the site is a WordPress installation or another CMS, confirm that the site URL matches the domain and that the new host can serve the correct document root.
6. Test the new hosting before switching traffic
Whenever possible, test the site on the new server before DNS fully propagates. Common methods include using a temporary hosts file entry, a staging URL, or a preview domain provided by the host. Check:
- homepage and key internal pages;
- forms and contact pages;
- image loading and media paths;
- admin login;
- SSL status;
- email sending and receiving if mail is hosted there.
This step is especially useful in managed hosting environments where the control panel can show domain and certificate status separately.
7. Monitor propagation after the change
DNS propagation is the time it takes for DNS changes to be visible across networks. In practice, some users may see the new host within minutes, while others continue to hit the old host until cached records expire.
During this period, both the old and new hosting environments may receive traffic. Keep the old account active until you are confident traffic has moved over and no important requests are still using the previous server.
What records you usually need to update
Root domain and www
The root domain, such as example.com, usually uses an A record pointing to the new server IP. The www hostname can be configured as either:
- a CNAME to the root domain; or
- a separate A record pointing to the same IP.
Using a CNAME for www is often simpler to maintain.
IPv6 records
If the old host used IPv6 and the new host does not, remove the AAAA record. If IPv6 is supported on the new provider, make sure the new AAAA address is correct.
Email records
If email is hosted separately, keep MX records pointed to the current mail server and confirm SPF, DKIM, and DMARC still match that setup. If email moves with the website, update the MX records only after mailboxes are created and tested on the new platform.
Verification and third-party services
Many services use TXT records for verification, ownership confirmation, marketing tools, and API integrations. These records are easy to overlook during a move. Keep them in the zone unless you are sure they are no longer needed.
Common mistakes when pointing a domain
- Changing nameservers without copying all records: this can break email, subdomains, or SSL validation.
- Forgetting the www record: visitors may reach the bare domain but not the www version, or the reverse.
- Leaving an old AAAA record in place: traffic may still resolve to the previous host over IPv6.
- Deleting MX records too early: email can stop working even if the website is fine.
- Not lowering TTL first: the switch may take longer to settle.
- Moving DNS and website content at the same time without testing: this makes troubleshooting harder.
How long DNS changes take
Most DNS changes begin to work within a few minutes to a few hours, but full propagation can take longer depending on TTL values and resolver caching. A common expectation is up to 24 hours, and in some cases longer.
If you need a faster transition, lower TTL values before the switch and avoid making repeated changes during propagation. Every extra change can reset caches and create confusion.
How to verify the domain points to the new host
After updating DNS, check the domain from multiple networks or tools. Confirm that:
- the root domain resolves to the new IP address;
- www resolves correctly;
- the website loads over HTTP and HTTPS;
- the SSL certificate is valid for the domain;
- email still delivers if MX records were unchanged;
- subdomains and API endpoints still resolve as expected.
You can also compare the active DNS records against your backup list to make sure nothing was missed.
Troubleshooting after a domain change
The old site still appears
This is often due to cached DNS. Try from another network or use a DNS lookup tool to check the current record. If the A record is correct, wait for caches to expire.
The site loads for some users but not others
This usually indicates mixed propagation. Some resolvers have updated, while others still hold the old values. Keep both hosting environments available until traffic stabilises.
Email stopped working
Check MX, SPF, DKIM, and DMARC records. If you switched nameservers, make sure the new zone includes the full email configuration. Also confirm that the new host has mail services enabled if it is meant to handle mail.
SSL warnings appear
Install or renew the certificate on the new host and confirm the domain points to the correct web server. A certificate mismatch can happen if the domain still resolves to the old server or if the certificate was not issued for the current hostname.
Subdomains do not resolve
Recheck the DNS zone for missing CNAME or A records. If the subdomain was delegated separately, make sure the delegation still exists and points to the right nameservers.
Best practice for a safe hosting migration
The most reliable migration process is:
- Prepare the new hosting account and upload the site.
- Copy and verify all DNS records.
- Lower TTL values ahead of time.
- Test the site on the new server before switching DNS.
- Update nameservers or A records.
- Monitor web and mail services during propagation.
- Keep the old host online until the change is fully stable.
This sequence reduces downtime and helps ensure that the website, email, and DNS all continue to function during the move.
FAQ
Do I need to change nameservers to point a domain to a new host?
Not always. If you only want the website to load from the new server, you can often keep the existing DNS provider and update the A record instead. Change nameservers only if you want the new provider to manage DNS.
How do I point a domain to a new hosting provider without changing email?
Keep the current MX records unchanged and update only the website records, usually the A record for the root domain and the CNAME or A record for www. This keeps email delivery routed to the same mail service.
Will my website go offline when I change DNS?
Usually not if the new host is ready and the DNS records are correct. Some visitors may briefly see the old host while changes propagate, so keep both environments available during the transition.
How do I point a domain to Plesk?
Add the domain to the correct subscription in Plesk, ensure the web root is set correctly, and then either update the DNS zone in Plesk or change the external DNS records to the server IP. If DNS is hosted elsewhere, only the public records need to be changed.
What is the difference between an A record and nameservers?
An A record points a hostname to an IP address. Nameservers define which DNS server is authoritative for the domain’s records. If you change nameservers, you are moving DNS management. If you edit an A record, you are only changing the destination IP for the website.
How long should I wait before closing the old hosting account?
Keep the old hosting active for at least 24 to 72 hours after the DNS change, or longer if you expect slower propagation or ongoing email traffic. This gives time to confirm that all users are reaching the new server.
Conclusion
Pointing a domain to a new hosting provider is mainly a DNS task, but it works best when combined with careful migration planning. Prepare the new host, back up existing DNS, preserve important records, and verify the site before switching traffic. Whether you change nameservers or update A records, the goal is the same: move the domain cleanly with minimal interruption to the website and email services.
By following a structured process and checking propagation carefully, you can complete the move with less risk and a smoother experience for visitors and administrators alike.