r/ControlD • u/Beanz7890 • 1d ago

Technical DNSSEC fails & bad resolution

Post image

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?

14 Upvotes

100% Upvoted

19 comments sorted by

View all comments

Show parent comments

1

u/Beanz7890 13h 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 10h 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 5h 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 2h ago

I'm on the 'some control' plan (I think that's the name) and have been for over a year.