Malformed transaction errors

Matus UHLAR - fantomas uhlar at fantomas.sk
Mon Oct 19 06:54:27 UTC 2020


On 18.10.20 11:00, @lbutlr wrote:
>I am getting the following error on one specific domain and I am unsure how to fi it. Searching for the error lead to suggestions about not running multiple copies of bind on the same machine, but that is not the case here (and it is only affecting one domain).
>
>named[652] malformed transaction: example.com.signed.jnl last serial 2018022385 != transaction first serial 2018022384
>named[652] zone example.com/IN: zone_resigninc:dns_journal_write_transaction -> unexpected error
>named[652] malformed transaction: example.com.signed.jnl last serial 2018022385 != transaction first serial 2018022384
>named[652] zone example.com/IN: zone_resigninc:dns_journal_write_transaction -> unexpected error
>
>If I put aside the jnl file and stop/start bind the error goes away, but eventually it comes back, always for the same domain.
>
>(Setup is DNS primary on on machine and a secondary server on a separate machine. Errors are on the primary server.)

what's the primary server? maybe broken DNS implementation

-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Remember half the people you know are below average.


More information about the bind-users mailing list