Re: [DNSOP] Resolver behaviour in the presence of unrequested answer records

2024-01-18 Thread Petr Špaček
On 11. 01. 24 18:34, Bellebaum, Thomas wrote: Hello, We have been looking at some DNS resolvers and encountered a question: When a DNS response contains (in the answer section) records which were not requested, how should the resolver react to those and what should it return to the requesting c

Re: [DNSOP] Dnsdir early review of draft-ietf-dnsop-qdcount-is-one-01

2024-01-18 Thread Petr Špaček
On 17. 01. 24 21:42, Matt Brown via Datatracker wrote: The proposal has been discussed in the dnsop group and previous meetings and my observation of the discussion is that there is both broad agreement that QDCOUNT > 1 is not used in practice and at least some supporting evidence presented that

Re: [DNSOP] Dnsdir early review of draft-ietf-dnsop-qdcount-is-one-01

2024-01-18 Thread Joe Abley
On 18 Jan 2024, at 13:42, Petr Špaček wrote: > The only piece missing to make it *perfect* is "MUST use QDCOUNT=1", or in > other words, banning QDCOUNT=0 usage with DNS COOKIES. It's unnecessary > complexity. I think these are two different suggestions: (1) Update the cookies spec to require

Re: [DNSOP] Resolver behaviour in the presence of unrequested answer records

2024-01-18 Thread Eric Orth
As a what-one-stub-resolver-does data point... The resolver I'm most familiar with validates that all the CNAME records form a single chain from the query name, and that all answer records of the query type match the final name at the end of the CNAME chain. If that is not true, as in the case of

Re: [DNSOP] Dnsdir early review of draft-ietf-dnsop-qdcount-is-one-01

2024-01-18 Thread Mark Andrews
Really, cancel culture. It’s a couple of lines of code in a nameserver to support QCOUNT=0. It will take more time debating this than it took to implement support for QCOUNT=0. > On 19 Jan 2024, at 00:22, Joe Abley wrote: > > On 18 Jan 2024, at 13:42, Petr Špaček wrote: > >> The only piece