DNS Propagation, Nameservers and Why Your Domain Does Not Point to Your Site Yet

If your domain does not show your new site yet, it is almost always because DNS changes have not reached every resolver. Either the nameservers or A record at your registrar are wrong, or old answers are still cached until their TTL expires, which usually takes minutes to a few hours and at most about 48 hours. This guide shows you how to point a domain registered elsewhere to your Cloudesta hosting or server, check the change from several locations, and preview your site before DNS is live.

It applies when you move a website to Cloudesta, launch a new site, or change mail providers.

Prerequisites

• Login access to the registrar where your domain was bought (or to your current DNS provider).
• Your Cloudesta welcome email, which lists your server IP address and, for hosting accounts, the nameservers to use.
• A terminal with dig. On Ubuntu 22.04/24.04 install it with sudo apt install dnsutils. Windows users can use nslookup.

1. How does DNS resolution work?

When someone types example.com, their device asks a recursive resolver, usually run by their ISP or a public service such as 1.1.1.1 or 8.8.8.8. If the resolver has no cached answer, it asks the root servers, which refer it to the servers for .com. Those servers refer it to the domain's nameservers. The nameservers hold the actual records and return the final answer, such as the IP address of your web server.

Every answer carries a TTL (time to live) in seconds, and resolvers keep the answer in cache for that long. "Propagation" is not a push to the whole internet. It is the time it takes for old cached answers to expire around the world. Different users can therefore see your old and new site at the same time.

2. What is the difference between nameservers and A, CNAME and MX records?

• Nameservers (NS) are set at your registrar. They decide which DNS service is authoritative for the whole domain.
• A record maps a name to an IPv4 address, for example example.com → 203.0.113.10.
• CNAME record makes one name an alias of another, for example www.example.com → example.com.
• MX records tell other mail servers where to deliver email for your domain. TXT records hold SPF, DKIM and verification values.

Records only take effect on the DNS service your nameservers point to. Editing an A record anywhere else has no effect.

3. How do I point a domain registered elsewhere to Cloudesta?

You have two options. Choose one, not both.

Option A: Use Cloudesta nameservers (typical for shared hosting)

At your registrar, replace the existing nameservers with the ones in your welcome email. For cPanel hosting accounts these are normally:

dns1.madar-it.com
dns2.madar-it.com

After the change, you manage all records in cPanel » Domains » Zone Editor. Click Manage next to your domain.

Option B: Keep your current DNS and change records

This is the usual choice for a Cloud VPS or n8n server, or when another provider manages your DNS. Leave the nameservers alone and edit these records at your current DNS provider, using the IP from your welcome email:

Type   Name               Value                    TTL
A      example.com (@)    203.0.113.10             300
CNAME  www                example.com              300
MX     example.com (@)    mail.example.com (10)    3600   # only if mail is hosted on Cloudesta
A      mail               203.0.113.10             3600   # only if mail is hosted on Cloudesta

If your email stays with another provider, do not touch its MX records.

4. How long does DNS propagation take?

For record changes, the wait equals the TTL of the old record. A record with TTL 3600 can be cached for up to one hour. Nameserver changes take longer, because the TLD's delegation records commonly have a 48-hour TTL. In practice most resolvers update within a few hours.

To make a planned move fast, lower the TTL of the records you will change to 300 at least one old-TTL period in advance. Make the change, then raise the TTL again afterwards.

5. How do I preview my site before DNS changes?

Add a line to your computer's hosts file. This overrides DNS on your machine only.

# Linux / macOS
sudo nano /etc/hosts

# Windows (open Notepad as Administrator)
C:\Windows\System32\drivers\etc\hosts

# Add this line, then save:
203.0.113.10   example.com www.example.com

Reload the site in a private browser window. Expect an SSL warning, because AutoSSL or Let's Encrypt cannot issue a certificate until public DNS points to the server. Remove the line when you are done, or you will keep seeing the new server even if DNS is wrong.

Verify it works

First, check the delegation and query the authoritative servers directly. Their answer is what the world will eventually see.

dig NS example.com +short
dig @dns1.madar-it.com example.com A +short
dig +trace example.com A

Next, compare public resolvers. They may still return cached old values.

dig @1.1.1.1 example.com A +short
dig @8.8.8.8 www.example.com +short
dig @8.8.8.8 example.com MX +short

# Windows
nslookup example.com 1.1.1.1

For a worldwide view, use a web tool such as dnschecker.org. It shows answers from resolvers in many countries. Once the authoritative servers return 203.0.113.10, your setup is correct. Any remaining old answers are cache and will expire on their own.

Common problems

Email stopped arriving after changing nameservers

The new zone lacks your mail provider's MX and TXT records. Add them in cPanel » Domains » Zone Editor and set Email Routing to Remote Mail Exchanger. Then check the result with dig @8.8.8.8 example.com MX +short.

example.com works but www.example.com does not, or the reverse

The apex domain and www are separate names, and each needs its own record. Add an A record for @ and a CNAME or A record for www.

The DNS provider refuses a CNAME on the root domain

A CNAME at the apex is not allowed by the DNS standard, because it conflicts with the NS, SOA and MX records there. Use an A record pointing to the server IP. Some providers also offer an ALIAS/ANAME or flattening record that works at the apex.

dig shows the new IP but your browser still loads the old site

Your ISP, operating system or browser has cached the old answer. Check your hosts file for leftover lines, then flush your local cache:

sudo resolvectl flush-caches                                  # Ubuntu
ipconfig /flushdns                                            # Windows
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder # macOS

If the old site still loads, try mobile data or set the resolver to 1.1.1.1. An ISP cache cannot be cleared from your side. It expires when the old TTL runs out.

AutoSSL or Let's Encrypt fails to issue a certificate

Validation needs public DNS to point to the server. Wait until the authoritative servers and major resolvers return the new IP. Then run cPanel » Security » SSL/TLS Status » Run AutoSSL, or re-run Certbot on your VPS.

Frequently asked questions

Can I speed up DNS propagation?

You cannot force other resolvers to drop their cache. You can lower the TTL to 300 seconds before a planned change so that old answers expire quickly.

Should I change nameservers or just the A record?

Change the nameservers if you want to manage everything in cPanel. Change only the A record if your DNS or email is managed elsewhere and you want to leave it untouched.

Who sets reverse DNS (PTR) for my server IP?

Reverse DNS is controlled by the owner of the IP block, so you cannot set it in your own zone. Open a support ticket and Cloudesta will set it for your VPS or dedicated server IP.

Need help? If your domain still does not resolve after 48 hours, or you are unsure which records to create, open a ticket at https://cloudesta.com/submitticket.php and include your domain name and the output of dig NS example.com +short.