Saucepan

User Tools

Site Tools

Trace: • extend_server_licence • about • doh_dot • migration • ntp • user-id • ssh • ecs • adp • dns
dns:dot_doh

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
dns:dot_doh [2025/02/14 09:31] – [Cloudflare DoH] bstafforddns:dot_doh [2025/07/28 20:58] (current) – [Quad9 DoH] bstafford
Line 44: Line 44:
 <code>curl -H "accept: application/dns-json" "https://cloudflare-dns.com/dns-query?name=www.google.com&type=A"</code> <code>curl -H "accept: application/dns-json" "https://cloudflare-dns.com/dns-query?name=www.google.com&type=A"</code>
 Response is the same as for Google (above) but doesn't have the extra . at the end of the domains. Response is the same as for Google (above) but doesn't have the extra . at the end of the domains.
 +
 +===== Quad9 DoH =====
 +<code>curl -H "accept: application/dns-json" "https://dns.quad9.net/dns-query?name=www.google.com&type=A"</code>
 ===== Infoblox B1TD DoH ===== ===== Infoblox B1TD DoH =====
 Following RFC, the endpoint should receive a base64 encoded HTTP friendly DNS packed. Following RFC, the endpoint should receive a base64 encoded HTTP friendly DNS packed.
dns/dot_doh.1739525515.txt.gz · Last modified: by bstafford