4 ms·

Nice page, but a strange product. Why would anyone pay for an API that performs DNS queries instead of just performing a DNS query?

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 ago
  I don’t see why it’s simpler, though there’s an argument to be made for HTTP being more familiar.
- oaiey 5y ago
  Well... are you / competitors just proxying or is there DoH elements sparkled in? ps: lovely graphics
  - pul 5y ago
    It's just a glorified Dig wrapper ;)
- donavanm 5y ago
  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.
- 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.
vbezhenar 5y ago
You can't make DNS query from browser JavaScript AFAIK.
- Mup_TIpekpaceH 5y ago
  ahha
- cookiengineer 5y ago
  > You can't make DNS query from browser JavaScript AFAIK. Yes, you can. [1] Lots of public DNS resolvers have support for it, too. [2] Example: fetch('https://cloudflare-dns.com/dns-query?name=example.com&type=AAAA https://cloudflare-dns.com/dns-query?name=example.com&type=A...', { method: 'GET', headers: new Headers({ 'accept': 'application/dns-json' })}); 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. [1] https://developers.google.com/speed/public-dns/docs/doh/json https://developers.google.com/speed/public-dns/docs/doh/json [2] https://developers.cloudflare.com/1.1.1.1/encrypted-dns/dns-over-https/make-api-requests/dns-json https://developers.cloudflare.com/1.1.1.1/encrypted-dns/dns-... [3] https://www.rfc-editor.org/rfc/rfc8427 https://www.rfc-editor.org/rfc/rfc8427 [4] https://datatracker.ietf.org/doc/html/rfc8484 https://datatracker.ietf.org/doc/html/rfc8484
  - capableweb 5y ago
    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).
    - kube-system 5y ago
      Some might argue that DoH is proper DNS. Port 53 DNS sucks.
      - LinuxBender 5y ago
        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.
brightball 5y ago
Maybe rate limiting?
haroldp 5y ago
I run an install of RRDA[1] because it's easier to use http/json in scripts than parsing raw DNS queries. [1] https://github.com/fcambus/rrda https://github.com/fcambus/rrda

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 ago
I don’t see why it’s simpler, though there’s an argument to be made for HTTP being more familiar.
oaiey 5y ago
Well... are you / competitors just proxying or is there DoH elements sparkled in? ps: lovely graphics
- pul 5y ago
  It's just a glorified Dig wrapper ;)
donavanm 5y ago
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.
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.

vbezhenar 5y ago

You can't make DNS query from browser JavaScript AFAIK.

Mup_TIpekpaceH 5y ago
ahha
cookiengineer 5y ago
> You can't make DNS query from browser JavaScript AFAIK. Yes, you can. [1] Lots of public DNS resolvers have support for it, too. [2] Example: fetch('https://cloudflare-dns.com/dns-query?name=example.com&type=AAAA https://cloudflare-dns.com/dns-query?name=example.com&type=A...', { method: 'GET', headers: new Headers({ 'accept': 'application/dns-json' })}); 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. [1] https://developers.google.com/speed/public-dns/docs/doh/json https://developers.google.com/speed/public-dns/docs/doh/json [2] https://developers.cloudflare.com/1.1.1.1/encrypted-dns/dns-over-https/make-api-requests/dns-json https://developers.cloudflare.com/1.1.1.1/encrypted-dns/dns-... [3] https://www.rfc-editor.org/rfc/rfc8427 https://www.rfc-editor.org/rfc/rfc8427 [4] https://datatracker.ietf.org/doc/html/rfc8484 https://datatracker.ietf.org/doc/html/rfc8484
- capableweb 5y ago
  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).
  - kube-system 5y ago
    Some might argue that DoH is proper DNS. Port 53 DNS sucks.
    - LinuxBender 5y ago
      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.

brightball 5y ago

Maybe rate limiting?

haroldp 5y ago

I run an install of RRDA[1] because it's easier to use http/json in scripts than parsing raw DNS queries. [1] https://github.com/fcambus/rrda https://github.com/fcambus/rrda