Knot Resolver: Resolve DNS names like it's 2021! https://www.knot-resolver.cz/support/
#define FREQUENT_PSAMPLE 10 /* Sampling rate, 1 in N */
kresd -v ...
manually in terminal)
dig githubstatus.com AAAA
;; ANSWER SECTION:
githubstatus.com. 900 IN AAAA fe80::21b:aabb:b9c7:6c99
githubstatus.com. 900 IN AAAA fe80::21b:aabb:b9c7:6d99
githubstatus.com. 900 IN AAAA fe80::21b:aabb:b9c7:6e99
githubstatus.com. 900 IN AAAA fe80::21b:aabb:b9c7:6f99
;; AUTHORITY SECTION:
githubstatus.com. 900 IN SOA ns-1330.awsdns-38.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
modules = {
'policy',
'stats',
'http',
'hints',
'serve_stale < cache',
'workarounds < iterate',
dns64 = 'fe80::21b:77ff:0:0',
}
(kresd 5.1.3) We are using the configuration line in cases where we want to bind to all available IP addresses and it works very well:for name, iface in pairs(net.interfaces()) do pcall(net.listen, {iface['addr'], 53 }) end
Usually the port binding is immediate, but on a particular instance we see a huge delay. It takes almost a minute before the kresd process(es) binds to the ports (as observed through netstat
)
Does anyone have an idea what could be the root cause for such a behavior?
sudo pkill -SIGABRT kresd
perhaps
hints.use_nodata(false)
kresd[14932]: DNSSEC validation failure fedoraproject.org. DNSKEY
kresd-5.1.3, zacalo to delat po upgradu na Fedoru 33 u spousty domen. nslookup fedoraproject.org
vraci SERVFAIL, pri dotazu primo na 1.1.1.1 nebo jakoukoliv jinou adresu vrati uspesne adresy