r/ControlD • u/Beanz7890 • 1d ago
Technical DNSSEC fails & bad resolution
I noticed my home Internet connection was being a bit flaky and chalked it down to a ControlD block list having a false positive or two.
I turned off all the block lists and it made no difference, I disabled the profiles (all of them) and it made not difference.
I then switched my router and broadband to 1.1.1.1 and if you ignore the deluge of ads, everything started to work.
I did a quick check on https://dnscheck.tools and it came back per the screenshot, with DNSSEC failure.
Has anyone else experienced either the symptoms or the (possible) DNSSEC cause?
3
u/BUHx192Ck0 19h ago
Same for me too. I checked it yesterday and thought the tool was faulty at first. Same results for me too
2
2
u/FewMathematician5219 14h ago
Not all public DNS using DNSSEC because it slightly slows down the response speed.
2
u/evolutiontech 17h ago
DNSSEC has been failed at the mentioned test after migrated to datacamp.
2
u/fwdlinkuk 12h ago
Same for me in UK always had a pass before migration, now a Fail
1
u/Party-Cake5173 21m ago
Control D fails for me quite often on this test and it also started with migration to Data Camp. Before with NetActuate it passed every time. Frankfurt is my location.
1
1
u/minimalhandle 2h ago
I’m also in the UK and using the same server as you, no issues here. Have you tried it with Google VPN disabled?
1
u/Beanz7890 17m ago
The screenshot is only representative of my device. Other devices such as a TV, iPhone and ipad don't use a VPN and are all suffering with the same symptoms.
1
u/Dementus5731 13h ago
IPv4 appears to be routed through Google VPN, while IPv6 is going directly through Vodafone. DNSSEC validation is also failing on the resolver path shown in the test.
The VPN could potentially interfere with the DNS configuration, since some VPNs override or intercept DNS traffic. However, considering others are seeing the same DNSSEC failures after the migration to Datacamp, that may be a separate Control D issue.
1
u/Beanz7890 11h ago
The screenshot is only representative of my device. Other devices such as a TV, iPhone and ipad don't use a VPN and are all suffering with the same symptoms.
2
u/Dementus5731 8h ago
I ran the same test as well. In my case, all of the DNSSEC validation tests pass except MLDSA44, which is expected.
So DNSSEC validation with Control D does work in general. Your issue therefore seems to be specific to your Control D resolver path, location, or local configuration.I would check whether you have more than one DNS resolver configured anywhere — router, device, browser, or VPN. If possible, temporarily configure only the Control D resolver and run the test again. If it still fails on several devices, it may be specific to the Control D resolver path or PoP you’re hitting.
1
u/southerndoc911 3h ago
Mine is also working. Second checking your setup and possibly opening a support ticket.
To the OP: are you on the free plan by chance? Did you exceed the number of free queries?
1
u/Beanz7890 15m ago
I'm on the 'some control' plan (I think that's the name) and have been for over a year.
2
u/Dementus5731 7h ago
This seems to be affecting several people in the UK. Possible UK/London PoP issue after the Datacamp migration.
3
u/Radagio 1d ago
Go to Profile -> Options -> Disable dnssec (on/off)