How long does DNS propagation take?

DNS propagation time is primarily determined by the TTL (Time to Live) value of the previous DNS record. A TTL of 3600 means resolvers can cache the old record for up to one hour. To speed up a planned DNS change, reduce the TTL to 300 seconds at least 24–48 hours before making the change.

How do I check if my DNS changes have propagated worldwide?

Enter your domain into the DNS propagation checker and select the record type. The tool queries from 65+ nodes across Europe, North America, Asia, and other regions. Nodes are highlighted green when they return the new value and red when they still return the old cached value. The world map shows propagation progress at a glance.

Why do some locations still show the old DNS record after I made a change?

Resolvers around the world cache DNS records for the duration of the record's TTL. Until that cache expires, different users in different regions may receive different DNS responses. This is normal — the old value will be replaced automatically once the TTL period has passed on each individual resolver.

Does changing my A record affect my MX record propagation?

No. Each DNS record type propagates independently. Changing your A record has no effect on the propagation status of your MX, CNAME, or TXT records. Use the record type selector to test each record type individually when verifying a full DNS migration.

github.com 的 DNS 傳播檢測

If set, nodes are highlighted green/red based on match.

正在檢測傳播…

0 / 0

已傳播

不一致

無記錄

永久連結 |

DNS 傳播檢測 github.com

位置	解析值	TTL	狀態
Albania, Tirana
Australia, Sydney
Bosnia and Herzegovina, Novi Travnik
Bulgaria, Sofia
Brazil, São Paulo
Canada, Montreal
Switzerland, Bern
Switzerland, Zurich
China, Hohhot
Cyprus, Larnaca
Germany, Nuernberg
Germany, Frankfurt am Main
Germany, Limburg
Germany, Frankfurt am Main
Germany, Frankfurt am Main
Germany, Koblenz
Germany, Langen
Germany, Frankfurt am Main
Denmark, Glostrup Municipality
Spain, Bilbao
Spain, Barcelona
Finland, Helsinki
Finland, Helsinki
France, Gravelines
France, Paris
United Kingdom, London
Hong Kong, Hong Kong
Croatia, Zagreb
Hungary, Budapest
Israel, Petach Tikwa
Israel, Netanja
India, Bangalore
Iran, Tehran
Iran, Tehran
Iceland, Reykjavik (Miðborg)
Italy, Como
Japan, Tokyo
South Korea, Seoul
Kazakhstan, Almaty
Lithuania, Pilaite
Latvia, Riga
Moldova, Chisinau
Netherlands, Amsterdam
Netherlands, Amsterdam
Netherlands, Amsterdam
Netherlands, Amsterdam
Netherlands, Eygelshoven
Norway, Oslo
Poland, Warsaw
Romania, Bacău
Romania, Bucharest
Serbia, Belgrade
Russia, Moscow
Singapore, Singapore
Tor, Onion
Tor, Onion
Tor, Onion
Turkey, Istanbul
Turkey, Istanbul
Ukraine, Khmelnytskyi
United States, Dallas
United States, Los Angeles
United States, Houston
United States, Miami
South Africa, Johannesburg

什麼是 DNS 傳播？

DNS 傳播是指 DNS 記錄變更擴散至全球各地解析器所需的時間。當你更新 A 記錄、切換名稱伺服器或修改 MX 記錄後，變更不會立即在全球生效。各地解析器會在記錄的 TTL（Time to Live）到期前持續快取舊值，因此不同地區的使用者可能在同一時間收到不同的 DNS 回應。

傳播需要多長時間？

傳播時間主要取決於原 DNS 記錄的 TTL 值。TTL 為 3600，代表解析器最多可將舊記錄快取一小時；TTL 為 86400（24 小時）則可能導致整整一天的傳播延遲。若需加速傳播，建議在執行 DNS 變更前 24 至 48 小時將 TTL 降低至 300 秒，確保切換後解析器能快速取得新值。

本工具顯示什麼

本工具從分布在歐洲、北美、亞洲及其他地區的 65+ 個真實解析節點查詢 DNS。每個節點顯示目前的解析值與 TTL。若輸入預期值（如新的 IP 位址），回傳該值的節點以綠色標記，仍回傳舊值的節點以紅色標記。世界地圖可直觀呈現傳播進度的地理分布。

常見 DNS 變更情境

最常見的使用情境包括：將網站遷移至新伺服器（A 記錄變更）、切換 DNS 服務商（NS 記錄變更）、驗證郵件設定（MX、TXT/SPF、DKIM），以及確認 CDN 記錄更新（CNAME）。各類記錄獨立傳播——A 記錄的變更不影響 MX 記錄的傳播狀態。請透過記錄類型選擇器逐項檢測。