Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DNSGlobe – Rust TUI to watch DNS propagate around the world

github.com

Post reply on HN
Print view View original

51–60 of 74 posts

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

#51

Post by khurs »

oksurerly wrote: post #50
khurs wrote: post #49

Earlier quoted context omitted.

You can do GUI/web easily enough in Rust, but as this is DNS and so most users will be network/sysadmin types, their natural habitat is the terminal. Rust is taking over from C/C++ (as per US Government guidance on using more secure languages) and so is attracting the most hardcore programmers. Libraries for everything: https://crates.io p.s. stop being so grumpy!

> most hardcore programmers > Vibe-coded LOL. LMAO.

Microsoft are using Rust for Windows and Azure

Google are using Rust despite having developed GO

SpaceX and NASA are using Rust for critical life and death systems.

Cloudflare use Rust to obtain extreme high performance.

And many, many more.

Stop being a pain: https://en.wikipedia.org/wiki/Straw_man

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

#52

Post by bcjdjsndon »

khurs wrote: post #49
bcjdjsndon wrote: post #48

What's with the rust community and terminals? I get that gui's are tedious in those languages, but surely you don't have to write everything in rust? Or has rust become the be-all-and-end-all for them?

You can do GUI/web easily enough in Rust, but as this is DNS and so most users will be network/sysadmin types, their natural habitat is the terminal. Rust is taking over from C/C++ (as per US Government guidance on using more secure languages) and so is attracting the most hardcore programmers. Libraries for everything: https://crates.io p.s. stop being so grumpy!

> so most users will be network/sysadmin types, their natural habitat is the terminal.

But we've moved beyond learning commands like a programmer just to operate a program.... Have some respect or at least sympathy for your users

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

#54

Post by josteink »

phikappa wrote: post #32
AndyMcConachie wrote: post #31

Earlier quoted context omitted.

>> The myth of DNS “propagation” needs to die. > What's the actual issue? Are you being frustrated by people laboring under the assumption that DNS records are being sent by carrier pidgeon or something? The actual issue is that some people misunderstand how DNS works, and the notion that records propagate doesn't help people understand it better. It propagates a misunderstanding of DNS.

DNSGlobe – Rust TUI to watch misunderstandings about DNS propagate around the world (github.com/514-labs) There I fixed it for you.

But it's written in Rust so it must be good :D

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

#55

Post by tgv »

jon-wood wrote: post #37
tgv wrote: post #28

Earlier quoted context omitted.

But is there a functional difference between push and pull in this case? Is there something that cannot be explained in terms of propagation? Perhaps timing: there's no reason for propagation to wait an hour or a day. BTW, only last week I explained a potential problem of a DNS change with caching, and it was understood. There doesn't seem to be a need to simplify it.

There is absolutely a reason for propagation to wait an hour or a day, and you've set that value in the TTL field for the record in question. It stands for Time To Live and specifies how long downstream resolvers should cache the last value they saw before querying the authoritative server again, if you set that value to a few seconds then almost every DNS resolver in the world will get updated values within a few se…

The discussion was about caching vs propagation. You're already mixing them.

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

#57

Post by goodpoint »

bcjdjsndon wrote: post #48

What's with the rust community and terminals? I get that gui's are tedious in those languages, but surely you don't have to write everything in rust? Or has rust become the be-all-and-end-all for them?

They are more easily sloppable.

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

#58

Post by _joel »

goodpoint wrote: post #57
bcjdjsndon wrote: post #48

What's with the rust community and terminals? I get that gui's are tedious in those languages, but surely you don't have to write everything in rust? Or has rust become the be-all-and-end-all for them?

They are more easily sloppable.

I doubt that, but cool story bro'

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

#59

Post by JdeBP »

inigyou wrote: post #42
teddyh wrote: 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.

What do you call it when an application queries systemd-resolved and systemd-resolved queries PiHole and PiHole queries your home router and your home router queries your ISP? What is that if not a chain?

Forwarding proxy DNS servers leading to a (yes) single resolving proxy DNS server at the end.

* https://jdebp.uk/FGA/dns-server-roles.html

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

#60

Post by teddyh »

walrus01 wrote: post #45
teddyh wrote: post #2

The myth of DNS “propagation” needs to die. Changed DNS entries do not “propagate”. The old cached DNS entries in DNS resolvers simply expire, in an arbitrary order. DNS resolvers are not linked geographically; there is no “propagation”. If this tool was querying a list of widely-used public (and/or private) DNS resolvers, it might be useful. But pretending that DNS entries propagate geographically does not do anyone…

> The old cached DNS entries in DNS resolvers simply expire, in an arbitrary order. I really wish that was so. There's lots of weird resolvers out there used by weird ISPs that don't properly respect the TTL value. Setting TTL to some really low number a full day before making a major change is no guarantee that your zone will expire in a bunch of places. All kinds of weird ISPs try to do things with the dns results…

It’s still arbitrary, with no geographical (or other) form of propagation.
Post reply on HN