Live data from Hacker News

DNS Toys

dns.toys

81–90 of 111 posts

Re: DNS Toys

#82

Earlier quoted context omitted.

> Although QUIC or TLS 1.3 improves that a bit. On a TLS1.3 QUIC connection with a session supporting 0-rtt would DNS still require less round trips?

But you generally don't wanna keep a "connection" open to everyone in every scenario, like the one in the post.

You don't need a connection, you just need to have a session cached that you can resume. That's how 0-RTT works.

Re: DNS Toys

#83

“Why? For fun.” I love this. It doesn’t need a reason to exist. It’s interesting on its own. That being said, can anyone think of additional interesting reasons for why this would be useful rather than the same toys over HTTP?

This may work on pay to use Wi-Fi. There was a previous interesting post here about tunneling through DNS on airplane or other pay to use Wi-Fi. https://news.ycombinator.com/item?id=511908

You have no idea how badly I was looking for a way to tunnel via airplane wifi. Even going as far as trying to use the "free tier" fb messenger access to move packets. Now the ToS have a very low bandwidth limit on the free tier (eg. 100mb), so I'm not sure if it'd work for any real application.

I never thought to use DNS as a tunnel, but I have seen some pretty interesting loopholes that I was trying to find. Some airline's captive portal used to rely on some google service (captcha probs), and for a period of time didn't block any google-owned IP address that wasn't a consumer website (eg search, yt) so GCP and developer docs would load if you had the URL. I couldn't reliably get to user-generated content through it though.

Re: DNS Toys

#84

Earlier quoted context omitted.

This may work on pay to use Wi-Fi. There was a previous interesting post here about tunneling through DNS on airplane or other pay to use Wi-Fi. https://news.ycombinator.com/item?id=511908

You have no idea how badly I was looking for a way to tunnel via airplane wifi. Even going as far as trying to use the "free tier" fb messenger access to move packets. Now the ToS have a very low bandwidth limit on the free tier (eg. 100mb), so I'm not sure if it'd work for any real application. I never thought to use DNS as a tunnel, but I have seen some pretty interesting loopholes that I was trying to find. Some a…

> I never thought to use DNS as a tunnel

Most firewalls drop or hijack packets on port 53.

Re: DNS Toys

#86
post #9

Awesome! Surprised to see the resolver correctly handle my typo: $ dig seat2222tle.time @dns.toys +short "Seattle (America/Los_Angeles, US)" "Sat, 11 Jun 2022 08:22:42 -0700"

It is probably levenshtein distance

probably just removing numbers etc

dig seattlr.time @dns.toys +short

Re: DNS Toys

#87
post #47

This is awesome but I'm getting NXDOMAIN when I try to use it. Am I doing something wrong, perhaps something to do with EDNS? $ dig 42km-mi.unit @dns.toys ; > DiG 9.16.27-Debian > @dns.toys 42km-mi.unit ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER

You should ask for a TXT record, not an A record.

Re: DNS Toys

#88

To others, yr.no is a free weather service with API: https://developer.yr.no I see that dns.toys use it.

Out of curiosity, I looked at the headers after clicking on your link and I found that it was sending Referrer as: https://news.ycombinator.com which is not an issue. But then I refreshed the page and saw the same Referrer again. So I checked where it was getting the Referrer from and it was not storing anything in localStorage, not in URL, nor in sessionStorage, nor in cookies. Any idea where the site was getting the Referrer from?

Re: DNS Toys

#89

Earlier quoted context omitted.

You have no idea how badly I was looking for a way to tunnel via airplane wifi. Even going as far as trying to use the "free tier" fb messenger access to move packets. Now the ToS have a very low bandwidth limit on the free tier (eg. 100mb), so I'm not sure if it'd work for any real application. I never thought to use DNS as a tunnel, but I have seen some pretty interesting loopholes that I was trying to find. Some a…

> I never thought to use DNS as a tunnel Most firewalls drop or hijack packets on port 53.

I have experienced this, i.e., hijacking, but I would respectfullly contest the term "most". But perhaps the statement was only referring to airports. I could be wrong but I like to think it is a minority of networks that hijack or block DNS. For example, a minority of consumer ISPs, other networks controlled by third parties (airports, hotels, etc.) or countries that conduct extremely aggressive internet censorship.

Re: DNS Toys

#90

I guess you could deliver web pages over DNS too, if you wanted... though I'm not sure why you'd want to. Instead of DoH it would be HoD.

I experimented with this over 10 years ago. I used a modified dnstxt from djbdns and put MIME headers and HTML into TXT RRs. tinydns allows a wider variety of bytes in RRs than other DNS software. At least, it was generally less restrictive than the other DNS software available at that time.
Post reply on HN