Hello,
I'm using BIND to run DNSBL and it has been working great for a while. But recently (and this coincides with upgrade to the most recent version of OpnSense), I find that BIND sometimes exits due to an error that I do not understand, and I'd have to manually restart it. I've pasted the BIND log below (in reverse chron order). Does anyone know why this is happening?
Is there a way to make BIND automatically restart upon exit? Or at least get a notice that it died?
Thanks!
09-May-2019 07:46:38.754 general: critical: exiting (due to assertion failure)
09-May-2019 07:46:38.754 general: critical: #7 0x0 in ??
09-May-2019 07:46:38.754 general: critical: #6 0x3479b784c36 in ??
09-May-2019 07:46:38.754 general: critical: #5 0x14c5f2204d in ??
09-May-2019 07:46:38.754 general: critical: #4 0x14c5e53ab1 in ??
09-May-2019 07:46:38.754 general: critical: #3 0x14c5e50bd0 in ??
09-May-2019 07:46:38.754 general: critical: #2 0x14c5e4a428 in ??
09-May-2019 07:46:38.754 general: critical: #1 0x14c5f021fa in ??
09-May-2019 07:46:38.754 general: critical: #0 0x14c5d192c0 in ??
09-May-2019 07:46:38.754 general: critical: resolver.c:4895: INSIST(dns_name_issubdomain(&fctx->name, &fctx->domain)) failed, back trace
09-May-2019 07:46:38.754 lame-servers: info: FORMERR resolving 'c-0.19-a7000081.80081.1770.f17.2fc8.210.0.ig6b68dgmvuczv4udl6dz2i2g5.avts.mcafee.com/A/IN': 127.0.0.1#53
09-May-2019 07:46:38.754 resolver: notice: DNS format error from 127.0.0.1#53 resolving c-0.19-a7000081.80081.1770.f17.2fc8.210.0.ig6b68dgmvuczv4udl6dz2i2g5.avts.mcafee.com/A for client 192.168.128.237#58153: non-improving referral
How often does this happen?
This never happened before when I was on 18.7.xx and I was running BIND to do DNSBL for many months. Then over the weekend I got around to upgrading to the current 19.1.7(?) and this has happened maybe 2 to 3 times? So maybe once every couple of days?
It's not super frequent, but because I run everything through DNSBL, the internet stops working when BIND dies.
I setup Monit last night to check on BIND and restart it whenever the process does not exist, but I can't tell if it's working correctly yet.
Bind was updated to latest 914 from 912, maybe there is a Bug in Bind itself.