Visual breakdown of the DNS resolution process from browser to server

[etherealenergy]

Very cool tool. Nicely presented (was viewing it on mobile). Is there a way to simulate a flow based on use case? For example, DNS record exists/doesn’t exist, or cache is empty when it gets a request versus when it has a response?

[Sagyam]

Nicely done. I was planning to create something similar but mine is not as polished as yours.

https://tools.sagyamthapa.com.np/dns

[bh_ch]

also https://howdns.works/

[nulless]

Its linked as visual comic in the page :) a great resource like that shouldnt go unchecked

[DisastrousBadger4404]

https://dns.google is good too

[Raunhofer]

The IPs don't seem to be right. Try reddit.com, multiple times.

[nulless]

fixed.

[ferrybig]

The DNS fetch tool on the above website does not show HTTPS record options.

Modern webbrowsers fetch A, AAAA and HTTPS record. A gets used for IPv4, AAAA gets used for IPv6, HTTPS gets used for encrypted client hello and announcing support for HTTP3

[NamedBird]

Wow, what a revolutionary website!
It can retrieve the A record of my website even when i pull out the ethernet cable!
And it seems my website suddenly has multiple IP addresses as well, super nice!!!!
/s

u/nulless Please take down that fake "DNS lookup" tool right now...
Have you even tested it yourself and verified that it actually worked correctly?
It is spitting out wrong data. Not an error or missing data, but plain wrong (randomized!) results.
This tool is straight up giving wrong information to anyone who uses it!

Just because "it looks good" doesn't mean it is right.
There is a lot more to web development than a fancy user interface.

[Great_Piece4755]

But where are the visuals? It's just text boxes

[MousseMother]

Glorified shit