Re: FC34 broke my bind

# host google.com 127.0.0.1 Using domain server: Name: 127.0.0.1 Address: 127.0.0.1#53 Aliases: Host google.com not found: 2(SERVFAIL) [root@rn6 etc]# systemctl status named-chroot.service ● named-chroot.service - Berkeley In

Re: FC34 broke my bind

dnssec-validation yes; should work, ensure include "/etc/named.root.key"; is in named.conf too. dnssec-validation auto; would work even without it. It requires your forwarders to supply DNSSEC records. Check with: dig @$IP +dnssec com ds Or with validation: delv @$IP com ds Replace $IP with any

Re: FC34 broke my bind

On 6/13/21 1:40 AM, Ed Greshko wrote: try dig @localhost -x 8.8.8.8 Works, even without the work around I just posted ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora C

Re: FC34 broke my bind

On 6/13/21 1:29 AM, ToddAndMargo via users wrote: On 6/12/21 11:39 PM, ToddAndMargo via users wrote: Oh poop!  Figured it out! # systemctl status named-chroot.service ● named-chroot.service - Berkeley Internet Name Domain (DNS)   Loaded: loaded (/usr/lib/systemd/system/named-chroot.service;

Re: FC34 broke my bind

On 13/06/2021 16:29, ToddAndMargo via users wrote: On 6/12/21 11:39 PM, ToddAndMargo via users wrote: Oh poop!  Figured it out! # systemctl status named-chroot.service ● named-chroot.service - Berkeley Internet Name Domain (DNS)   Loaded: loaded (/usr/lib/systemd/system/named-chroot.service

Re: FC34 broke my bind

On 6/12/21 11:39 PM, ToddAndMargo via users wrote: Oh poop!  Figured it out! # systemctl status named-chroot.service ● named-chroot.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled; vendor preset: disabled) Active:

Re: FC34 broke my bind

On 6/12/21 11:09 PM, Tim via users wrote: On Sat, 2021-06-12 at 22:50 -0700, ToddAndMargo via users wrote: So why am I getting "file not found" in the following? If your files are at the expected paths, check SELinux. It's a common cause of unexpected and unexplained "file not found" errors.

Re: FC34 broke my bind

Oh poop! Figured it out! # systemctl status named-chroot.service ● named-chroot.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; enabled; vendor preset: disabled) Active: active (running) since Sat 2021-06-12 14:49:05 PDT; 8h

Re: FC34 broke my bind

On Sat, 2021-06-12 at 22:50 -0700, ToddAndMargo via users wrote: > So why am I getting "file not found" in the following? If your files are at the expected paths, check SELinux. It's a common cause of unexpected and unexplained "file not found" errors. -- uname -rsvp Linux 5.11.21-100.fc32.x

Re: FC34 broke my bind

On 6/12/21 4:39 PM, ToddAndMargo via users wrote: Hi All, Just upgraded from FC33 to FC34. # rpm -aq bind\* bind-export-libs-9.11.11-1.fc30.x86_64 bind-license-9.16.16-1.fc34.noarch bind-dnssec-doc-9.16.16-1.fc34.noarch bind-libs-9.16.16-1.fc34.x86_64 bind-utils-9.16.16-1.fc34.x86_64 bind-dnss

Re: FC34 broke my bind

On 6/12/21 5:13 PM, Todd Zullinger wrote: Hi, ToddAndMargo via users wrote: Hi All, Just upgraded from FC33 to FC34. FC34 broke my bind. Here are "some" of the repeating errors: Bind was updated from 9.11 to 9.16 in Fedora 34: https://fedoraproject.org/wiki/Changes/BIND9.

Re: FC34 broke my bind

On 6/12/21 5:26 PM, Tom Horsley wrote: On Sat, 12 Jun 2021 16:39:45 -0700 ToddAndMargo via users wrote: Please note this all worked perfectly under FC33 Named completely ceased working for me under f34 as well (I just run a server for my local LAN). Apparently some setting in the new config f

Re: FC34 broke my bind

On Sat, 12 Jun 2021 16:39:45 -0700 ToddAndMargo via users wrote: > Please note this all worked perfectly under FC33 Named completely ceased working for me under f34 as well (I just run a server for my local LAN). Apparently some setting in the new config files screwed something up. Rather than t

Re: FC34 broke my bind

Hi, ToddAndMargo via users wrote: > Hi All, > > Just upgraded from FC33 to FC34. > > FC34 broke my bind. Here are "some" of the repeating errors: Bind was updated from 9.11 to 9.16 in Fedora 34: https://fedoraproject.org/wiki/Changes/BIND9.16 You'

FC34 broke my bind

Hi All, Just upgraded from FC33 to FC34. FC34 broke my bind. Here are "some" of the repeating errors: # named-checkzone -t /var/named/chroot/var/named/slaves xyz xyz.hosts xyz.hosts:3: ignoring out-of-zone data (xyz.local) xyz.hosts:15: ignoring out-of-zone data (DeadStick