New Zealand DNS Propagation Checker
Run a DNS lookup against 3 resolvers located in New Zealand — Auckland · Auckland · Hamilton.
- Resolved
- No answer
- Checking
-
Auckland
New Zealand
—
-
Auckland
New Zealand
—
-
Hamilton
New Zealand
—
What checking DNS from New Zealand tells you
A DNS resolver keeps a cached copy of each record for as long as its time-to-live allows, and does so separately in every location. A change you have published can be live on one resolver while another still serves the old answer.
Checking from New Zealand looks up the record on servers inside the country, so you see what people there actually get rather than what a resolver on another continent returns.
This matters most right after you edit a record: an update visible on a global resolver like 8.8.8.8 can still be stale at a local ISP in New Zealand until its cached copy expires. The check confirms the new value has reached the resolvers your New Zealand visitors depend on.
In 2011 Telecom New Zealand was split in two. Chorus took the copper and fibre lines and became the wholesale network almost every broadband connection still rides; the retail arm kept the customers and, in 2014, the Spark name. So whichever brand sells the plan — Spark, One NZ, or 2degrees — the last mile is usually Chorus fibre, and the resolver a household gets is whatever its retail ISP hands out over DHCP, not one it chose.
New Zealand also sits a long way from the servers it talks to. Most international traffic leaves on the Southern Cross cables, which Spark part-owns, landing in Sydney and on the US west coast; the 2022 Southern Cross NEXT link is the lowest-latency hop to the United States. That distance is the reason to check from inside the country: it shows whether your CDN serves Aucklanders from an Auckland edge or from Sydney, and whether a record change has reached the caches Spark, One NZ and 2degrees actually run.
- Spark122.56.237.1 Incumbent (ex-Telecom New Zealand); default resolver for most households
- One NZ Former Vodafone New Zealand; hands out DNS over DHCP
- 2degrees118.148.1.10 Third national ISP; default resolver on its network
How DNS propagation works
Every DNS record carries a time-to-live: the seconds a resolver may keep its cached answer before asking again. Change a record and resolvers holding the old value keep serving it until that timer runs out.
Propagation is this expiry playing out across many independent resolvers, so a lower time-to-live set ahead of a change makes it take effect sooner. There is no fixed waiting period — each record's time-to-live decides how long the old answer lingers.
Frequently Asked Questions
Why do DNS servers in New Zealand return different results than 8.8.8.8?
Two things cause it. Each resolver caches independently, so one can hold an older answer than another.
And content delivery networks reply based on where the asking resolver is, steering a resolver in New Zealand toward a nearby edge node.
Both answers can be correct at the same time for their own location.
How long until a DNS change is visible in New Zealand?
It depends on the record's time-to-live, not on the country.
Resolvers in New Zealand keep the previous answer until their cached copy expires, then pick up the new one.
If you lowered the time-to-live before making the change, it appears sooner; otherwise the old value can persist until the original timer elapses.
Which DNS server should users in New Zealand use?
For most people the resolver their internet provider assigns is fine and usually the lowest latency.
Anyone who wants an alternative can point to a public resolver reachable from New Zealand, such as Cloudflare (1.1.1.1) or Google (8.8.8.8); the right choice depends on whether you value speed, privacy, or filtering.
Why check DNS from New Zealand specifically?
Because it shows what visitors in New Zealand actually resolve, which can differ from a global lookup.
If your audience is in New Zealand, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
Does New Zealand filter or block domains at the DNS level?
Only narrowly. The Department of Internal Affairs runs a voluntary Digital Child Exploitation Filtering System (DCEFS) that Spark, One NZ, 2degrees and most other providers connect to, covering roughly 95% of users. It matches traffic against a secret list of URLs hosting child sexual abuse material and diverts those via BGP to a DIA block page. There is no piracy or general-content blocklist, and no court-ordered site blocking of the kind common in Europe. For any ordinary domain a New Zealand resolver returns the same record a global one does, so a check here reflects propagation and CDN geography, not filtering.
Why can a New Zealand DNS check disagree with one from Australia?
Distance and routing. New Zealand's international traffic rides the Southern Cross cables to Sydney and the US west coast, and CDNs sometimes serve the country from a Sydney edge rather than an Auckland one, so the IP a Spark or 2degrees resolver gets can differ from what a Sydney resolver sees. Almost every New Zealand broadband line also runs over Chorus's wholesale fibre no matter which retailer bills it, so a local check tells you whether your record reached the resolvers those retailers run and whether visitors get a nearby edge or a slower hop across the Tasman.
