Re: [Pdns-users] pdns-recursor suddenly started to answer with content from . zone instead of what is configured in forward.zones.

2021-09-21 Thread Thomas Mieslinger via Pdns-users
Hi Peter, Am 21.09.21 um 18:20 schrieb Peter van Dijk via Pdns-users: Hello Thomas, On Tue, 2021-09-21 at 13:53 +0200, Thomas Mieslinger via Pdns-users wrote: dog.80 IN NSEC domains. NS DS RRSIG NSEC This looks like aggressive NSEC reuse ( https://datatracker.ietf.org/doc

Re: [Pdns-users] pdns-recursor suddenly started to answer with content from . zone instead of what is configured in forward.zones.

2021-09-21 Thread Otto Moerbeek via Pdns-users
On Tue, Sep 21, 2021 at 06:20:16PM +0200, Peter van Dijk via Pdns-users wrote: > Hello Thomas, > > On Tue, 2021-09-21 at 13:53 +0200, Thomas Mieslinger via Pdns-users > wrote: > > dog.80 IN NSEC domains. NS DS RRSIG NSEC > > This looks like aggressive NSEC reuse ( > https://d

Re: [Pdns-users] pdns-recursor suddenly started to answer with content from . zone instead of what is configured in forward.zones.

2021-09-21 Thread Peter van Dijk via Pdns-users
Hello Thomas, On Tue, 2021-09-21 at 13:53 +0200, Thomas Mieslinger via Pdns-users wrote: > dog.80 IN NSEC domains. NS DS RRSIG NSEC This looks like aggressive NSEC reuse ( https://datatracker.ietf.org/doc/html/rfc8198) and/or NXDOMAIN: There Really Is Nothing Underneath ( http

[Pdns-users] pdns-recursor suddenly started to answer with content from . zone instead of what is configured in forward.zones.

2021-09-21 Thread Thomas Mieslinger via Pdns-users
Hi, we're experiencing the problem that pdns_recursor (4.3.5 and 4.5.1) answers with the information from the . zone instead of what we have configured in forward.zone. Some configuration details (please name the setting you additionally need to diagnose the problem further) forward.zones: ...