Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Unbound DNS key error

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 1 Posters 1.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F Offline
      farrina
      last edited by

      Hello

      I am running 2.4.2-RELEASE-p1 (amd64) and am having periodic failures with DNS (unbound running in I believe resolver mode with DNSSEC enabled).

      Looking in the status / system logs / DNS resolver I am seeing at the time of DNS failure the following entries (snipped to avoid repetition)

      Jan 1 15:57:42 unbound 80204:3 info: failed to prime trust anchor – DNSKEY rrset is not secure . DNSKEY IN
      Jan 1 15:57:26 unbound 80204:2 info: failed to prime trust anchor -- could not fetch DNSKEY rrset . DNSKEY IN

      I am also running pfblockerNG and this updates once a day. The above error seems to commonly occur on the restart of unbound post pflockerNG update, but it can also occur randomly (whilst undound is running).

      Usually the error seems to disappear after a short period of time (say 5 minutes) and dsn resolution recommences

      I wonder if anyone can assist with any troubleshooting suggestions ?

      Cheers

      1 Reply Last reply Reply Quote 0
      • F Offline
        farrina
        last edited by

        In case anyone else comes across this query I thought I would post an update.

        Since posting my original message I have continued to experience intermittent key errors lasting for minutes at a time (with consequent loss of DNS resolution).

        Now it may be mere coincidence, but since I enabled Pre-fetch DSN Key Support (Services/DNS Resolver/Advanced Settings I have not experience a repetition of these key error message.

        I don't profess to know the reason why this might have resolved my issue.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.