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

DNS Toys

dns.toys

Post reply on HN
Print view View original

71–80 of 111 posts

Re: DNS Toys

#71

Post by anonu »

really cool. wonder if it does any checks to ensure packet response stays within 512 bytes to avoid packet frags.

Re: DNS Toys

#72

Post by dicknuckle »

lazide wrote: post #36
QuadrupleA wrote: post #16

Earlier quoted context omitted.

Simplicity / 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 Anyway if you're using a 14.4 modem in a rusty bunker at the bot…

A 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.

ooh, MOSH over DNS. Theres all kinds of features to compensate for UDP lossiness built in.

Re: DNS Toys

#73

Post by lillecarl »

dicknuckle wrote: post #72
lazide wrote: post #36

Earlier quoted context omitted.

A 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.

ooh, MOSH over DNS. Theres all kinds of features to compensate for UDP lossiness built in.

Most tunnel protocols are UDP these days, vxlan, geneve, wireguard etc... Just because it doesn't guarantee delivery, meaning you don't get the retransmit amplification you'd get with TCP over TCP.

Re: DNS Toys

#74

Post by trvr »

For years now I have published DNS TXT records for my domain that include my twitter handle, email address, and a Google Voice number. I always thought it would be a fun "protocol" for people to adopt, but never knew how to advance it.

  dig TXT trevormanternach.com

Re: DNS Toys

#75

Post by lillecarl »

SahAssar wrote: post #18
QuadrupleA wrote: post #16

Earlier quoted context omitted.

Simplicity / 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 Anyway if you're using a 14.4 modem in a rusty bunker at the bot…

> 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.

Re: DNS Toys

#76

Post by BMc2020 »

Copy and run the below commands to try it out.

I can't make it work from the explorer bar, powershell prompt, dos shell.

Bye.

Re: DNS Toys

#77

Post by stjohnswarts »

BMc2020 wrote: post #76

Copy and run the below commands to try it out. I can't make it work from the explorer bar, powershell prompt, dos shell. Bye.

dig is a unix utility, you'll have to download a windows version somewhere if you want to try it. He should have warned people I guess. Also I think currently it got the HN hug of death as it doesn't work in linux either :)

Re: DNS Toys

#78

Post by 1vuio0pswjnm7 »

Remember the bert.secret-wg.org RPN calculator via DNS from the old days. It's still going.

Recursive

   DNSCACHEIP=185.49.141.200 dnstxt 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org 
   dq txt 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org 
   drill 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org txt
   kdig 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org txt
   dig 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org txt
Non-recursive

   dnsq txt 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org 185.49.141.200  
   dq -a txt 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org 185.49.141.200
   drill -ord 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org @185.49.141.200 txt 
   kdig +nord 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org @185.49.141.200 txt
   dig +nord 4.9.+.3.+.7.+.7.+.7.+.5.+.rp.secret-wg.org @185.49.141.200 txt
Two different TXT RRs will be returned. The second one is new as of last year.

Read more at https://bert.secret-wg.org/Tools/index.html

Re: DNS Toys

#79

Post by hug »

lazide wrote: post #36
QuadrupleA wrote: post #16

Earlier quoted context omitted.

Simplicity / 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 Anyway if you're using a 14.4 modem in a rusty bunker at the bot…

A 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.

I used to use iodine, a tunneling server which uses DNS as the transport, which would work even through captive portals at the time.

https://github.com/yarrick/iodine

Re: DNS Toys

#80

Post by mike_d »

trvr wrote: post #74

For years now I have published DNS TXT records for my domain that include my twitter handle, email address, and a Google Voice number. I always thought it would be a fun "protocol" for people to adopt, but never knew how to advance it. dig TXT trevormanternach.com

That was the intention behind the .tel TLD: https://en.wikipedia.org/wiki/.tel
Post reply on HN