You have just purchased a new hosting plan, uploaded your website files, and updated your domain's nameservers. Everything appears to be configured correctly, but when you visit your website, something strange happens.
Your laptop still displays the old website, while your friend can see the new one. You try opening the website on your mobile phone, and it works perfectly. But when you connect to your office Wi-Fi, the old version appears again.
Naturally, you begin to wonder whether something went wrong with your hosting account.
In many situations, the problem is not your website or hosting provider. It is a process known as DNS propagation.
DNS propagation is one of the most common sources of confusion when moving websites, changing nameservers, or connecting a domain to a new hosting service.
Understanding how it works can save you hours of unnecessary troubleshooting and help you avoid making changes that could disrupt your website or business email.
In this guide, we explain what DNS propagation means, how long it takes, why different visitors may see different versions of your website, and what you can do when your DNS changes are not showing.
DNS propagation describes the period during which updated Domain Name System (DNS) information becomes visible to internet users through different DNS resolvers.
To understand this, think of DNS as the internet's address directory.
When someone types a domain name such as yourbusiness.com into a browser, DNS helps the browser find the server associated with that domain.
Your domain name is the address people remember, while DNS records provide the technical information needed to locate the appropriate services.
For example, a DNS record might connect your domain to the IP address of your hosting server. Other records can direct email to the correct mail provider or verify ownership of your domain.
When you change these records, not everyone immediately receives the updated information.
Some DNS resolvers may still have the previous information stored in their cache. Until those cached records expire or are refreshed, they may continue directing visitors to the old destination.
This delay is commonly called DNS propagation.
Technically, DNS changes are not distributed through a single worldwide update. The authoritative DNS servers publish the current records, and other resolvers retrieve updated information as their cached answers expire.
That is why the process can appear inconsistent.
Imagine you operate an online fashion store in Lagos.
Your website has been running on one hosting server, but you decide to move to a new provider because your business needs a different hosting environment.
Your previous server uses one IP address, while your new hosting server uses another.
After moving your website files and database, you update your domain's DNS record to point to the new server.
At this stage, the new DNS information may already be available from the authoritative DNS server.
However, some internet service providers and public DNS resolvers may still remember the old IP address.
As a result, customers using one network may reach your new website, while others continue reaching the old server.
Eventually, the cached information expires, and resolvers can retrieve the updated DNS records.
This explains why your website may appear to work correctly on one device or network but not another.
The process is normal, provided the DNS changes have been configured correctly.
There is no single guaranteed DNS propagation time.
Some DNS record changes become visible within minutes. Others take several hours, and nameserver changes can take longer.
The actual duration depends on factors such as the previous record's Time to Live (TTL), DNS resolver caching, and whether you changed individual DNS records or the domain's nameservers.
Here is a general guide:
| DNS change | What to expect |
|---|---|
| Updating an A record | Often minutes to hours, depending on caching |
| Updating a CNAME record | Depends on the previous cached record and TTL |
| Updating MX records | Often minutes to hours, but cached mail-routing information can persist |
| Adding a TXT record | May appear quickly, although previously cached negative responses can delay visibility |
| Changing nameservers | Can take several hours and sometimes 24–48 hours or longer |
These are general expectations, not guaranteed completion times.
For example, Cloudflare explains that the TTL of a DNS record determines how long resolvers may cache it. Google Cloud also notes that resolver caches and provider-specific behaviour can affect when updated records become visible.
Sources: Cloudflare DNS TTL Documentation and Google Cloud DNS Overview.
TTL stands for Time to Live.
It is a value associated with DNS records that tells caching resolvers how long they may retain a DNS answer before checking for updated information.
TTL values are measured in seconds.
For example:
| TTL value | Equivalent time |
|---|---|
| 300 | 5 minutes |
| 900 | 15 minutes |
| 1,800 | 30 minutes |
| 3,600 | 1 hour |
| 14,400 | 4 hours |
| 86,400 | 24 hours |
Suppose your domain's A record has a TTL of 3,600 seconds.
A resolver that recently retrieved that record may continue using its cached answer for up to one hour under normal TTL behaviour.
If you change the record during that period, the resolver may not immediately request the new information.
This is why TTL settings matter when planning website migrations.
Not necessarily.
Lower TTL values can help resolvers check for updated information more frequently, which may be useful when you expect to make DNS changes.
However, shorter TTLs can also increase the number of DNS queries reaching authoritative servers.
For websites with stable DNS configurations, there may be little benefit in constantly using extremely short TTL values.
If you are planning a migration, consider reducing the TTL before the change. Ideally, do this far enough in advance for resolvers holding the previous, longer TTL to refresh their cached records.
Changing the TTL at the same moment you update the IP address will not immediately remove old answers already cached elsewhere.
DNS propagation is one possible explanation, but it is not the only one.
When your website continues displaying old content after a migration or update, investigate the following possibilities.
This is the classic DNS propagation scenario.
Your domain has been updated correctly, but the resolver used by your internet connection still has the old address cached.
You may notice that the website works on mobile data but not on your office Wi-Fi.
Try checking the domain through another network or a DNS lookup service to see whether different resolvers return different results.
Changing an A record in the wrong DNS management interface will not necessarily affect your live website.
For example, your domain might be using nameservers from a third-party DNS provider while you are editing DNS records inside your hosting control panel.
In that situation, the records you are changing may not be authoritative for your domain.
Before making changes, confirm which nameservers your domain is currently using.
Then manage the DNS records at the provider responsible for those nameservers.
Sometimes, DNS is already correct, but your browser continues showing an older version of the website.
Browsers cache website resources such as images, stylesheets, and scripts to improve loading performance.
Try opening the website in a private browsing window or clearing the relevant browser cache.
If the DNS records already point to the correct server, the problem may be related to website caching rather than DNS propagation.
A content delivery network (CDN) may store copies of website resources across multiple locations.
Even after your DNS changes are complete, cached website content may remain available until it expires or is purged.
If your hosting environment uses a CDN or server-level caching system, review the appropriate cache settings before assuming that DNS is responsible.
This issue is particularly common when moving a WordPress website to a different domain name.
WordPress stores website URLs and other information in its database.
If your domain changes but the WordPress configuration still references the previous domain, visitors may experience redirects, broken links, missing images, or unexpected behaviour.
Updating DNS alone does not automatically update your WordPress database.
You may need to update the WordPress Address and Site Address settings and perform a carefully planned database search-and-replace where appropriate.
Always create a backup before making database changes, and use WordPress-aware tools that handle serialized data correctly.
Not every DNS issue is caused by propagation.
A mistyped IP address, missing record, incorrect CNAME target, or incomplete nameserver configuration can prevent your website from working.
Waiting another 24 hours will not fix a record that points to the wrong destination.
This is why checking the actual DNS values is more useful than simply waiting indefinitely.
You do not need to be an experienced system administrator to perform a basic DNS propagation check.
Several online tools allow you to inspect how your domain resolves through different DNS locations or services.
Visit DNSChecker.
Enter your domain name and choose the record type you want to inspect.
For example, select A if you recently changed your website's IPv4 address, or NS if you changed your nameservers.
The tool displays results from multiple DNS resolvers.
If some return your previous IP address while others return the new address, cached DNS information may still be affecting the results.
Remember that these tools provide samples from selected resolvers. They do not prove that every DNS resolver worldwide has updated.
Google provides a public DNS lookup interface at dns.google.
You can use it to inspect DNS responses for a domain and check whether Google's resolver is returning the expected information.
This can help you distinguish between a local network issue and a more widespread DNS configuration problem.
If you recently changed your domain's nameservers, verify that the registrar has published the intended nameserver information.
For supported domains, you can use SIRSTEVEHQ WHOIS Lookup or an appropriate registry lookup service.
If the published nameservers are still incorrect, investigate the change at the registrar rather than repeatedly editing unrelated DNS records.
If you have recently updated your DNS and the website is not working as expected, avoid making multiple changes without first identifying the problem.
Repeatedly switching nameservers or changing IP addresses can make troubleshooting more complicated.
Start by confirming that the intended DNS changes were saved successfully.
Next, check the authoritative DNS records and compare them with the information provided by your hosting provider.
If the authoritative records are correct, test the domain through different resolvers.
You can also try clearing your device's DNS cache or temporarily using another network. This may help you determine whether the issue is limited to your connection.
However, clearing your local cache cannot force every DNS resolver on the internet to update.
Google's Public DNS documentation explains that cached responses may persist until they expire, and it provides troubleshooting guidance for stale DNS information.
Source: Google Public DNS Troubleshooting.
If the problem continues beyond the expected caching period, contact your domain registrar, DNS provider, or hosting provider with the details of the changes you made.
Include the domain name, record type, expected value, current value, and approximate time of the change.
This gives the support team useful information for investigating the problem.
Yes, DNS changes can contribute to website disruption, especially when a migration is not planned carefully.
Consider a business moving its website from one hosting server to another.
If the old hosting account is immediately cancelled after updating the DNS records, visitors whose resolvers still return the old server's address may encounter an unavailable website.
Meanwhile, other visitors may already be accessing the new server.
A safer approach is to keep the old hosting environment available during the transition, where possible.
Before switching DNS, make sure the new website has been uploaded and tested.
For database-driven websites, plan how to handle new orders, contact form submissions, customer registrations, and other changes during the migration. Running two independent writable copies of a website can create data inconsistencies.
For an online store, this is particularly important because customers could potentially reach different servers during the transition.
DNS changes should therefore be treated as part of a complete migration plan rather than an isolated technical task.
Yes.
DNS does not only control where your website points. It also helps direct email through records such as MX.
When you change your domain's email provider, you may need to update MX records so that incoming messages reach the new mail service.
During the transition, some sending mail servers may still use cached routing information.
If you disable the old email service too early, messages may be delayed, rejected, or delivered to a mailbox you are no longer monitoring.
Before changing email providers, create the required mailboxes on the new platform, configure the necessary DNS records, and test the new service.
Keep the old mail service accessible during the transition where practical, and monitor both environments until the migration is complete.
Also verify SPF, DKIM, and DMARC configurations as applicable to your email service.
These records serve different purposes from MX records, but they are important for email authentication and deliverability.
The best way to manage DNS propagation is to plan for it before making changes.
If you know you will be moving your website, start by documenting your current DNS configuration.
Record your existing nameservers, A records, CNAME records, MX records, and any TXT records used for email authentication or third-party verification.
This information can be valuable if you need to troubleshoot or restore a previous configuration.
Next, prepare the new hosting environment.
Upload your website files, import the database, configure the application, and test the website before directing public traffic to the new server.
If appropriate, reduce the TTL of the records you intend to change well ahead of the migration.
When you are ready, make the DNS changes and verify the results using reliable lookup tools.
Do not immediately cancel the old hosting account.
Continue monitoring the website, email, and other connected services until you are confident that the migration is complete.
For business-critical websites, schedule the transition during a period of relatively low activity and establish a rollback plan before starting.
At SIRSTEVEHQ, we understand that domain management and hosting configuration can be confusing, particularly for business owners who simply want their websites to work reliably.
When connecting a domain to a SIRSTEVEHQ hosting service, it is important to use the correct nameservers or DNS records for your particular hosting platform.
Different hosting environments may have different DNS requirements, so always refer to the configuration information provided with your service.
If you purchased your domain through SIRSTEVEHQ, you can manage its nameserver settings through your Client Area.
For technical assistance with domain resolution, DNS configuration, or hosting-related issues, open a support ticket through your SIRSTEVEHQ Client Area so the technical team can investigate the relevant service.
You can also explore our domain registration and web hosting services at SIRSTEVEHQ.
DNS propagation can be frustrating, especially when you have just launched a website or completed a hosting migration.
You may see the new website while your customers still see the old one. Your mobile connection may work perfectly while your office network continues returning outdated information.
In many cases, this happens because different DNS resolvers are still using cached records.
But not every website issue following a DNS change is caused by propagation.
Incorrect nameservers, missing DNS records, browser caching, CDN caching, and application configuration problems can produce similar symptoms.
The most important lesson is to verify your configuration before making additional changes.
When you understand how DNS caching works and prepare properly for migrations, you can reduce disruption, troubleshoot more confidently, and keep your business website accessible.
There is no fixed DNS propagation time specifically for Nigeria. The duration depends on the DNS records, their TTL values, the resolver used by your internet connection, and other caching behaviour.
Some changes may appear within minutes, while others take hours or longer.
Your mobile network and Wi-Fi connection may use different DNS resolvers with different cached information.
If one resolver has updated and another has not, they may direct you to different servers. However, browser caching or network-specific issues can also cause similar behaviour.
You can prepare for DNS changes by reducing the relevant TTL values ahead of time. You may also clear your local DNS cache to remove outdated information on your device.
However, you generally cannot force all external DNS resolvers to discard their cached records immediately.
No.
Changing nameservers changes which DNS servers are authoritative for your domain. It does not transfer your website files, databases, or email messages to another hosting provider.
You must arrange any required migration separately.
Not necessarily.
If both the old and new hosting environments are correctly configured and remain available during the transition, visitors may continue accessing the website.
However, poor migration planning or incorrect DNS settings can cause downtime.
If your DNS changes are still not working after 48 hours, investigate the configuration rather than assuming that more waiting will solve the problem.
Check the authoritative nameservers, DNS records, DNSSEC settings where relevant, and your hosting application.
Some caching situations can last longer, but persistent errors may indicate a configuration problem.
DNS changes can affect which server visitors reach. If the new server does not have a valid SSL certificate configured for your domain, visitors may encounter HTTPS errors.
DNS propagation itself does not automatically install, renew, or transfer SSL certificates.
Normally, no.
Renewing a domain extends its registration period. It does not ordinarily require you to change its DNS records or nameservers.
However, if the domain has expired or its DNS configuration has been modified, additional steps may be necessary.
Comments (0)
No comments yet. Be the first to comment!