Signed zone does not get updated 'receive_secure_serial: not exact'

Hi, I'm having the problem that after rolling a dynamic update on one of the zones - a newly signed zone - the signed zone does not get updated, but mocks about the serial being 'not exact'. Dec 26 07:39:26 spectre named[23831]: client 188.138.3.243#16192/key tlx.leuxner.net: signer

Re: Signed zone does not get updated 'receive_secure_serial: not exact'

Am 26.12.2012 um 23:31 schrieb Mark Andrews ma...@isc.org: What it is complaining about is that when the change you just applied to the unsigned version of the zone is applied to the signed version it found one of: * the record to be removed was not there * the record to be aded was

Re: Signed zone does not get updated 'receive_secure_serial: not exact'

Am 26.12.2012 um 23:31 schrieb Mark Andrews ma...@isc.org: * the record to be removed was not there * the record to be aded was already there This means that the two versions of the zone have become unsyncronized. I did some more tests with another zone. Not sure BIND works as intended

dns_journal_write_transaction on managed-keys-zone

After introducing views in my BIND 9.9.2-rpz+rl.028.23-P1 configuration the log starts to report managed keys errors periodically. Deleting the files does not solve the issue. view internal { match-clients { internal_hosts; }; recursion yes; include

Re: [SOLVED] dns_journal_write_transaction on managed-keys-zone

* Thomas Leuxner t...@leuxner.net 2013.02.11 21:13: * Evan Hunt e...@isc.org 2013.02.11 20:30: I haven't seen this problem before. Can you share the rest of your configuration with me? You can open a ticket by mailing bind9-b...@isc.org. Config sent. Regards Thomas Finally

Re: Unable to slave root zones

* Mark Knight 2017.04.07 16:36: > masters { > 192.5.5.241;// F.ROOT-SERVERS.NET. > }; Hi Mark, I had the same issue basically. Tracing the zone transfers with dig it turned out they worked for IPv6, but no longer work for IPv4. So I ended