Re: [bind-9.18.26] named crash with assertion failure

Start with upgrading to the latest 9.18. You are 8 versions behind, and yes, bugs get fixed. Ondrej -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 27. 2. 2025, at 23:12, avije

[bind-9.18.26] named crash with assertion failure

Hi All, I have bind9 version 9.18.26 deployed on a dns server running on the AWS ECS cluster. I noticed "named" crashed with assertion failure. It has happened a few times now. >From the coredump, it appears named crashied when it is trying to respond to a query. I was sending a dig query with +d

Re: XoT Testing: TLS peer certificate verification failed

When validating a certificate, be sure to use the context of the DNS service... So, if your service runs under user BIND, you may need to su to BIND to test. This may help flush out issues where the ca.crt file was set so BIND could not read it. I don't know what happens when you set TLS to str

XoT Testing: TLS peer certificate verification failed

Hi! I want to test XoT between Bind9.20.6 primary and secondary. On the primary I created a self-signed certificate with CN=xot-test-primary.ops.nic.at and configured bind: # Create a 10years valid self-signed certificate: # openssl genpkey -algorithm RSA -out private.key -pkeyopt rsa_keygen_