41–50 of 71 posts
NextDNS gives you a name that you can put in certain UIs (like "Private DNS" in Android) -- I always assumed there was just something special about those.
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.
The DNS protocol is just text over udp. When making a DNS request, your system will open a socket, write "google.com" in it and read for a response. The server, if it is properly configured as a DNS server, will reply with the appropriate DNS record, again as text. Google.com is a cname to some subdomain used for load balancing, so the server will simply reply "CNAME blabla.google.com" and may optionally also resolve…
Your description of how queries work is not how queries work at all. Your entire comment is a net negative and detracts from the overall knowledge at Hacker News.
This reminds me of a neat little trick I used back then to "reliably" compute IP address of my machines for a dynamic DNS utility I wrote for myself. OpenDNS resolvers (such as resolver1.opendns.com) will resolve myip.opendns.com to your actual IP address. Whether you get A or AAAA records depends on your connection. Since the IP addresses for these resolvers tend to be anycast IPs, I also want to believe they are ma…
Very nice idea. Seems way simpler than the STUN protocol.
I'm a big fan of Julia Evans[1] who's made a number of useful toys including ones for DNS here[2] and here[3]. - [1] https://jvns.ca/ - [2] https://dns-lookup.jvns.ca/ - [3] https://messwithdns.net/
I'm surprised that they aren't also available in some subdomain of dns.toys (so that they would resolve without using a special name server).
If you used default nameservers, you'd be introducing all the usual DNS complications, e.g. caching.
This reminds me of a neat little trick I used back then to "reliably" compute IP address of my machines for a dynamic DNS utility I wrote for myself. OpenDNS resolvers (such as resolver1.opendns.com) will resolve myip.opendns.com to your actual IP address. Whether you get A or AAAA records depends on your connection. Since the IP addresses for these resolvers tend to be anycast IPs, I also want to believe they are ma…
Google and akamai also has a DNS service. dig @ns1-1.akamaitech.net ANY whoami.akamai.net +short dig @ns1.google.com TXT o-o.myaddr.l.google.com +short
nslookup whoami.akamai.net ns1-1.akamaitech.netCan 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.
The DNS protocol is just text over udp. When making a DNS request, your system will open a socket, write "google.com" in it and read for a response. The server, if it is properly configured as a DNS server, will reply with the appropriate DNS record, again as text. Google.com is a cname to some subdomain used for load balancing, so the server will simply reply "CNAME blabla.google.com" and may optionally also resolve…
Earlier quoted context omitted.
The DNS protocol is just text over udp. When making a DNS request, your system will open a socket, write "google.com" in it and read for a response. The server, if it is properly configured as a DNS server, will reply with the appropriate DNS record, again as text. Google.com is a cname to some subdomain used for load balancing, so the server will simply reply "CNAME blabla.google.com" and may optionally also resolve…
Your reply is riddled with errors and you don't seem to actually know how the DNS protocol works at all, on the wire or otherwise. It is, firstly, impossible for "google.com" to contain a CNAME record. This would violate standards, and it's simply not done. Query or yourself; there is no CNAME at that label. Your description of how queries work is not how queries work at all. Your entire comment is a net negative and…
It is possible for an apex domain to contain/be a CNAME, and it simply is done, by many companies: https://serverfault.com/questions/55528/set-root-domain-reco...
Nice, but why over DNS? Perhaps I simply didn't get the point.
The README for this project may explain some of the general benefits (my project): https://github.com/m3047/rkvdns
HTTP is everywhere. I think SOAP sucks, but it's everywhere and it works well enough. (For that matter XHR sucks, but even I use it occasionally.)
(This is not the first time DNS Toys has shown up on Hacker News, there's a link in another comment.)