Re: Ubuntu service file is missing Restart parameter

2023-02-05 Thread Blažej Krajňák
Thank you for clarification. I'm not sure, who maintains which package. I opened bug report https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/2006054 ne 5. 2. 2023 o 15:55 Ondřej Surý napísal(a): > > Those are maintained by Ubuntu, not ISC, so you need to contact them. > > Or you can use pack

Re: Ubuntu service file is missing Restart parameter

2023-02-05 Thread Ondřej Surý
Those are maintained by Ubuntu, not ISC, so you need to contact them. Or you can use packages provided by ISC: https://kb.isc.org/docs/isc-packages-for-bind-9 Ondrej -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be different. Please do not feel obligated to reply ou

Re: Ubuntu service file is missing Restart parameter

2023-02-05 Thread Blažej Krajňák
Hi Ondrej, sorry, I really thought it's clear enough, but as I just found, the problem presents in releases for Ubuntu 20.04, 18.04 and maybe older also. It's all about the content of /lib/systemd/system/named.service Release for Ubuntu Jammy 22.04 LTS (1:9.18.1-1ubuntu1.3) contains "Restart=on-

Re: Ubuntu service file is missing Restart parameter

2023-02-05 Thread Ondřej Surý
Hi, it might seem like we do practice black magic, but we really don’t. Thus we can’t really help if you don’t provide more details like the content of the file, the source of the package(s), and the version of the package(s). Ondrej -- Ondřej Surý — ISC (He/Him) My working hours and your work

Ubuntu service file is missing Restart parameter

2023-02-05 Thread Blažej Krajňák
Hi there, I just discovered that default Bind9 systemd service file for Ubuntu is missing "Restart" parameter. Is there any reason? Service file for Debian contains "Restart=on-failure" Thanks Blažej -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC

Re: Resolve some hosts thats are dnssec signed differently

2023-02-05 Thread Darren Ankney
Matthias, This is what I did to force my resolver bind instance to lookup my internal domain directly on my authoritative bind instance without asking any other servers (would have failed anyway as it is a fake domain "mylocal"): // on resolver (or caching name server) zone "mylocal" { type for