Re: QNAME minimisation question

2025-06-02 Thread Petr Špaček
On 6/2/25 12:01, Nick Tait via bind-users wrote: I can reproduce the issue by clearing the BIND cache, and then running the following DIG command, to attempt a reverse DNS lookup of 45.90.5.195 On 6/2/25 12:54, Carlos Horowicz via bind-users wrote: The problem seems related to "No zone cut at

Re: QNAME minimisation question

2025-06-02 Thread Carlos Horowicz via bind-users
Hi The problem seems related to "No zone cut at 90.45.in-addr.arpa." , shouldn't trigger a SERVFAIL with qname-minimisation relaxed This is strange, because the intermediate response has a SOA , and NSEC seems enough to fail-over to qname-minimisation off .. it seems you're force to set the

QNAME minimisation question

2025-06-02 Thread Nick Tait via bind-users
Hi list. I've been investigating a failure that I noticed in my DNS logs. I know the issue is related to QNAME minimisation, but rather than just turning it off (to make the problem go away), I'm trying understand whether BIND is doing exactly what it is expected to do? I can reproduce the i