Re: 'managed-keys' is deprecated ??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 15/06/2021 12:42, ToddAndMargo via users wrote:
On 6/14/21 9:16 PM, Todd Zullinger wrote:
ToddAndMargo via users wrote:
Placing
    include "/etc/named.root.key";
in my bind.conf, give me the following error


# named-checkconf -l -t /var/named/chroot /etc/named.conf
/etc/named.root.key:1: option 'managed-keys' is deprecated

What do I use it its place?  (The Duck is failing me.)

The fine manual¹ covers this:

     managed-keys

         Is identical to trust-anchors; this option is
         deprecated in favor of trust-anchors with the
         initial-key keyword, and may be removed in a future
         release.

¹ https://bind9.readthedocs.io/en/latest/reference.html#index-0

Bind has some very thorough documentation.  It's even
easily searchable if you view it online.  That's better than
any general search engine.

Hi Todd,

Then I do believe I just tripped across a bug:

# cat --number named.root.key
     1    trust-anchors {

Line 1 is NOT 'managed-keys'.

Or perhaps it was just a warning to confuse
the dickens out of the uninitiated?


If I were you I may consider checking the upgrade logs.

While not using the chroot service I just upgraded my internal bind system from F33 to F34.
I do have all of these installed on the upgraded system.

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-dnssec-utils-9.16.16-1.fc34.x86_64
bind-9.16.16-1.fc34.x86_64
bind-chroot-9.16.16-1.fc34.x86_64

There exists only one

[root@f33k ~]# locate named.root.key
/etc/named.root.key

And the first line of that file contains

trust-anchors {

I didn't change anything in /etc/named.root.key since my named.conf contains

        dnssec-enable yes;
        dnssec-validation yes;

And using your example in your notes post.

[egreshko@f33k ~]$ delv @208.67.222.123 com ds
; fully validated

Also, the named.service was enabled, it started at the boot, and there were no errors.


--
Remind me to ignore comments which aren't germane to the thread.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux