Folders

Group your rules into folders, and assign actions to them.

Folders give you a way to organize your Custom Rules and can be used for multiple use cases.

Use Cases

Organization

The simplest use case is to organize your Custom Rules into logical categories, so you can keep track of them all in one place. A normal folder can contain a mix of Custom Rules of all action types.

Action Folders

A folder can be optionally assigned an action, meaning any domain that exist in this folder will inherit the action type of the folder. With this, you can make your own "Allow" and "Deny" folders, or get more creative. For example, create a Redirect folder that spoofs to Toronto proxies. Any domain you add to it, will be automatically spoofed via proxies in Toronto.

1470

Sharing

A folder can be exported as a json file. This file can be modified, or shared, and then re-imported back into another Profile.

1480

Magic Folders

There are special folders that you can create that allow you to enforce advanced behaviors.

Captive Portal Bypass

If you're using Command Line Daemon, GUI Setup Utility or Apple DNS Profiles (.mobileconfig) on roaming devices that frequent public WiFi networks with captive portals, this feature is for you.

πŸ“˜

Common Captive Portals

We're already excluding common captive portals for major airlines and those that were reported to us by users. There is a good chance you don't need to worry about this. However if you encounter a captive portal that indeed does not work, then read on!

Create a folder with this exact name in a Profile enforced by these roaming devices: Magic Captive Portal Bypass.

Any enabled BYPASS rule that you put into this folder will get excluded from using your Control D DNS resolver, much like the base rules we're already enforcing. This allows captive portals to load. Once Internet access is established, then Control D can do its thing.

Rules can be exact hostnames (wifi.airline.com), or wildcards (*.airline.com).

🚧

Updates are not instant

If you encounter a captive portal that doesn't work with Control D (let us know!), and you add a bypass using this method, the changes are not instant and requires end-user action, which depends on how Control D was deployed.

GUI app or ctrld daemon

In order for newly added rules to be enforced, you need to restart the app or daemon. Simply go into the GUI app, and disconnect, and then re-connect. If you're using ctrld daemon, then execute the restart command.

Apple DNS Profile

These cannot be updated, as rules are baked in into the profile itself. You will have to re-download and re-install the DNS profile. Sorry about that.