On a 9.20 server that is a resolver only, I have a mystery. This is
running out of the official docker. I have a fleet of these and there is
nothing special about them. But I have a trouble child that provides no
explanation as to why it fails a query every now and then when none of the
other instances do. First I discover that a domain is failing, and I check
it manually:
$ host americanautowire.com 192.168.8.12
Using domain server:
Name: 192.168.8.12
Address: 192.168.8.12#53
Aliases:
Host americanautowire.com not found: 2(SERVFAIL)
Yes, that is indeed failing. So this problem child has been running with
the following log configuration:
########### named.conf:
http local {
endpoints { "/dns-query"; };
};
options {
directory "/var/cache/bind";
listen-on { any; };
listen-on-v6 { any; };
listen-on tls ephemeral { any; };
listen-on-v6 tls ephemeral { any; };
listen-on tls ephemeral http local { any; };
listen-on-v6 tls ephemeral http local { any; };
};
logging {
channel default_file {
file "/var/log/bind/bind.log" size 10m;
severity debug;
print-time yes;
print-severity yes;
print-category yes;
};
category default{ default_file; };
};
########### named.conf:
and the log it produces for the query is simply this:
25-Nov-2024 23:01:56.703 resolver: debug 1: fetch: americanautowire.com/A
25-Nov-2024 23:01:56.703 resolver: debug 1: fetch: com/NS
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:500:2d::d#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:500:2::c#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2801:1b8:10::b#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:500:a8::e#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:500:2f::f#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:dc3::35#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:7fd::1#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:500:9f::42#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:503:ba3e::2:30#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:7fe::53#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:503:c27::2:30#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:500:12::d0d#53
25-Nov-2024 23:01:56.703 lame-servers: info: network unreachable resolving
'com/NS/IN': 2001:500:1::53#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:503:a83e::2:30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:502:8cc::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:502:1ca1::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:502:7094::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:503:d2d::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:503:eea3::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:503:231d::2:30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:500:856e::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:501:b1f9::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:503:39c1::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:503:d414::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:503:83eb::30#53
25-Nov-2024 23:01:56.731 lame-servers: info: network unreachable resolving '
americanautowire.com/A/IN': 2001:500:d937::30#53
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: ns1.g02.cfdns.net/A
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: ns1.g02.cfdns.net/AAAA
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: ns2.g02.cfdns.biz/A
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: ns2.g02.cfdns.biz/AAAA
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: ns3.g02.cfdns.info/A
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: ns3.g02.cfdns.info/AAAA
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: ns4.g02.cfdns.co.uk/A
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: ns4.g02.cfdns.co.uk/AAAA
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: net/NS
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: net/NS
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: biz/NS
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: biz/NS
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: info/NS
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: info/NS
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: uk/NS
25-Nov-2024 23:01:56.815 resolver: debug 1: fetch: uk/NS
25-Nov-2024 23:01:56.815 lame-servers: info: network unreachable resolving
'net/NS/IN': 2001:503:ba3e::2:30#53
25-Nov-2024 23:01:56.815 lame-servers: info: network unreachable resolving
'biz/NS/IN': 2001:503:ba3e::2:30#53
25-Nov-2024 23:01:56.815 lame-servers: info: network unreachable resolving
'info/NS/IN': 2001:503:ba3e::2:30#53
25-Nov-2024 23:01:56.815 query-errors: debug 1: client @0x7fb2d06ea000
172.21.0.10#51271 (americanautowire.com): query failed (failure) for
americanautowire.com/IN/A at query.c:7814
We can ignore all the IPv6 stuff. But what I don't see is anything that
explains the failure. Even more oddly is that if I just make the query
several times in a row, it eventually works just fine.
Is there anything I can do to produce any more messaging in the logs other
than debug? Or has anyone seen anything like this before?
Thank you
-G
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
