Re: qname minimization: me too :(

2024-06-21 Thread Stephane Bortzmeyer
On Fri, Jun 21, 2024 at 07:03:14AM +, 65;6800;1c Michael Batchelder wrote a message of 59 lines which said: > You'll need to fix these zones so that the response is NOERROR rather than > NXDOMAIN. Yes and, if you want the whole context, you can read RFC 8020

Re: Debian download source on ISC website

2024-06-21 Thread Ondřej Surý
The authoritative source is bind.debian.net that can be redirected. But the primary reason is that I already have the infrastructure ready and I also maintain BIND 9 packages directly in Debian, so the contents mirror what ends up in Debian. Ondrej -- Ondřej Surý — ISC (He/Him) My working hour

Re: Debian download source on ISC website

2024-06-21 Thread Dominic Preston
On Fri, 21 Jun 2024 at 15:13, Ondřej Surý wrote: > > The authoritative source is bind.debian.net that can be redirected. But the > primary reason is that I already have the infrastructure ready and I also > maintain BIND 9 packages directly in Debian, so the contents mirror what ends > up in De

Re: Debian download source on ISC website

2024-06-21 Thread Dominic Preston
On Wed, 19 Jun 2024 at 14:19, Ondřej Surý wrote: > > If by production-ready you mean it’s reasonably well-tested, we are using it > ourselves and it also matches what’s being uploaded to Debian directly then > yes. > > If you mean there will be no bugs and it will magically work until the end of

Re: qname minimization: me too :(

2024-06-21 Thread Peter
On Fri, Jun 21, 2024 at 07:03:14AM +, Michael Batchelder wrote: ! > Yes, sure. I grabbed three typical cases to analyze further, and ! > currently trying to understand the proceedings - unsuccessfully, up ! > to now. :( ! > ! > Case 1: ! > --- ! > Jun 19 17:42:12 conr named[24481]: lame-se

Re: qname minimization: me too :(

2024-06-21 Thread Michael Batchelder
> Yes, sure. I grabbed three typical cases to analyze further, and > currently trying to understand the proceedings - unsuccessfully, up > to now. :( > > Case 1: > --- > Jun 19 17:42:12 conr named[24481]: lame-servers: >info: success resolving '26.191.165.185.in-addr.arpa/PTR' >