Live data from Hacker News

DNSGlobe – Rust TUI to watch DNS propagate around the world

github.com

71–74 of 74 posts

Re: DNSGlobe – Rust TUI to watch DNS propagate around the world

#71
post #5

Earlier quoted context omitted.

That's what the tool is doing - querying a bunch of public resolvers around the world to see the state of what they resolve to. Since end users usually use DNS servers close to their location, this gives an idea, around the world, of who sees what. Agreed, this is a cache that expires and refreshes from the source DNS server. It just looks like a virus that propagates when the cache expires.

> It just looks like a virus that propagates when the cache expires. No it does not. The changes do not happen geographically. There is no geographical connection whatsoever. Calling the tool “DNSGlobe”, and displaying a map, only further reinforces the myth.

dnspatter

(dns spatter + dns patter)

Re: DNSGlobe – Rust TUI to watch DNS propagate around the world

#72
post #63
post #38

Earlier quoted context omitted.

> local vs intermediary vs backbone TTLs This is an example of the myth in action. There are no such things. There is a single resolver, which you use, and a set of authoritative server, which that resolver will query when the TTL in the resolver’s cache times out. There is no chain of resolvers.

> There is no chain of resolvers. There absolutely can be a chain of resolvers. It's very common to run a caching recursive resolver on client nodes that sends its requests to an external recursive resolver (usually the network owner's suggested server). Nicer local caching resolvers will recurse themselves if/when the configured forwarding destination is unavailable. Some decades ago, it wasn't unusual for ISPs to r…

> We could agree to use percolate though, it was suggested elsewhere in the thread and it's a fun word and easier to spell.

A more accurate term would be to talk about waiting until old DNS entries “age out”, or “expire”.

Re: DNSGlobe – Rust TUI to watch DNS propagate around the world

#73
post #62

Earlier quoted context omitted.

Thanks for the feedback!

Sort is working! Another suggestion is to allow the user to edit the DNS resolver list -- in the running program itself. An ADD/DELETE feature would be useful (to me at least). A quick note... when I open the app I only see the left pane. I wouldn't have known there was a map had I not previously seen/read about it. Thanks :)

I added runtime by adding a resolver and removing it. I also made the map responsive.
Post reply on HN