By Greg Nowak. Updated 17 November 2026.
A DNS request can succeed while the automation reading its answer makes the wrong decision. Cloudflare’s changes to its DNS-over-HTTPS (DoH) JSON responses expose that gap: valid JSON can contain a record representation your script no longer understands.
If you run an agency, manage operations or own a business with automated domain checks, start with the workflow behind the lookup. Client onboarding, certificate checks and provisioning deserve attention wherever a DNS answer can trigger a change or block a customer.
What changed in Cloudflare’s DoH JSON?
Cloudflare’s 28 July 2026 change notice announced breaking changes to the response’s data field:
- Generic hexadecimal encoding became DNS presentation text for CAA, NAPTR, RP, IPSECKEY, SVCB, HTTPS, TLSA, SSHFP and OPENPGPKEY records.
- DNSSEC algorithm identifiers became numeric for RRSIG, DS, CDS, DNSKEY and CDNSKEY records. DS digest identifiers also became numeric.
- HINFO values gained individual quoting around each character-string, preserving boundaries when values contain spaces.
The announcement warned that either representation could appear during rollout. That makes saved examples more useful than one successful live lookup when checking compatibility.
These changes concern how the resolver represents answers. They do not mean your domain’s records were edited. A and AAAA records are outside the listed groups, so an address-only checker does not automatically need this particular repair.
Find the scripts behind the business process
I would begin with a small inventory: which job makes the request, which record types it asks for, who owns it and what happens next. For agencies, include utilities copied into client environments. Updating the shared repository may leave scheduled copies running old code.
From a repository root, this search is a useful starting point:
rg -n -i 'cloudflare-dns\.com|one\.one\.one\.one|1\.1\.1\.1|application/dns-json|dns-query' .Follow matches into helper functions and deployment configuration. Ripgrep normally skips hidden and ignored files; inspect relevant CI files separately, along with scheduled jobs and monitoring outside the repository.
Look for awk, cut, regular expressions, split() and unconditional access to the first answer. Using jq or a JSON library handles the JSON layer. The extracted data value still needs interpretation according to its DNS record type.
Prioritise by what a wrong answer can do
A useful audit produces an ordered repair list with an owner and a clear failure response. Use the consequence of misinterpretation to decide what gets attention first.
| Consumer | Business consequence | First action |
|---|---|---|
| Provisioning or configuration job | A misunderstood answer could trigger an incorrect change | Stop changes on parsing errors; repair and test first |
| Onboarding or certificate readiness check | A customer could be blocked or marked ready incorrectly | Verify the decision against representative records |
| Monitoring and alerts | A broken parser could hide a problem or generate noise | Expose interpretation failures as a separate state |
| Report reviewed by a person | Incorrect information may reach a reviewer | Label unavailable results and schedule the repair |
Capture the response, then test the decision
Cloudflare’s JSON documentation specifies GET requests with an Accept: application/dns-json header. This diagnostic command saves the headers and response. Replace the domain and record type with ones your workflow actually uses:
curl --fail --silent --show-error --max-time 15 \
--header 'Accept: application/dns-json' \
--dump-header doh-headers.txt \
--output doh-response.json \
'https://cloudflare-dns.com/dns-query?name=example.com&type=CAA'The command’s success does not establish that a CAA record exists. Test three layers separately:
- HTTP delivery: Handle timeouts, unsuccessful status codes and unexpected content types.
- DNS outcome: Inspect the JSON
Statusfield. Distinguish a nonexistent name, a successful lookup without the requested records and a resolver failure. - Record interpretation: Check answer owners and types, handle aliases deliberately and validate the parsed values before using them.
This distinction is fundamental to DoH: RFC 8484 explicitly permits successful HTTP responses carrying DNS failures.
Save representative old and new responses as test fixtures, with expected interpreted values and downstream decisions. Include multiple answers, missing fields, quoting and unsupported formats. Equivalent records should produce equivalent decisions; unexpected input should produce an explicit error.
Should you keep JSON or move to DNS wire format?
A small diagnostic script can reasonably retain JSON with explicit record handling and useful errors. For a critical integration, Cloudflare recommends DNS wire format because the JSON interface has no formal RFC or guaranteed stable schema.
Use a maintained DNS library that supports DoH and exposes structured records. Keep those records structured through the workflow: converting them into display text and splitting that text recreates the same weakness.
There is a practical migration detail here. Cloudflare supports GET and POST for wire format, and GET for JSON. Wire format uses application/dns-message and encoded DNS messages. Changing a header or switching to POST alone will not migrate the integration.
Deploy the repair where the jobs actually run
Repair one representative consumer, then compare interpreted results before allowing a replacement to drive changes. Account for caching and query timing when investigating differences. For monitoring, compare the relevant record values rather than entire responses, where TTL or ordering differences can create noise.
Track transport failures, DNS failures and parsing errors separately. Confirm that every scheduled copy has been updated and that the fallback understands current responses. Rolling back your code cannot restore the provider’s former output.
If these dependencies are scattered across suppliers, scripts and client environments, I can help map the callers, agree repair priorities and coordinate deployment. Contact Greg with the workflow you rely on and, if available, a sample response and the code reading it.
Related on GrN.dk
- Your AI workflow has logs. Can they explain one bad decision?
- When AI writes JSON, one bad field can break the workflow
- When the AI API Says “Try Again,” What Does Your Customer See?
Need help with this kind of work?
Review your DNS automation with Greg Get in touch with Greg.