- Custom Rules are matched first. If there is no Custom Rule (Block, Bypass, or Redirect) that matches the DNS query, we proceed to the next scope.
- Service Rules are matched second. If there is no matching rule within this context, we proceed further.
- Filters are matched third. Unlike the first 2 scopes, these can only block things. If no Filter matched the DNS query, we proceed to the 4th and final scope.
- Default Rule matches everything that wasn't affected by any of the 3 previous scopes. This will either resolve a domain to its true IP (BYPASS), spoof to a location (REDIRECT) or block the query entirely (BLOCK).
If you happen to use Multiple Enforced Profiles feature, your 2nd Enforced profile would then follow the same logic as above, however the Default Rule in the first Profile must be set to BYPASS. If it's set to REDIRECT or BLOCK, the 2nd Profile will be ignored.
Once you wrap your head around the above, you can create highly customizable behaviors. For example.
Your Default Rule is set to REDIRECT mode, which will spoof all domains you resolve to Control D IPs and mask your source IP from websites you visit. This may not be desirable for everything, and you may want to access certain websites and services (like your bank, or a game) using your true source IP.
Since Custom Rules and Service Rules are always consulted before Default Rule, you can create an overriding record that will be matched first. Simply choose your desired Service from the Services section, and create a BYPASS rule for it. Alternatively, you can do the same for any domain name in the Custom Rules section.
Now, your chosen services and domain names will always resolve to their true IPs, same as any other DNS resolver, while all other traffic is going to be redirected.
Control D supports over 400 different web services and apps in the Services section. These are essentially collections of domains that we painstakingly curated for your convenience. Toggling a single switch that assigns is a rule type, does so for dozens (and sometimes hundreds) of different domains which could be used to deliver a single service. Some of these services may require certain tracking domains to be loaded, otherwise the service may not work in all scenarios. Since Service Rules are matched before Filters, they will supersede them and allow for trackers to load. If this is not desirable, you can create a Custom Rule to re-block the desired tracking domain. As Custom Rules are matched first, these will supersede Service Rules.
If you recall, the default matching order is: Custom Rules -> Service Rules -> Filters -> Default Rule. What if you wanted to enforce these scopes in a different order, say.... Filters -> Custom Rules -> Service Rules -> Default Rule. One way to achieve that is to leverage Multiple Enforced Profiles feature.
Enable all the Filters you wish to enforce, and don't create any Service or Custom Rules inside this profile. Default Rule should be set to BYPASS.
In your 2nd Enforced Profile, create your Service and Custom Rules, and don't enable any Filters here (since they exist in your first profile).
Now when a query arrives, it's matched against your first profile first, since here are no Service or Custom Rules, there is nothing else to do except try to match the Filters. If there is a match, the query is blocked. If there is no match, then the 2nd profile will be consulted.
Updated about 2 months ago