We use adapters in addns.xml to receive the unsigned zones via zone transfers. This worked well. An update of the zone on the source server was received and processed by opendnssec in a few seconds. Recently I installed ods 1.4.5. I now have the impression that a notify from the source system is not received by opendnssec any more. In the logs of the source system, I see that a notify is sent, but opendnssec does not read the new zone with a zone transfer. I have two questions:

1) In the log files notify messages are not mentioned at all. The logging verbosity in config.xml is set to 3. Is there a verbosity that will show logging of incoming notify messages for further diagnostics?

2) Is there a way to force opendnssec to read the new zone with a zone transfer?


BTW, in the log files I see for many zones messages like :
May 15 09:58:09 dns ods-signerd: [axfr] axfr fallback zone erdg.usor.nl
May 15 09:58:09 dns ods-signerd: [axfr] zone erdg.usor.nl journal not found for serial 2014051501
May 15 09:58:09 dns ods-signerd: [axfr] axfr fallback zone erdg.usor.nl
In an attempt to force a zone transfer, I restarted both the enforcer and the signer daemons. For some zones I see in the log file messages like: May 15 12:11:48 dns ods-signerd: [backup] bad ixfr journal: trailing RRs after final SOA May 15 12:11:51 dns ods-signerd: [zone] corrupted journal file zone erdg.usor.nl, skipping (General error)

Is this normal? If not, should I do something to fix it, or is it fixed automatically? (Note, this i not the zone that has a problem with the notify, but I mention it, because it could indicate a more general problem.)


_______________________________________________
Opendnssec-user mailing list
Opendnssec-user@lists.opendnssec.org
https://lists.opendnssec.org/mailman/listinfo/opendnssec-user

Reply via email to