On 11 Nov 2026, at 21:26, Ralf Weber <[email protected]> wrote:

> On 11 Nov 2026, at 12:31, Robert Edmonds wrote:
>> I read the draft and the slides from Ralf's presentation [0] but I don't
>> see a clear rationale for why an RCODE=4 (NOTIMP) response would be
>> preferable to, say, an RFC 8482 §4.2 (HINFO) response. The closest seems
>> to be the anecdote in the slide deck that speculates that a broken RFC
>> 8482 implementation might have been responsible for events where broken
>> responses were observed from root nameservers?
> 
> Yes I am talking about recursive resolver who can not easily make up an HINFO 
> response. And yes there were incidents where root name servers answered 
> without glue when asked with qtype ANY. If recursive resolvers answers NOTIMP 
> and hence no longer forward a query to any server with qtype ANY these 
> behaviours can no longer happen.

FWIW

[manta:~] $ dig @1.1.1.1 example.com any

; <<>> DiG 9.20.30 <<>> @1.1.1.1 example.com any
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOTIMP, id: 41951
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 21 (Not Supported)
;; QUESTION SECTION:
;example.com. IN ANY

;; Query time: 12 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (TCP)
;; WHEN: Wed Nov 11 21:44:23 CET 2026
;; MSG SIZE  rcvd: 46

[manta:~] $ 


>> Similarly, are there issues with recursive resolvers returning RCODE=4
>> to stub clients, like causing the stub clients to retry the query
>> against the other resolver addresses configured into the stub resolver?
> 
> Maybe, but that then means that another resolver will act as amplification 
> vector and not mine. I don’t think there are any reasons left for stub 
> clients to send ANY.

I haven't heard of clients of 1.1.1.1 having problems, but I agree it's hard to 
tell whether that's because the choice of RCODE is safe or if nobody is 
expecting QTYPE=ANY to do anything useful any more. Certainly if your use-case 
is dig driven by humans, the response is not difficult to understand.

>> Side note, in the draft I found the use of the unqualified terms "DNS
>> client" and "DNS server" a little unclear. Recursive resolvers function
>> as clients when sending queries to nameservers and as servers when
>> sending responses to stub resolvers, so it seems that both the "DNS
>> client" and "DNS server" guidance applies to recursive resolvers.

Yeah. I agree there is scope to make this clearer.


Joe


_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to