31–40 of 71 posts
I like it. I just wish that dig were installed on every platform. I'm always annoyed that it isn't available on Windows and when I checked Debian doesn't have it by default (though easily installable.) OpenBSD and Mac OS X have it though so that's good.
Surely Windows has some kind of DNS lookup tool!
Earlier quoted context omitted.
Oh interesting - those circumferences are actually closer than I assumed they would be!
Yeah, it's pretty minor stuff of no real import to many ... unless someone had a background in geodesy and had to measure fields on a oblate spheroid with fragmented moving plates girt by sloshing fluids.
(Drawing from 1-semester CCNA course in uni) Since DNS operates over UDP, isn't the amount of data that can be safely transferred effectively bottlenecked by the smallest page size between the routers that reach your device? DNS is served in one chunk, right?
Can someone ELI5 for the idiot in the thread. I know it's for fun but I don't get it. Also how's it's working? I'm aware it's my ignorance.
A IP = ...1
AAAA IP = ...2
Where 'a' is the type of record. But there are other types of records:
TXT gender = 'male'
So there's a few assumptions here about DNS that are normally true:
1. People are using DNS as a switch board to other services.
2. The values in the switchboard are normally static.
With this setup they're doing something completely different because they're serving back changing values based on the domain. To do this you would need to write a custom DNS server (though the DNS protocol is quite simple.) The reasons this is a clever hack though are as follows:
1. DNS is one of the most widely used and supported protocols. All mainstream programming libraries support it. This includes numerous command-line tools already in operating system. By providing this as a service over DNS it provides an elegant way for command-line tools and libraries to access services with minimal dependencies.
2. It challenges the way the DNS system should be used by tipping the normal assumptions behind its use on its head (direct usage for information, dynamic content for values.) This makes it possible to use DNS directly as an application service rather than as a switch board operator for regular internet services.
3. DNS is so integral that a complex integration wouldn't be needed to add it to existing software. A DNS request is arguably more straight-forwards than a typical web API. Chances are this also has benefits for censorship resistance, too.
All in all a clever hack.
I like it. I just wish that dig were installed on every platform. I'm always annoyed that it isn't available on Windows and when I checked Debian doesn't have it by default (though easily installable.) OpenBSD and Mac OS X have it though so that's good.
You don't need to use dig. nslookup or host work also. Surely Windows has some kind of DNS lookup tool!
Resolve-DnsName(Drawing from 1-semester CCNA course in uni) Since DNS operates over UDP, isn't the amount of data that can be safely transferred effectively bottlenecked by the smallest page size between the routers that reach your device? DNS is served in one chunk, right?
- [1] https://jvns.ca/
- [2] https://dns-lookup.jvns.ca/
- [3] https://messwithdns.net/
Seems like we can just build light weight APIs on top of this. And port 53 is always open too just 80 and 443.