Check whether a DNS record change has finished propagating worldwide after updating a domain.
Watch propagation live in a terminal instead of refreshing a website checker repeatedly.
Spot resolvers that disagree with the majority answer during a DNS migration.
See how a GeoDNS zone answers for a different network location using EDNS Client Subnet.
| 514-labs/dnsglobe | zerx-lab/fluxdown | tobilg/polyglot | |
|---|---|---|---|
| Stars | 910 | 820 | 810 |
| Language | Rust | Rust | Rust |
| Setup difficulty | easy | easy | easy |
| Complexity | 2/5 | 2/5 | 2/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Dnsglobe is a terminal application that checks how a DNS record has spread across the internet. When you change a domain's DNS settings, it takes time before every server around the world knows about the change, and dnsglobe watches that process happen. It sends the same query to 34 public DNS resolvers scattered across regions like North America, Europe, Russia, the Middle East, East Asia, and the southern hemisphere, then compares their answers side by side in a table right in your terminal. Answers that agree get grouped together, so a domain using several servers that answer differently on purpose does not get flagged as broken, only genuinely conflicting answers are marked as different. A progress style gauge shows what share of resolvers agree with the majority. If your terminal window is wide enough, dnsglobe also draws a small world map or a spinning globe on the side, with a colored dot for each resolver showing whether it agrees, differs, errored, or is still waiting on a reply. You can toggle between the flat map and the globe view by hand or let it switch automatically based on window width. For big cloud DNS providers that route different users to different nearby servers, dnsglobe can also ask which physical location actually answered you, and there is an option to fake your location using something called EDNS Client Subnet, so you can see how the DNS answer looks from a different network's point of view. You can install it through Homebrew, cargo, the Arch Linux AUR, Nix, or a prebuilt binary from GitHub releases. Once running, you type a domain name, or pass one on the command line, and it starts checking immediately, refreshing every 30 seconds until every resolver reports the record has fully propagated. There is also a plain, non interactive mode for scripts. Settings like custom resolver lists can be saved in a config file. The project is released under the MIT license.
A terminal tool that checks how a DNS record has spread across dozens of public servers worldwide, shown live on a map or globe.
Mainly Rust. The stack also includes Rust, Ratatui, DNS.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.