Moving a site can feel like changing a store sign while customers are still walking in. One wrong DNS edit, and visitors hit the old server, the wrong server, or nothing at all.
The good news, this is usually a short job. To point a domain to a new host, we need the new host’s details, one careful change at the registrar, and time for the update to spread. Let’s do it in the order that keeps our site live and our email safe.
Get the new hosting account ready before we change anything
When people search how to point domain to host, they often mix up two separate tasks. Pointing changes DNS so traffic goes to a new server. A domain transfer changes where the domain is registered. We can point first and transfer later, or never transfer at all.
Before we touch DNS, we should finish the move on the new host. That means uploading site files, importing the database, and checking the site on a temporary URL or preview link. If we change DNS too early, we’re sending traffic to an unfinished site.
We also want a copy of the current DNS zone. A screenshot works. A proper export is even better. Keep the current A, CNAME, MX, and TXT records handy, because those details matter if email or third-party tools stay where they are.
One prep step saves time later: lower the TTL 24 to 48 hours before the switch. A TTL of 300 seconds is a common choice. That tells other servers not to cache the old answer for long, so the new host shows up faster after the change.
If we’re moving to a better setup, the hosting choice matters too. Our cPanel hosting with free SSL is a strong fit for small business sites that want easy control without extra clutter. If we run WordPress, managed plans can cut down the admin work. For a broader migration checklist, this hosting transfer overview from DreamHost is a useful reference.
Update the DNS settings that actually control the move
Once the site is ready, we log into the account where the domain is managed. That’s often the registrar, not the host. From there, we decide whether to change nameservers or only the website records.
This quick guide helps us pick the right move:
| Situation | What we change | Why |
|---|---|---|
| The new host will manage all DNS | Nameservers | Easiest full handoff |
| Only the website is moving | A record for root, CNAME for www | Keeps other DNS in place |
| Email stays with another provider | Leave MX and email TXT records alone | Prevents mail issues |
The short version, nameservers move the whole DNS house. A records move one room.
Here’s the safe order:
- Open the domain’s DNS manager at the registrar.
- Enter the new host’s nameservers, or update the root A record to the new server IP.
- Make sure
wwwalso points correctly, usually with a CNAME to the root domain. - Save the change, then leave the old hosting active for now.
If email stays on Microsoft 365, Google Workspace, or another mail service, don’t replace the MX, SPF, DKIM, or DMARC records unless the email provider is also changing.
There’s one common trap worth calling out. We should not use a CNAME for the root domain in most normal setups. Use an A record there. A root CNAME can break email and other services. If we want a second source on full nameserver changes, Cloudflare’s nameserver setup guide explains the handoff well.
Verify propagation, then check the parts people forget
After we save the change, the wait begins. DNS propagation can happen in minutes, but it often takes 4 to 24 hours, and in some places up to 48 hours. That doesn’t mean something is broken. It means different networks are learning the new answer at different speeds.
While the change spreads, we should test more than the homepage. Open the site on Wi-Fi and mobile data. Check the www version and the root domain. Log in to the admin area. Submit a contact form. If the site takes payments, test checkout. Also confirm the SSL certificate is active on the new host, because browsers don’t give second chances on security warnings.
A few mistakes cause most of the panic. The first is a typo in the server IP or nameserver. The second is forgetting the www record. The third, and the most painful, is breaking email by wiping out mail records during a website-only move. We also don’t want to redesign the site at the same time. Change one variable first, then make cosmetic updates later.
If we moved because the old host couldn’t keep up, this is the right time to think bigger. Our Web Hosting Plus gives growing sites more power without turning management into a chore. For a more detailed no-downtime checklist, this DNS migration guide is worth a look.
Pointing a domain isn’t hard, but order matters. We set up the new host first, change only the DNS records that need to change, and wait until the site, SSL, and email all look normal before we cancel anything old.
That’s the whole move. Calm, clean, and controlled. If we’re ready to leave slow hosting behind, now’s a good time to put the domain on a platform that gives us speed, support, and room to grow.