Re: Why does dig +trace ignore Additional Records?

Hello list, I am also interested in understanding the reasons behind this behaviour, especially after reading the following snippet from the official knowledge base [1]: When following delegation iteratively as specified with the +trace option, dig will begin by requesting the NS records

receive_secure_serial: unchanged (why?)

While sorting this latest DNSSEC problem, autosign not autosigning, this older *cosmetic* problem would be nice to have fixed too... Windows Event Viewer filling with these error messages, which I guess are not actual errors, should be more like warnings or notifications. When the named

VL: DNSSEC zones not updated

Yes, that worked. Also had to delete the .jnl, to prevent the "not exact" error.. Jukka -Alkuperäinen viesti- Lähettäjä: Mark Andrews Lähetetty: 23. tammikuuta 2020 0:53 Vastaanottaja: Jukka Pakkanen Kopio: bind-us...@isc.org; Browne, Stuart Aihe: Re: DNSSEC zones not updated On

RE: NSEC3 salt change - temporary performance decline

Thank you all for the answers. We do not use ixfr-from-differences on the actual zone, but on several others on the same server. Not sure how a BIND handles that scenario. I will try to solve the problem by changing the max-journal-size. According to the docs https://kb.isc.org/docs/aa-01641