Troubleshooting Propagation
Domain propagation is the process where updated DNS records spread across the internet’s global network of servers. When you modify your domain’s settings, these updates must be cached by Internet Service Providers (ISPs) worldwide. This synchronization period typically lasts between 24 to 48 hours, though local visibility often resolves sooner depending on your Time to Live (TTL) settings.
For businesses and domain investors in the New Zealand market, waiting for a new .nz domain or a website migration to go live can be a frustrating experience. You have updated your nameservers, but you still see the old site, or worse, an error page. This phenomenon, known as DNS propagation, is a fundamental part of how the internet functions. While you cannot force the entire internet to update instantly, there are specific strategies to monitor progress and troubleshoot local caching issues that are common with NZ ISPs like Spark, One NZ, and 2degrees.
What is DNS Propagation?
To understand propagation, you must first understand the Domain Name System (DNS). The DNS is essentially the phonebook of the internet. Computers communicate using numbers called IP addresses (e.g., 192.0.2.1), but humans prefer memorable names like example.co.nz. DNS servers translate these domain names into IP addresses.
When you purchase a domain or switch web hosting providers, you update your DNS records (specifically the Nameservers or A Records) to point to a new location. However, this change is not instantaneous. The internet is composed of millions of servers, and for efficiency, they “cache” (store) DNS information for a set period. Propagation is the time it takes for every server across the globe—from the root .nz servers to your local ISP’s recursive resolver—to clear their old cache and accept the new information.
How to Check Domain Propagation in NZ?
Because propagation occurs physically across different geographic locations, your website might be visible to a user in Auckland but invisible to a user in London. To accurately assess the status of your domain, you need to use global propagation tools that ping your domain from multiple servers worldwide.
Top Tools for Monitoring DNS Status
While you cannot speed up the servers, you can watch the progress. Here are the industry-standard tools for checking domain propagation:
- DNSChecker.org: This is perhaps the most popular tool. It checks your domain against a list of over 25 DNS servers located in various countries. Look for green ticks next to New Zealand or Australian servers to confirm local propagation.
- WhatsMyDNS.net: Similar to DNSChecker, this tool provides a visual map. It is particularly useful for visualizing if the propagation is stuck in a specific region (e.g., Oceania vs. Europe).
- Google Admin Toolbox Dig: For a more technical view, Google’s tool allows you to query specific record types (A, CNAME, MX) directly from Google’s infrastructure.
When using these tools, ensure you are checking the correct record type. If you changed hosting, check the A Record. If you changed email providers, check the MX Record. If you moved the entire domain management, check the NS (Nameserver) Record.
Why Does Propagation Take Up to 48 Hours?
The 48-hour rule is a standard disclaimer provided by registrars, but in modern infrastructure, it is often much faster. However, several factors dictate exactly how long you wait.
The Role of TTL (Time to Live)
Every DNS record has a TTL value, measured in seconds. This value tells servers how long they should store the information before checking for an update.
For example:
- TTL 3600: The record is cached for 1 hour.
- TTL 86400: The record is cached for 24 hours.
If your previous TTL was set to 24 hours, servers will not look for your new IP address until that timer expires. This is the primary driver of propagation delays.
Registry Updates
For .nz domains, the updates must also propagate from the InternetNZ registry down to the root servers. While .nz is generally very efficient, slight delays can occur at the registry level before the changes are pushed to the global root DNS servers.
NZ ISP Caching Issues: Spark, One NZ, and 2degrees
A common scenario for New Zealand users is that a client overseas can see the new website, but you—sitting in Wellington or Christchurch—cannot. This is often due to aggressive caching by local Internet Service Providers (ISPs).
ISPs like Spark, One NZ (formerly Vodafone), and 2degrees maintain their own recursive DNS resolvers. To reduce bandwidth usage and speed up browsing for their customers, they cache DNS records. Sometimes, these ISPs ignore the TTL settings and hold onto old data longer than they should. This results in a “stale” cache.
If you suspect your ISP is showing you an old version of the site, you can try accessing the site via a mobile data connection (disconnecting from Wi-Fi). If the site loads correctly on 4G/5G but not on your fibre connection, the issue is isolated to your ISP’s DNS cache.
How to Flush Your Local DNS Cache?
Before blaming the ISP, ensure your own computer isn’t the problem. Your operating system also builds a cache of DNS records to load websites faster. Flushing this cache is the first step in troubleshooting.
Flushing DNS on Windows
- Press Windows Key + R to open the Run dialog.
- Type
cmdand press Enter. - In the command prompt, type the following command and press Enter:
ipconfig /flushdns - You should see a message: “Successfully flushed the DNS Resolver Cache.”
Flushing DNS on macOS
The command varies depending on your version of macOS, but for most modern versions (macOS Monterey, Big Sur, Catalina), follow these steps:
- Open the Terminal app (Command + Space, type “Terminal”).
- Type the following command and press Enter:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Enter your administrator password when prompted.
Flushing DNS in Google Chrome
Even after flushing your OS cache, your browser might still be holding onto old data. Chrome has its own internal DNS cache.
- Open a new tab and navigate to:
chrome://net-internals/#dns - Click the button labeled “Clear host cache”.
Advanced Troubleshooting: Bypassing ISP DNS
If you have flushed your local cache and confirmed via external tools that the domain has propagated, but you still cannot see it, your ISP is likely the bottleneck. You can bypass your ISP’s DNS servers by configuring your computer to use public DNS resolvers.
Switching to Google Public DNS or Cloudflare
Public DNS servers often update faster than local ISP servers.
- Google DNS: 8.8.8.8 and 8.8.4.4
- Cloudflare DNS: 1.1.1.1 and 1.0.0.1
How to change DNS settings on Windows 10/11:
- Go to Settings > Network & Internet.
- Select your connection (Wi-Fi or Ethernet).
- Click on “Edit” next to IP assignment or DNS server assignment.
- Select “Manual”, toggle on IPv4, and enter the Preferred DNS (e.g., 1.1.1.1) and Alternate DNS (e.g., 1.0.0.1).
- Save and restart your browser.
Using the Hosts File (For Developers)
If you need to work on a site immediately before propagation is complete, you can “trick” your computer into going to the new server IP by editing your hosts file.
Warning: This is an advanced technique. You must remember to remove the entry once propagation is complete, or you may face connection issues in the future if the server IP changes again.
- Open Notepad as an Administrator.
- Open the file located at
C:\Windows\System32\drivers\etc\hosts. - Add a line at the bottom:
123.45.67.89 yourdomain.co.nz(replace with your new server IP and domain). - Save the file. Your computer will now map that domain directly to that IP, ignoring DNS completely.
Conclusion
Troubleshooting domain propagation in New Zealand requires patience and a systematic approach. While the global internet infrastructure takes time to sync, understanding the difference between a global propagation delay and a local caching issue empowers you to take action. By utilizing propagation checkers, flushing your local DNS, and potentially bypassing your ISP’s resolvers, you can verify your domain’s status and get back to business faster.
People Also Ask
How long does .nz domain propagation take?
Propagation for .nz domains typically takes between 2 to 24 hours. However, the global standard allowance is up to 48 hours to account for all ISP caches worldwide to clear.
Can I speed up DNS propagation?
You cannot speed up propagation after the change has been made. However, if you plan ahead, you can lower your TTL (Time to Live) settings to 300 seconds (5 minutes) a day before the migration to ensure faster updates.
Why is my domain working on mobile but not on Wi-Fi?
This indicates a local caching issue. Your mobile network (4G/5G) has likely updated its DNS records, while your home or office ISP (Wi-Fi) is still holding onto the old “stale” data.
What is the command to check DNS propagation?
To check where your computer is pointing a domain, use the nslookup command in Windows or Terminal. Type nslookup yourdomain.co.nz to see the IP address your system is resolving to.
Does clearing browser cache fix DNS propagation?
Sometimes. Browsers like Chrome have their own internal DNS cache. Clearing your browser data or flushing the internal sockets via chrome://net-internals/#dns can help if the OS cache is already clear.
What does NXDOMAIN mean during propagation?
NXDOMAIN stands for “Non-Existent Domain.” If you see this during propagation, it means the DNS server you are querying does not yet have a record for your domain, or the domain registration hasn’t fully completed.
