Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The query API is quite limited: No Msg ID and only one EDNS0 option supported (ECS). For example, the EDNS chain query draft is now approved and future support for this would be nice. 

  • For DNSSEC the only option is to trust Google to do the validation, this API does not support validating stubs obtaining DNSSEC records.

  • Also interesting to note that when DNSSEC validation fails, the error comment includes a link to the DNSviz tool to try to figure out the failure!
  • They don't use the 8.8.8.8 IP address directly for the queries, instead they use dns.google.com on 216which resolved to 216.58.208.142 and 2a00:1450:4009:803::200e from the Buenos Aires Hackathon. It is likely this is served by the Google web service cloud which ultimately uses 8.8.8.8 as a back end for the resolution.
  • When a query is made via the web interface provided at https://dns.google.com it seems that QUIC over IPv6 is always used
  • We also notice that the server will answer do DNS-over-HTTP on port 80.