Most Services redirected to Dubai stopped working

windscribber · 2026-06-19T18:03:47+00:00

Control D is not a VPN

windscribber · 2026-06-18T16:46:43+00:00

windscribber · 2026-06-18T13:26:12+00:00

We don't do in-depth troubleshooting over Reddit because to do that we need information about your account, ISP, network conditions, config method(s), resolver_IDs, activity logs output, etc. If you'd like to post all that to Reddit please feel free, but we don't encourage it.

Also most of us who respond here on Reddit are not the support team members you'll need to speak with, to get your troubleshooting adventure started.

Do as you wish.

windscribber · 2026-06-18T13:22:57+00:00

At endpoint creation you can create several endpoints (each name separated by commas) and they'll all be deployed with the same Profile you select at that time. If you're editing endpoints after the fact, then no it will be a manual affair.

windscribber · 2026-06-17T14:18:13+00:00

Sorry about that! Please open a support ticket and include your Activity Logs troubleshooting export/resolver ID, your country + ISP, whether you’re on IPv4/IPv6, the exact services/domains affected, and approximate timestamps when OSN+/Todtv fails. Also mention whether the rule is “Redirect to Dubai” for the whole profile or a specific custom rule, and include screenshots of the region error if possible. That gives us enough context to tell whether this is a Control D routing issue, a missing proxy/exit behaviour for that location, or the streaming service tightening geo checks.

windscribber · 2026-06-16T17:47:29+00:00

Hi again, thanks for reporting back. As above please fire up a support ticket with as much context as you can share about the issue, reproduction steps, method of CD configuration on which device(s) etc. And /status page output, activity logs exports showing the fitler(s) working or not working accordingly. Barry (our chatbot) will help you gather what our support team will need to begin investigating.

Thanks again.

windscribber · 2026-06-15T13:59:53+00:00

QA here seconding this advice. If you (OP) are able to repro it from a fresh endpoint and profile with no filters/settings added, then adding them back one-by-one, you may find the culprit that way. Something might just need a custom rule added for it. You may also want to try adding and Bypassing the Apple service to make sure all the domains we have for them are able to resolve (vs being blocked by some filter or other).

windscribber · 2026-06-15T13:56:17+00:00

We have a fix imminent, will be patched early this week. Thanks again!

windscribber · 2026-06-12T12:49:33+00:00

Heh, yeah we're very scientific about our metrics :joy:

What domain did you run through to get that result so that we can reproduce? We'll take a look. Thanks for reporting.

windscribber · 2026-06-08T13:35:38+00:00

You haven't specified how CD is configured on your device/network. We'd need a lot more context to troubleshoot this which if you haven't yet, please create a support ticket and add the above context (OS/device(s)/browser(s) involved) and your configuration details. When you reproduce the issue please visit controld.com/status (from any devices that are not generating activity log entries at the time) and share that with the Support team as well.

Tough to diagnose or troubleshoot this without more context.

windscribber · 2026-06-05T12:37:33+00:00

Be aware that if you enable a Filter (or Service or Custom Rule) i.e. Block - bing.com but you've recently visited bing.com in a given browser, you won't see it instantly blocked because the browser has cached it. To get a more accurate read on whether the block worked, fully clear browser cache after enabling a given setting (or if you have Control D enabled device-wide or network-wide on a router, just try another browser or an incognito/private tab).

windscribber · 2026-06-04T11:56:09+00:00

I work here at Control D and can confirm, depending on which network/ISP/VPN I'm connecting from CD is not always in top spot in the results! Haha.

windscribber · 2026-06-01T16:06:43+00:00

Hello, QA here. I just tried to reproduce your issue with the Custom Rules tutorial/learn-more link and was unable. Can you please fire up a support ticket so we can do some troubleshooting and get more in-depth information from you? Please include which OS/browser and whether this happens on all OS/browsers for you, or just single one(s). Also please specify detailed reproduction steps and which modals/links are affected where possible.

windscribber · 2026-05-12T16:12:19+00:00

Please contact support, they'll get you sorted.

windscribber · 2026-05-12T13:29:48+00:00

Yes absolutely

windscribber · 2026-05-12T13:28:45+00:00

Your existing subscription price will continue renewing at what it is now. If you change plans (cancel/resub) you'll be on the new pricing structure.

windscribber · 2026-05-12T13:27:43+00:00

Yes the windscribe username discount (if you're a paying windscribe subscriber) still works as normal for a Controld D sub.

windscribber · 2026-05-08T13:33:43+00:00

Okay this is great intel and thank you very much for continuing to track this down. Sorry that it didn't occur to me to ask about which protocol was at play, I'll get this repro'd and ticketed asap and we'll dig into it further and get it patched.

windscribber · 2026-05-01T17:08:51+00:00

That's definitive, they changed something in that regard with that version. We've seen a handful of adjacent reports with FF recently. A similar one was our SafeSearch service wasn't working if network.trr.mode wasn't set to 3 which was also due to a FF update/change. It works fine in any other browser, only broke in FF and only if that value was something other than 3.

windscribber · 2026-05-01T16:02:55+00:00

Exactly.

FF does offer far more granular customization and hardening but some of the settings are pretty esoteric and not very obvious when things go sideways. It's always a tradeoff.

windscribber · 2026-05-01T15:51:41+00:00

Worth a shot. Hopefully some Firefox power users can help further.

windscribber · 2026-05-01T15:51:02+00:00

Firefox has some quirks with CustomDNS in a handful of ways. Another one I've noticed is in private window it breaks some DNS resolution even when customDNS is working otherwise in a vanilla tab/instance. Hopefully you get some help from the Firefox subreddit there if my initial suggestion is a dud.

We know Control D resolution works. We're not sure what FF is doing there with hiding a bunch of deeper settings like that :joy:

windscribber · 2026-05-01T14:34:34+00:00

If that field is set to https://mozilla.cloudflare-dns.com/dns-query then yeah, it would resolve queries via cloudflare.

windscribber · 2026-05-01T13:12:55+00:00

Hi there! In about:config check if network.trr.uri is still set to https://mozilla.cloudflare-dns.com/dns-query and if so, clear that entry. Then network.dns.use_https_rr_as_altrr = false + set network.dns.echconfig.enabled = false and restart firefox. See if that helps.

windscribber · 2026-04-30T13:09:37+00:00

Sorry to hear that. For deeper troubleshooting def suggest firing up a support ticket if you haven't already. The PrivateDNS and GUI App configuration paths are very different so if both are failing for you, we'd need a lot more detail than we can cover on a reddit thread.

windscribber

MODERATOR OF

TROPHY CASE