Re: Named keeps dying on me

On 12/15/22 16:26, Sam Varshavchik wrote: ToddAndMargo via users writes: # cat /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search . Ummm. This is not bind. This is, most likely, systemd-resolved. The problem happens whenever a network configuration event occurs, such and

Re: Named keeps dying on me

ToddAndMargo via users writes: # cat /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search . Ummm. This is not bind. This is, most likely, systemd-resolved. pgpjBPesEYtnH.pgp Description: PGP signature ___ users mailing list -- u

Re: Named keeps dying on me

On Thu, 15 Dec 2022 14:21:34 -0800 ToddAndMargo via users wrote: > Your in frustration, Has resolv.conf changed? Sometimes DHCP comes along on lease renewal and rewrites sutff. Somewhere there is a NetworkManager option to make it leave resolv.conf alone (always takes me an hour to find it though

Re: Named keeps dying on me

On 12/15/22 14:21, ToddAndMargo via users wrote: Hi All. FC37 bind-chroot-9.18.8-1.fc37.x86_64 I have a caching server configured. This is becoming a real pain in the ... Named can not be connected to after about five minutes. As of FC37 (no issue in FC36) # cat /etc/resolv.conf nameserve

Named keeps dying on me

Hi All. FC37 bind-chroot-9.18.8-1.fc37.x86_64 I have a caching server configured. This is becoming a real pain in the ... Named can not be connected to after about five minutes. As of FC37 (no issue in FC36) # cat /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search . And