A global DNS propagation checker for your terminal — a Rust TUI that queries 34 public DNS resolvers around the world in parallel, compares their answers, and shows the propagation of your record on a world map.

Think dnschecker.org / whatsmydns.net, but in your terminal, with watch mode: start a check and it re-polls until the record has propagated everywhere.

Resolvers span the global anycast networks (Google, Cloudflare, Quad9), North America, Europe, Russia, the Middle East, East Asia, and the southern hemisphere (Telstra AU, SafeSurfer NZ, UOL BR) — each queried directly, so you see every server's own current view of the record.

Each resolver is queried directly (no cache, EDNS0, TCP fallback for truncated answers), so what you see is each server's own current view of the record. Answers sharing any record are grouped together — so round-robin DNS (each resolver caching a different subset of an IP pool) counts as one consistent answer, not twenty conflicting ones. The propagation gauge shows how many resolvers are in the majority group; outliers are flagged ≠ DIFFERS once all results are in.

On terminals ≥150 columns wide, a world map appears on the right with one dot per resolver, colored by status (green agrees, magenta differs, red error, yellow in flight).

Anycast networks are asked which of their sites is answering you: Quad9 (TXT id.server.on.quad9.net), Cloudflare (CH TXT id.server), Google (egress subnet via TXT o-o.myaddr.l.google.com matched against TXT locations.publicdns.goog), OpenDNS (TXT debug.opendns.com), CleanBrowsing, and Neustar UltraDNS. The discovered site shows in the Loc column as →YUL-style codes, and the resolver's map dot moves to the POP actually serving your queries.

Install:

brew install 514-labs/tap/dnsglobe   # Homebrew (macOS/Linux)
cargo install dnsglobe               # from crates.io
yay -S dnsglobe                      # from archlinux aur (compile from source)
yay -S dnsglobe-bin                  # from archlinux aur (install prebuilt binary)
# or grab a prebuilt binary from the GitHub Releases page

Run:

dnsglobe                            # start empty, type a domain
dnsglobe example.com                # query immediately and watch
dnsglobe example.com TXT            # same, starting on TXT records
dnsglobe --once example.com TXT     # no TUI: print results, exit (for scripts)

Optionally, add your own resolvers — or replace the built-in list entirely — with a TOML config file at ~/.config/dnsglobe/config.toml ($XDG_CONFIG_HOME/dnsglobe/config.toml if set). Set DNSGLOBE_CONFIG to use a different path.

# Set to true to replace the built-in list instead of extending it —
# e.g. to watch propagation across your own nameservers only.
replace = false

[[resolvers]]
name = "Corp DNS"        # required — shown in the Resolver column
ip = "10.0.0.53"         # required — IPv4 or IPv6, queried on port 53
location = "HQ"          # optional — Loc column / location sort
lat = 40.7               # optional — position on the world map;
lon = -74.0              #            omit both to leave it off the map

[[resolvers]]
name = "NS1 (public)"
ip = "198.51.100.53"

Invalid config (bad IP, unknown key, lat without lon, replace = true with no resolvers) is reported at startup with the offending entry named.

• Several resolvers are anycast networks, so the responding node is the one nearest to you. Networks with an identification query report the actual answering site (→YUL); for the rest the location column is the operator's home region.
• The built-in resolver list lives in src/resolvers.rs; use the config file above to extend or replace it without rebuilding. Every built-in entry was verified to answer external queries; many well-known ISP resolvers (and, notably, all major African ones) refuse queries from outside their network, so they can't be included.

Made with ❤️ by the folks working on 514.ax.