Since doing a full upgrade today (which a do about once a week or more), upon starting BIND (systemctl start/restart named), it seems to immediately crash after Postfix does any sort of DNS resolution to it (with 127.0.0.1 in resolv.conf).
I could ping hostnames (like "google.com" or something random like "sadffssafsfasdfa.com") without it crashing.
Downgrading to the latest package I had in the cache, "bind-9.9.5.W1-2-x86_64", fixed it.
Here are the relevant log lines from doing "journalctl -l -u named -u postfix --since=today". There didn't seem to be anything logged at the same times for the rest of my mail stack (dovecot, spampd, clamd).
Any ideas? Broken BIND? Broken something else, maybe?
I'm running on OpenVZ (kernel version 2.6.32-042stab088.4).
Last edited by Mister_Magotchi (2014-05-29 15:43:27)
I upgraded to 3.10.39-2-lts this morning and named service crashes on start up
sudo chmod a+r /srv/named/etc/rndc.key
seems to have fixed the problem for me.
Last edited by laertiades (2014-05-13 15:37:54)
"Conversation enriches the understanding, but solitude is the school of genius"
I installed bind 9.10.0.P1-4 today, and it doesn't have the same problem.