I'm seeing wonky networking connectivity and my DNS logs are full of these types of notifications:
2024:06:07-00:17:08 wahine named[5119]: checkhints: view no_rpz_dlz: b.root-servers.net/A (170.247.170.2) missing from hints 2024:06:07-00:17:08 wahine named[5119]: checkhints: view no_rpz_dlz: b.root-servers.net/A (199.9.14.201) extra record in hints 2024:06:07-00:17:11 wahine named[5119]: network unreachable resolving '55.134.164.60.in-addr.arpa/PTR/IN': 2001:dd8:e::53#53 2024:06:07-00:17:11 wahine named[5119]: network unreachable resolving '55.134.164.60.in-addr.arpa/PTR/IN': 2001:13c7:7002:3000::14#53 2024:06:07-00:17:11 wahine named[5119]: network unreachable resolving '55.134.164.60.in-addr.arpa/PTR/IN': 2620:38:2000::53#53 2024:06:07-00:17:11 wahine named[5119]: network unreachable resolving '55.134.164.60.in-addr.arpa/PTR/IN': 2001:67c:e0::9#53 2024:06:07-00:17:11 wahine named[5119]: network unreachable resolving '55.134.164.60.in-addr.arpa/PTR/IN': 2001:ddd::53#53 2024:06:07-00:17:11 wahine named[5119]: resolver priming query complete
There appears to be a problem with something called the 'checkhints' file. I have never had to manage the bowels of DNS server functionality within the UTM presumably because DNS is such a fundamental land essential part of modern networking, it always has just worked.
Does anyone have a hint as to what I can do?
This thread was automatically locked due to age.