We have had this same problem on one of our servers. Version is BIND 9.16.1. It wasn't very common before, but we've had it happen 3 times this week. Here is the error from logs:
Dec 8 04:26:27 XXXXXXX kernel: [2824711.133384] isc-worker0007[710557]: segfault at 8 ip 00007f1c09ddb166 sp 00007f1bff192530 error 4 in libisc.so.1601.0.0[7f1c09db9000+46000]
Dec 8 04:26:27 XXXXXXX kernel: [2824711.133402] Code: 00 00 48 8d 3d ab b4 02 00 e8 66 39 fe ff 66 0f 1f 44 00 00 f3 0f 1e fa 41 57 41 56 41 55 41 54 55 53 48 83 ec 08 4c 8b 67 10 <41> 83 7c 24 08 02 0f 85 be 00 00 00 49 89 fd 49 8b 7c 24 10 48 89
To work around it for now we modified our systemd service to restart bind automatically with these changes:
Added to [Unit]:
StartLimitIntervalSec=500
StartLimitBurst=5
Added to [Service]:
Restart=on-failure
RestartSec=5s
We have had this same problem on one of our servers. Version is BIND 9.16.1. It wasn't very common before, but we've had it happen 3 times this week. Here is the error from logs:
Dec 8 04:26:27 XXXXXXX kernel: [2824711.133384] isc-worker0007[ 710557] : segfault at 8 ip 00007f1c09ddb166 sp 00007f1bff192530 error 4 in libisc. so.1601. 0.0[7f1c09db900 0+46000]
Dec 8 04:26:27 XXXXXXX kernel: [2824711.133402] Code: 00 00 48 8d 3d ab b4 02 00 e8 66 39 fe ff 66 0f 1f 44 00 00 f3 0f 1e fa 41 57 41 56 41 55 41 54 55 53 48 83 ec 08 4c 8b 67 10 <41> 83 7c 24 08 02 0f 85 be 00 00 00 49 89 fd 49 8b 7c 24 10 48 89
To work around it for now we modified our systemd service to restart bind automatically with these changes:
Added to [Unit]: valSec= 500
StartLimitInter
StartLimitBurst=5
Added to [Service]:
Restart=on-failure
RestartSec=5s