Ruurtjan from nslookup.io here. No one is really using the API it yet. Some competitors seem to be doing well, so I guess there's a demand. Maybe because it's simpler to integrate over HTTP than over DNS in terms of network config for enterprises? Not sure.
I haven’t looked at your API but a subtly critical aspect of diagnostics or introspection is being able to query from multiple client locations/resolvers. It’s really important to be able to disambiguate the “view” different clients have of the same labels.
Alternatively, if you’re targeted at direct client use, you may want to allow them to control the edns options, like client subnet, themselves.
Note that this is the JSON-specific format [3]. DNS over HTTPS itself uses the DNS wireformat [4], so you would have to build a parser for that if you want to integrate it into a web app.
That's a HTTP request no matter what data is being returned. Fact still stands that there is no JS API in browsers to make proper DNS requests (without HTTP).
DoH in its current implementation is just a tunnel using https to reach someone elses centralized servers that are using port 53 DNS. The root servers do not yet support DoH/DoT and I would be pleasantly surprised if they ever did.
Most of us are on the other end of the DNS hierarchy, and send queries to recursive resolvers, not root servers. Root server operators are conservative and there's much less of privacy consideration when traffic is mixed with others at a resolver.
I always thought ALIAS records were an actual record type, but it seems like they are non-standard additions by all the registrars that support it. Interesting.
It'd be nice if there were a bit more info on the different types (I tried clicking one of interest) - even just a link to the relevant RFC (section) would be cool.
Also you have a typo in the list (correct in the graphic) - 's/SVR/SRV/'.
