'But it loads on MY phone!' — the classic DNS confusion. Here is why changes appear unevenly and how to test like a pro.
Why propagation is uneven DNS results are cached everywhere: your phone, your browser, your ISP's resolver, public resolvers. Each cache keeps a record until its TTL (time-to-live) expires — minutes to 48 hours. So a change is 'propagated' gradually, person by person, resolver by resolver.
The checker's toolkit 1. whatsmydns.net: see your record's status across global resolvers on a map 2. nslookup/dig from a terminal: query a SPECIFIC resolver (1.1.1.1, 8.8.8.8) and compare answers 3. Your own cache: flush it (Windows: ipconfig /flushdns; phone: airplane-mode toggle often suffices) and retry
The three rules that prevent panic 1. Nothing is 'broken' during propagation — old and new answers coexist by design 2. Lower TTL to 300s a DAY BEFORE a planned change; raise it after things settle 3. Test through a fresh resolver, never just your own browser
The email warning Mail records (MX) propagate like everything else — during a nameserver switch, some mail may land at the old server for hours. Keep both mailboxes alive for a few days during migrations; forward anything that arrives late.
Kairalmas's DNS status page shows your records as the authoritative nameservers see them — the ground truth that ends 'is it just me?' conversations.