There are still regular clients that make ANY queries today.  We had a bug 
report about the handling a misconfigured load balance that returned NODATA to 
ANY and then
the follow up A query within the same second we returned NODATA when the server 
returns a CNAME.   That bug report is less than a month old.

Personally I’d like to be able to us ANY when looking for updated CDS and 
CDNSKEY to ensure you get everything from the same zone instance.  Additionally 
to have the matching NSEC3 included in the authority section so that clients 
can make decisions about whether to make a follow up query or not.  The tool 
makes multiple queries over TCP so it’s at least talking to the same instance 
of an anycast server. 
-- 
Mark Andrews

> On 12 Nov 2026, at 07:27, Ralf Weber <[email protected]> wrote:
> 
> Moin!
> 
>> 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.
> 
> But that is not the only reason. Anyone ;-) looking at DNS data will tell you 
> that the only use of ANY in todays internet is for attack amplification 
> traffic. There simply is no more legitimate ANY traffic.
> 
> […]
> 
>> 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.
> 
> 
>> 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.
>> Maybe it would be better to issue separate guidance for stub resolvers,
>> full-service resolvers, authoritative servers, etc., especially if a
>> phased approach is used.
> 
> I agree, but it’s a 00 that we as a working group surely can make better.
> 
> So long
> -Ralf
> ———
> Ralf Weber
> _______________________________________________
> DNSOP mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

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

Reply via email to