To point your domain to cloud hosting, you have two options: update your domain's nameservers to those provided by your cloud host, or edit the A and CNAME records directly at your registrar while keeping DNS management there. Both work — your choice depends on how much control you want over DNS configuration.
This guide covers exactly when to use each method, what you need before you start, and how to confirm the change propagated successfully.
What You Need Before You Start
Gather the following before touching any setting. Skipping this step is the single biggest cause of errors and unnecessary downtime.
- Your cloud server's public IP — found in your provider's dashboard (DigitalOcean, Linode, Hetzner, etc.) listed as "IPv4 Address."
- Your provider's nameservers — only needed if you're delegating full DNS (e.g.,
ns1.provider.comandns2.provider.com). - Access to your registrar panel — GoDaddy, Namecheap, Hostinger, or wherever you purchased the domain.
- Current record TTL — if you have a live site, lower it to 300 seconds (5 min) at least 24 hours before switching so propagation is fast.
Method 1 — Change Nameservers (Best for Beginners)
This method hands full DNS management to your cloud provider. It's the simplest option because the provider's panel automatically handles A, MX, CNAME, and other records.
- Log in to your registrar and find the Nameservers or DNS / Name servers section.
- Replace the current nameservers with the ones your cloud provider gave you (usually a primary and a secondary).
- Save. Your registrar will warn you about propagation time — that's normal.
- In your cloud provider's panel, create a DNS zone for your domain and add the records you need (A, CNAME, MX).
Propagation time: anywhere from 15 minutes to 48 hours, depending on TTL and the ISPs involved. The real-world average is usually under 2 hours.
Method 2 — Edit A and CNAME Records at Your Registrar
If you want to keep DNS at your registrar — useful when you have email configured there or use Google Workspace — you only need to update two records:
| Record | Host | Value | TTL |
|---|---|---|---|
| A | @ (root) | Cloud server's public IP | 300 – 3600 s |
| CNAME | www | yourdomain.com (or an A record) | 300 – 3600 s |
Some cloud providers assign a floating IP or hostname instead of a fixed IP. In that case, use a CNAME for the root (@) if your registrar supports "CNAME Flattening" (Cloudflare and NS1 do), or an ALIAS record if the platform offers it.
What About Email?
If you change nameservers, your MX records move to the new DNS zone. Copy them first before changing nameservers so email doesn't go dark. If you're only editing the A record, MX records are not affected.
How to Verify Your Domain Is Pointing Correctly
Once you've made the change, check propagation with these tools:
- Terminal:
dig yourdomain.com A +short— should return your cloud server's IP. - whatsmydns.net — shows propagation across multiple global regions at once.
- dnschecker.org — similar, with a visual country-by-country map.
If the A record already shows the correct IP but the site still won't load, the issue is on the server side — Apache or Nginx isn't listening on port 80/443, or the firewall is blocking traffic — not DNS.
SSL/TLS After the Change
Wait for DNS to propagate completely before requesting an SSL certificate with Let's Encrypt or a similar CA. Running certbot before your domain resolves to your server will cause the HTTP challenge to fail and burn rate-limit attempts.
Common Mistakes When Pointing a Domain to Cloud Hosting
- Not lowering the TTL in advance: if TTL was set to 86,400 s (24 h), resolvers will cache the old IP for a full day.
- Changing both nameservers and A records at the same time: these methods are mutually exclusive — pick one.
- Forgetting the www subdomain: always add both the root (
@) record andwwwso both versions resolve. - Dynamic IP with no protection: some budget VPS providers reassign the IP on reboot. Use a reserved or elastic IP so your DNS doesn't become stale.
If your team needs hands-on help migrating domains with zero downtime, the specialists at elenlace.com can guide you through every step of the process.
Find more cloud configuration guides in our cloud hosting blog section.
Key Takeaways
- Two methods exist: change nameservers (full DNS delegation) or edit A/CNAME records (keep DNS at your registrar).
- Lower TTL to 300 s at least 24 hours before any switch if your site is already live.
- Confirm propagation with
digor whatsmydns.net before declaring success. - Request your SSL certificate only after DNS has fully propagated.
- Never rely on a dynamic IP — use a reserved or elastic IP from your cloud provider.
Ready to move your domain without interruptions? The team at elenlace.com offers assisted migrations to get your site on the cloud in hours, not days.
FAQ
How long does nameserver propagation take?
Between 15 minutes and 48 hours, though most ISPs refresh their cache within 2 hours. The TTL of the previous records is the main determining factor.
Can I point my domain to a cloud IP without changing nameservers?
Yes. By editing only the A record (and a CNAME for www) at your registrar, you redirect web traffic to your cloud server without moving any other DNS configuration.
What happens to my email if I change nameservers?
Your MX records must be recreated in the new DNS zone before you swap nameservers, or email delivery will break. If you only change the A record, MX records are untouched.
Why won't my site load even though DNS has propagated?
Correct DNS is necessary but not sufficient. Check that your web server (Apache or Nginx) is running, your virtual host is configured for your domain, and that ports 80 and 443 are open in the server firewall.
Compare providers
Other providers and guides worth comparing:
