1. 17
    1. 2

      I like how the article started:

      This is great if you’re used to reading it and if you know which parts to ignore and which parts to pay attention to, but for many people this is too much information.

      Now, I thought it’s going to be a bit more in that perspective, but it looks more like a simplified version of, say, intodns.com or similar tools that already exist. They cleaned the information up, but what else can you do with it now?

      So it should either stay exactly the same: super simplified look into the DNS records, for info purposes for muggles - or it should add more features to be actually useful for something else.

      I do bet that the author had a lot of fun making the tool though :)

      1. 10

        hi, author here! I’m curious about what you were expecting – I’m considering adding more features (like maybe reverse DNS), but for me just looking up the value of a given record for a domain is all I want to do 90% of the time.

        1. 2

          I think choosing a name server would be useful.

          1. 2

            I’ve been thinking about that! Can you give an example of a different nameserver you’d like to use instead of (like do you want to query the authoritative namerserver for the domain? or do you want to just look at the results from a different public recursive dns server?)

            1. 2

              Maybe you want to make requests against your own ISP’s nameserver, whatever it is. Or make requests against the mullvad public non logging DNS server at an IP address I can’t remember off the top of my head. Or if you are setting up your own nameserver and want to test it.

            2. 2

              One DNS issue I’ve had to debug before is where there are several DNS servers and one of them is responding with the wrong value. So I look up the relevant NS records and then query each of them individually to see if there’s a mismatch.

              Another thing I’ve cared about in the past is split horizon DNS, where a particular server has one A record on the public internet and a different A record inside our LAN so it could be seen from both. (In retrospect, perhaps doing this with routing entries to make the external IP address with on our LAN would have been better?)

              It comes up rarely but “I’m testing our in house custom DNS server software before we deploy it” (yeah that sounds like a bad idea, doesn’t it? It was.) so obvs I wanna send queries to it instead of the live NS servers.

              The last common use I can think of was “dig +trace $name” to quickly get a view of the whole chain from TLD on down. Used to use this to diagnose issues where there were 3 oe more levels of domain servers.

            3. 2

              some people simply do not like to use google infrastructure, so at least having would be nice.

            4. 1

              I am mainly interested in and