3 ms·
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 s
by pul 5y ago
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.
- maltalex 5y agoI don’t see why it’s simpler, though there’s an argument to be made for HTTP being more familiar.
- oaiey 5y agoWell... are you / competitors just proxying or is there DoH elements sparkled in? ps: lovely graphics
- pul 5y agoIt's just a glorified Dig wrapper ;)
- donavanm 5y agoI 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.
- backoncemore 5y ago> Some competitors seem to be doing well, so I guess there's a demand. Sounds like a really thought out business plan.