South Korea DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in South Korea — Dong-gu · Ansan-si · Hanam · Ansan-si · Gangseo-gu · Hanam.
- Resolved
- No answer
- Checking
-
Dong-gu
South Korea
—
-
Ansan-si
South Korea
—
-
Hanam
South Korea
—
-
Ansan-si
South Korea
—
-
Gangseo-gu
South Korea
—
-
Hanam
South Korea
—
What checking DNS from South Korea 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 South Korea 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 South Korea until its cached copy expires. The check confirms the new value has reached the resolvers your South Korea visitors depend on.
Korea's default resolver is practically a cultural artifact: 168.126.63.1, KT's Kornet server, has been the number Koreans type into network settings since the dial-up era. The market it serves is dense, fast, and centralised on a few carriers, so propagation inside Korea tends to be quick and uniform once TTLs expire.
The wrinkle is regulatory. Korean ISPs redirect blocked domains, gambling and certain other categories, to an official warning page, warning.or.kr, and they do it inside the resolver and network layer.
A lookup from inside Korea tells you whether your records have arrived, and it catches something no outside resolver can: a domain quietly resolving to the warning page instead of your servers.
- KT Kornet168.126.63.1 The country's default resolver for decades
- LG Uplus Third big carrier; an independent second reading
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 South Korea 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 South Korea 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 South Korea?
It depends on the record's time-to-live, not on the country.
Resolvers in South Korea 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 South Korea 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 South Korea, 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 South Korea specifically?
Because it shows what visitors in South Korea actually resolve, which can differ from a global lookup.
If your audience is in South Korea, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
What is warning.or.kr and why would my domain point there?
It is the notice page Korean ISPs must show for domains blocked by the Korea Communications Standards Commission, mostly gambling, pornography and pirated content. If a Korean lookup of your domain lands on the warning page while the rest of the world resolves it normally, your domain, or something sharing its infrastructure, has been listed.
Is 168.126.63.1 a public resolver like 8.8.8.8?
Functionally yes: it answers queries, and Koreans memorised it the way the rest of the world memorised Google's. It is operated by KT as the resolver for its subscribers, applies the same national blocking rules as other Korean ISPs, and answers from inside Korea, which is what makes it a useful test point.
