query failed (SERVFAIL) and query failed (failure)
Barry Scott
barry at barrys-emacs.org
Fri Dec 13 12:24:22 UTC 2024
I have been using named-chroot on Fedora 40 for a long time without issue
on version bind-9.18.28-2.fc40.x86_64.
I have built a new router based on Fedora 41 and named version is
bind-9.18.30-1.fc41.x86_64.
This version is reporting errors like these:
client @0x7fb312835168 172.17.1.173#62806 (bolt.dropbox.com): query failed (failure) for bolt.dropbox.com/IN/A at ../../../lib/ns/query.c:7837
client @0x7fb30fa4d168 172.17.1.200#56216 (mail.gandi.net): query failed (SERVFAIL) for mail.gandi.net/IN/A at ../../../lib/ns/query.c:7837
client @0x7fb30fa4d168 172.17.1.200#56216 (mail.gandi.net): query failed (SERVFAIL) for mail.gandi.net/IN/A at ../../../lib/ns/query.c:7099
client @0x7fb30fa4d168 172.17.1.200#56216 (mail.gandi.net): query failed (SERVFAIL) for mail.gandi.net/IN/A at ../../../lib/ns/query.c:7099
Look at the sources it looks like this is not expected to happen.
Using dig I see it report communication error when logs like this are produced.
retrying the dig command a 30 seconds later I see no more errors and the
expected answer is returned.
Is this a know issue?
Could it be caused by a config error I've made?
I am happy to share named.conf if that will help.
What can I do to help debug this?
I am able to build the named software if required.
Barry
More information about the bind-users
mailing list