Good morning,
i just upgraded to 6.12 on debian 10, as i am notified in virtualmin upgrade of bind to 9.11.5 i have any of you had problems after bind upgrade? can i update without problems? thank you
Hi,
I installed mentioned BIND 9.11.5 update, to run tests for you on my Debian 10 instance.
After installation, I couldn’t restart the process properly:
~# systemctl restart bind9
Job for bind9.service failed because the control process exited with error code.
See "systemctl status bind9.service" and "journalctl -xe" for details.
~# journalctl -xe
Aug 28 16:59:58 host named[3621]: listening on IPv6 interfaces, port 53
Aug 28 16:59:58 host named[3621]: binding TCP socket: address in use
Aug 28 16:59:58 host named[3621]: listening on IPv4 interface lo, 127.0.0.1#53
Aug 28 16:59:58 host named[3621]: binding TCP socket: address in use
Aug 28 16:59:58 host named[3621]: listening on IPv4 interface enp1s0, 192.168.122.8#53
Aug 28 16:59:58 host named[3621]: binding TCP socket: address in use
Aug 28 16:59:58 host named[3621]: listening on IPv4 interface enp1s0:0, 192.168.122.9#53
Aug 28 16:59:58 host named[3621]: binding TCP socket: address in use
Aug 28 16:59:58 host named[3621]: unable to listen on any configured interfaces
Aug 28 16:59:58 host named[3621]: loading configuration: failure
Aug 28 16:59:58 host named[3621]: exiting (due to fatal error)
I had to run first:
pkill -9 named
… and then it worked as expected:
~# systemctl restart bind9
~# systemctl status bind9
● bind9.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-08-28 17:04:10 MSK; 13s ago
Docs: man:named(8)
Process: 4363 ExecStart=/usr/sbin/named $OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 4364 (named)
Tasks: 19 (limit: 1144)
Memory: 39.4M
CGroup: /system.slice/bind9.service
└─4364 /usr/sbin/named -u bind
~# named -v
BIND 9.11.5-P4-5.1+deb10u2-Debian (Extended Support Version) <id:998753c>
Perfect, great help, so do I install it?
I assume, it should work. 
Besides, it looks as a security fix, thus must be installed, as soon as possible.
after installation if I restart bind from virtualmin it gives me this error
● bind9.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-08-28 16:52:46 CEST; 24s Aug
Docs: man: named (8)
Process: 11736 ExecStart = / usr / sbin / named $ OPTIONS (code = exited, status = 0 / SUCCESS)
Process: 11833 ExecStop = / usr / sbin / rndc stop (code = exited, status = 1 / FAILURE)
Main PID: 11737 (code = exited, status = 0 / SUCCESS)
Aug 28 16:52:46 srv12486 named [11737]: no longer listening on 127.0.0.1 # 53
Aug 28 16:52:46 srv12486 named [11737]: no longer listening on 81.x.x.x # 53
Aug 28 16:52:46 srv12486 named [11737]: no longer listening on 81.x.x.x # 53
Aug 28 16:52:46 srv12486 named [11737]: no longer listening on 81.x.x.x # 53
Aug 28 16:52:46 srv12486 named [11737]: no longer listening on 81.x.x.x # 53
Aug 28 16:52:46 srv12486 named [11737]: no longer listening on 81.x.x.x # 53
Aug 28 16:52:46 srv12486 named [11737]: exiting
Aug 28 16:52:46 srv12486 rndc [11833]: rndc: connect failed: 127.0.0.1 # 953: connection refused
Aug 28 16:52:46 srv12486 systemd [1]: bind9.service: Control process exited, code = exited, status = 1 / FAILURE
Aug 28 16:52:46 srv12486 systemd [1]: bind9.service: Failed with result ‘exit-code’.
then after i do as you advised me pkil -9 named and reboot from console everything is fine
Try:
pkill -9 named
… and then
systemctl restart bind9
… I thought, I mentioned it on the initial post.
certainly already done but I noticed that it is not convenient to restart bind from virtualmin you can only do it from the terminal otherwise it gives the same error that is solved as you indicated. Thanks, it’s very kind of you
Oh, great report - it’s true. I will discuss with @Jamie what would be the better way to stop it. Meanwhile, you can go to Bind Configuration page and set Command to stop BIND under System configuration to:
service bind9 stop
Example:
nothing I always have to send the commands pkill -9 named and restart bind in terminal to restart bind does not work from virtualmin even with the changes you recommended
Changes I recommended affect stopping BIND, I assume you refer to command to apply BIND config? What is it set by default for you?
the problem is when restart bind as marked by the arrow from the image it seems that it restarts but if I type in the terminal systemctl status bind9 it gives me the errors that I have already posted. To make it restart then I have to do from the terminal pkill -9 named and systemctl restart and everything is fine.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.