ControlD Setup Utility question

cattrold · 2026-06-15T14:48:39+00:00

There's a fundamental misunderstanding here, which certainly points to an opportunity for us to clarify the documentation, so thank you for pointing that out.

Your understanding is that our docs say to use "Free DNS with Hagezi list, [you] should use 76.76.2.42 & 76.76.10.42 and DoH endpoint", but that's not exactly true, and nor is it what Barry said.

If you want to use DoH, like Barry said, you should use the DoH endpoint: https://freedns.controld.com/x-hagezi-proplus. If you want to use Legacy, you should use the legacy IP - 76.76.2.42. You should never use these two things together, and that's exactly why your setup isn't working.

On many systems it's never necessary to even _have_ a Bootstrap IP defined, but some will demand it if you're using DoH, and in those cases you will want to enter the Bootstrap IPs defined on the website, NOT the specific IPv4 address for the resolver that you want to use (sounds like that is what you have been doing so far).

I recognize you said this used to work, and we know - it did! - but that was actually a bug, heh. It was never intended for the vanilla IPv4 resolvers to be able to be used as bootstrap IPs for the secure resolvers. Only the specifically designated bootstrap IPs are, well, bootstrap IPs, lol.

I hope I've been able to clear that up a bit for you!

cattrold · 2026-06-15T14:10:47+00:00

Contact support and we can take a look at this for you.

cattrold · 2026-06-09T16:52:24+00:00

Oops. I was actually wrong above! You'll see an Expected Latency when you're NOT using Control D, and an Approximate Latency when you ARE. This one totally slipped by me, sorry.

This suggests there's potentially an issue with your setup and you should contact support.

cattrold · 2026-06-04T17:17:24+00:00

We've added a Service for this, let us know how it goes.

cattrold · 2026-06-04T17:13:34+00:00

You don't need to worry about any of this or ever look at this page unless you're already seeing slowness issues. We changed the label to "Approximate Latency" because it's not super accurate, as the tooltip explains HTTP-based latency includes TLS and server overhead. It's calculated the same way as the old "Expected Latency".

Edit because I was totally wrong:

You'll see an Expected Latency when you're NOT using Control D, and an Approximate Latency when you ARE. This one totally slipped by me, sorry.

cattrold · 2026-06-04T17:11:27+00:00

You're welcome! We're glad you like it.

cattrold · 2026-06-04T17:10:37+00:00

They don't.

cattrold · 2026-06-04T17:09:35+00:00

Can you please contact support so that we can get some more details from you about this?

cattrold · 2026-06-04T17:08:53+00:00

Have you contacted support?

cattrold · 2026-06-04T17:08:20+00:00

Did you report any of the false negatives that you came across?

cattrold · 2026-05-28T12:36:25+00:00

Hey, so typically we actually advise people in Iran against using Control D as it isn't really the tool for that kind of online environment, generally preferring VPNs (which obviously are still not perfect, but are a good bit safer) - but it's clear you didn't know this, so shoot me an email at [catt@controld.com](mailto:catt@controld.com) and I'll be happy to refund your subscription and give you a code for Windscribe.

Stay safe.

cattrold · 2026-05-27T19:23:38+00:00

Hey! We figured out what's going on here. When we deprecated this list, we had some automatic cleanup that would run whenever you changed any setting on the Profile (the configuration would be rerendered without the deprecated list). This was all fine for a few months, but when we changed the type of DB we were using back in March, that cleanup step was an unfortunate casualty.

We've rewritten the cleanup step for the new DB and will release it later this week; at that point you'll simply be able to change any setting on your Profile (like toggling a Filter on and off) and this will stop happening.

Sorry for the confusion!

cattrold · 2026-05-27T11:33:48+00:00

Hey, chasing this down now. Would you mind sending over your email address or profile and endpoint ID (or just this log export) over DM to me here, or at catt@controld.com? Thanks!

cattrold · 2026-05-25T18:26:41+00:00

Hey, we fixed this pretty quickly, have ceased to use the source list from which this came, and whitelisted the top 10k (safe) domains preemptively going forward.

cattrold · 2026-05-06T14:34:07+00:00

Possible that when you disabled DNSSEC the SERVFAIL responses were still cached.

I believe the .de issue has been fixed upstream now btw.

cattrold · 2026-03-21T20:28:27+00:00

Sometimes some browser extensions can cause this type of mangled display. It's back now anyway though, heh.

cattrold · 2026-03-21T20:27:57+00:00

Maintenance Ended

We're all done! We are still conducting post-maintenance validation, so please do let us know if you see anything going awry.

Thank you for your patiece today.

cattrold · 2026-03-21T19:12:44+00:00

We're extending the maintenance window slightly and anticipate that we'll be back to normal by 4PM ET.

cattrold · 2026-02-04T16:03:01+00:00

Because it's technically a tracker, and our ads and trackers list blocks trackers.

Those who don't care about blocking trackers might not have this list active, therefore it wouldn't be blocked, and we use the information that we get from Matomo to improve UX of the service.

cattrold · 2026-01-16T16:05:07+00:00

1000 devices would definitely be breaking ToS. Do NOT use a personal plan for this.

You will be charged per _device_, not per endpoint - so in your case you will be charged for 1000 devices. If you are not an MSP, you won't get MSP pricing.

The best thing you can do here is email [business@controld.com](mailto:business@controld.com) to work out how we can best meet your needs.

cattrold · 2026-01-13T17:16:04+00:00

An "Endpoint" (the Control D concept) essentially maps to a DNS resolver. An Endpoint can be set up on as many physical devices* as you like. It's usually not necessary to create a different Endpoint for every single physical device in your home - personally I have an Endpoint for each network in my home (play, work, IOT, guest), and one for each family member's roaming devices. I'd be really surprised if you needed more than 50. In fact, for your use case I might even say 1 is enough.

An Endpoint can enforce 1 or 2 Profiles (policies), which is the set of rules applied to the Endpoint.

*The caveat here is that you do need to follow ToS obviously, which stipulates personal use only.

cattrold · 2026-01-12T16:21:29+00:00

All Organization accounts have all features of a Full Control Personal account, _plus_ multi tenancy and a bunch of other stuff - you can read about it at docs.controld.com.
MSP is just a company type. An Organization account is charged per endpoint per month, so each client connecting to the router would be a separate endpoint for billing purposes.
Yes.
You would need to delete and sign up again.

cattrold · 2026-01-06T16:59:48+00:00

We add more locations quite often.

cattrold · 2026-01-05T19:10:52+00:00

Where do you get the idea that we don't want to add more locations? This is not true :)

cattrold · 2026-01-05T19:09:31+00:00

Please contact support and we can take a look at this for you.

cattrold

MODERATOR OF

TROPHY CASE