What is DNS Propagation and How Long Does It Take?

What is DNS propagation?

When you make a change to your domain's DNS records - such as updating nameservers, changing an A record, or adding an MX record - that change does not take effect instantly everywhere in the world. The change needs to spread (propagate) from your authoritative DNS server to thousands of other DNS servers globally.

This spreading process is called DNS propagation. During propagation, some users will see your old DNS information while others see the new information. This is normal and expected.

How DNS propagation works

Understanding the propagation process helps explain why it takes time:

1. You make a DNS change: You update a DNS record in your control panel or change your nameservers at your domain registrar
2. Your DNS server is updated: The authoritative DNS server for your domain reflects the change immediately
3. Other DNS servers check in: DNS servers around the world periodically query the authoritative server for updates
4. Caching delays propagation: DNS servers cache (remember) DNS information for a period of time specified by the TTL (Time To Live) value
5. Eventually, all servers update: Over time, all DNS servers worldwide update their cached copy of your DNS information

How long does DNS propagation take?

The standard answer is up to 48 hours, but the reality is more nuanced:

• Average propagation time: 4-24 hours for most changes
• Fast propagation: 1-4 hours for simple record changes with low TTL values
• Slow propagation: 24-48 hours for nameserver changes or records with high TTL values
• Instant for some: If a DNS server has not cached your old information, users querying that server see the change immediately

In South Africa, DNS propagation is typically on the faster end of this spectrum for major ISPs like Telkom, MTN, Vodacom, and Afrihost.

What affects propagation speed?

Several factors influence how quickly your DNS changes propagate:

TTL (Time To Live) values

The TTL is a setting on each DNS record that tells other servers how long to cache the record. A TTL of 3600 seconds (1 hour) means DNS servers will cache your record for an hour before checking for updates. A lower TTL means faster propagation.

Type of change

• Nameserver changes: Usually take the longest (24-48 hours) because they require updates at the domain registry level
• A or AAAA record changes: Typically propagate within a few hours
• MX record changes: Usually propagate within 4-12 hours
• TXT record changes: Generally quick, within a few hours

DNS resolver caching policies

Some ISPs and DNS providers ignore TTL values and cache records for longer than specified. This is rare but can delay propagation for users on those networks.

How to check DNS propagation

You can check whether your DNS changes have propagated using these methods:

Online DNS propagation checkers

Use websites like whatsmydns.net or dnschecker.org to check your DNS records from multiple locations worldwide. These tools query DNS servers in different countries and show you whether they are returning your old or new DNS information.

Command line tools

On Windows, Mac, or Linux, you can use command-line tools to check DNS:

nslookup yourdomain.co.za
dig yourdomain.co.za
host yourdomain.co.za

These commands query your local DNS server. To check a specific DNS server, use:

nslookup yourdomain.co.za 8.8.8.8

This queries Google's DNS server (8.8.8.8) specifically.

Flush your local DNS cache

Your computer also caches DNS information. To see the latest DNS data, flush your local cache:

• Windows: Open Command Prompt and run ipconfig /flushdns
• macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• Linux: Run sudo systemd-resolve --flush-caches

Common DNS propagation scenarios

Scenario 1: Changing nameservers

When you point your domain to 0724 Hosting's nameservers (ns1.practiwebs.co.za and ns2.practiwebs.co.za), propagation typically takes 12-48 hours. Your website and email may be unavailable during this time if the old nameservers are no longer responding.

Scenario 2: Moving a website to a new server

When you change your A record to point to a new IP address, propagation usually completes within 4-12 hours. During this time, some visitors see your old website while others see the new one.

Scenario 3: Changing MX records for email

When you update MX records to point to a new mail server, propagation takes 6-24 hours. During this time, some emails may be delivered to the old server and some to the new one. This is why it is important to keep both servers active during migration.

Best practices during DNS propagation

1. Lower your TTL in advance: If you know you will be making DNS changes, lower your TTL values to 300 seconds (5 minutes) a day or two before the change. After the change propagates, raise the TTL back to 3600 or higher.
2. Make changes during low-traffic periods: Schedule DNS changes for times when your website or email traffic is lowest to minimize impact.
3. Do not make multiple DNS changes at once: Allow one change to fully propagate before making another to avoid confusion and troubleshooting difficulties.
4. Keep old services running: Do not shut down your old web server or email server until DNS has fully propagated and all traffic is going to the new server.
5. Test before switching: Use a hosts file entry or direct IP access to test your new server before updating DNS.

Troubleshooting propagation issues

My DNS change has not propagated after 48 hours

If propagation seems stuck:

• Verify the change was actually saved on your authoritative DNS server
• Check that your domain is not locked at the registry
• Confirm you are checking the correct record type and name
• Contact your domain registrar or DNS provider for assistance

Some locations see the change but others do not

This is normal during propagation. Be patient - it will eventually complete. If certain locations remain stuck after 48 hours, the issue may be with specific DNS resolvers caching aggressively.

My website is working but email is not

MX records often take longer to propagate than A records. Check your MX records specifically using nslookup -type=MX yourdomain.co.za or an online DNS checker.

Getting help with DNS changes

If you need assistance with DNS changes or are experiencing propagation issues, contact 0724 Hosting support. We can verify your DNS configuration and check propagation status from our South African servers.