4 ms·
“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 reaso
by Waterluvian 4y ago
“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?
- pinato 4y agoI came across "open" WiFis that required another form of login inside that filtered all HTTP traffic but let through DNS. But no, it's not really useful outside of special circumstances.
- midasuni 4y agoI have WireGuard endpoints of UDP 53, 443 and a high random port - at least one of them tends to work (although not always — one hotel recently only allowed tcp/80 and tcp/443
- gpmcadam 4y agomaybe on a wifi network before authentication when it may allow DNS resolution but not HTTP requests?
- haliskerbas 4y agoCould you shuttle more data through this method to have a browser that works on unauthenticated captive portal wifi networks?
- QuadrupleA 4y agoSimplicity / latency / efficiency - DNS typically just fires off one UDP packet (generally one IP packet & ethernet frame too) and then gets one back (hopefully) and it's done. HTTP requires the TCP 3-way connection handshake, then the out & back roundtrip for request/response, then the 4-way teardown handshake. If it's HTTPS you also need the 4-way TLS <= 1.2 handshake and close notification alert. Although QUIC or TLS 1.3 improves that a bit. Anyway if you're using a 14.4 modem in a rusty bunker at the bottom of the sea you'll notice a substantial improvement :)
- SahAssar 4y ago> 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?
- lazide 4y agoA couple decades ago I did SSH over DNS at the request of a client. It was pretty fun, worked surprisingly well. At the time, exactly zero firewalls stopped it.
- dicknuckle 4y agoooh, MOSH over DNS. Theres all kinds of features to compensate for UDP lossiness built in.
- deleted 4y ago[deleted]
- martinmunk 4y agoI can see the IP echo command be useful to verify if DNS traffic is routed differently than other traffic on a corporate network. Assuming outbound port 53 is not blocked completely on the network that is.
- woevdbz 4y agoMaybe less likely to be blocked by some firewall policy?
- 323 4y ago> During the last decade, several types of software and malware used the DNS protocol for data exchange. https://resources.infosecinstitute.com/topic/bypassing-security-products-via-dns-data-exfiltration/ https://resources.infosecinstitute.com/topic/bypassing-secur...
- mbreese 4y agoThat doesn’t mean the protocol isn’t useful for other purposes. Part of why it’s useful for the malware writers is that it’s highly available and often ignored by firewall rules. That availability can also be used for good.
- Diesel555 4y agoThis 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 https://news.ycombinator.com/item?id=511908
- swznd 4y agoI have used this trick when I in high school grade. Just setup openvpn with port 53 UDP with cheap vps, then connect it, and get unlimited internet access Internet connection in my country is very limited and expensive in that day
- vineyardmike 4y agoYou 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.
- ignoramous 4y ago> I never thought to use DNS as a tunnel Most firewalls drop or hijack packets on port 53.
- 1vuio0pswjnm7 4y agoI 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.
- inopinatus 4y agoMy default is the other way around, I'll question why something that is not a web page uses HTTP as an application-layer protocol when better fitted alternatives usually exist. Add a bonus withering stare for assuming JSON is the only data serialization/interchange format.
- bityard 4y agoI can see using this on an isolated network of iot-like devices that don't quite have the guts or spare bandwidth for HTTPS. MQTT over DNS?