Hi Philip.
I echo Fred's response; why forward?
- Backup your config
- remove/comment the "forwarders {}" statement
- start a tcpdump to disc for port 53 (for evidence about what happens next)
- stop/start 'named'.
- try queries/look in the log/stop the tcpdump and analyse it in Wireshark.
As an a
On 23-09-2022 21:59, Ed Daniel wrote:
As per your previous email 17:54 where you share Sparklight response,
Quad9 uses strict DNS checking iirc, you should add another couple of
cloud DNS resolvers like 1.1.1.1 and 8.8.8.8 that fall back to resolve
when DNSSEC is broken at destination.
As I hin
Why are you forwarding at all?
On Fri, 23 Sep 2022, Philip Prindeville wrote:
I've changed locations (moved houses) and consequently ISPs (now on
Sparklight, used to have CTC) and I'm seeing a slew of DNS issues I
didn't have before [...]
As you can see, a LOT of noise.
[...]
// If y
As per your previous email 17:54 where you share Sparklight response,
Quad9 uses strict DNS checking iirc, you should add another couple of
cloud DNS resolvers like 1.1.1.1 and 8.8.8.8 that fall back to resolve
when DNSSEC is broken at destination.
forwarders {
// Sparklight
Hi all,
I've changed locations (moved houses) and consequently ISPs (now on Sparklight,
used to have CTC) and I'm seeing a slew of DNS issues I didn't have before like:
Sep 23 11:42:13 OpenWrt3 named[28113]: timed out resolving
'wdatpsngatewaytmcacane.trafficmanager.net/A/IN': 9.9.9.9#53
Sep 23
5 matches
Mail list logo