How to block DoH with BlueCat’s threat feed option
The use of DNS over HTTPS (DoH) is surging. That’s bad news for security admins. If you’re looking to block DOH, BlueCat’s threat feed makes it easy.
The article explains how DNS over HTTPS (DoH) usage surged during the pandemic—BlueCat observed a 1,500% increase in DoH domain queries across its customer base—and describes operational impact and mitigation steps for enterprises. Because DoH encrypts DNS queries it eliminates visibility for network and security administrators, so organizations using centralized DNS management can block DoH by adding known DoH resolvers to a response policy zone (RPZ) or by enabling BlueCat’s dedicated DoH threat feed. The piece details step-by-step deployment instructions for enabling the BlueCat Threat Protection DoH Public Servers feed in DNS Integrity (Address Manager) and DNS Edge, and notes BlueCat will maintain the feed as new DoH resolvers appear.
Why should an enterprise block DNS over HTTPS (DoH)?
Enterprises should consider blocking DoH because it encrypts DNS queries and therefore eliminates visibility for network and security administrators. That loss of visibility can interfere with monitoring, threat detection, policy enforcement, and overall network protection. The article highlights that DoH usage spiked during the pandemic—BlueCat saw a 1,500% increase in DoH domain queries—so the operational impact is real and widespread; blocking DoH via centralized DNS management helps maintain control and visibility across the corporate environment.
How do I enable the BlueCat DoH threat feed in DNS Integrity (Address Manager)?
To enable the BlueCat DoH threat feed in DNS Integrity, log into BlueCat Address Manager and select the DNS tab, ensuring the page is the configuration information view. Under DNS Views choose a DNS View and open the Response Policy Zones sub-tab. Click New and select Response Policy Zone, then under General add the RPZ name. For Type, select the “BlueCat Threat Protection DoH Public Servers” option and set any other deployment parameters you want. Finally click Update to apply the response policy zone with the DoH threat feed.
How do I enable the BlueCat DoH threat feed in DNS Edge and how is the feed maintained?
In DNS Edge, log into the DNS Edge user interface and select Policies from the top navigation bar. Choose an existing policy that uses the BlueCat Threat Protection domain list and click Edit. Within that policy select the BlueCat Threat Protection DoH Public Servers option, then click Save and Apply to enable the feed. The article notes BlueCat actively monitors for new DoH resolvers and adds them to the threat feed so enterprises remain protected as DoH usage evolves; additional details and technical notes are available via BlueCat’s care portal and an informational webinar.
DNS over HTTPS (DoH) is a method of encrypting DNS queries that has gained a lot of traction recently. In February 2020, DoH was added as a default setting in the Firefox browser.
Now ordinary users are jumping on the bandwagon. When the pandemic left everyone working from home, BlueCat noticed a 1,500% increase in DoH domain queries across its customer base. That dramatic surge in DoH usage continues to this day.
Opinions vary on the benefits of DoH, but one thing’s for sure: It reduces the visibility of network and security administrators to zero. If you’re charged with protecting a corporate network, you’re probably going to want to prevent users from accessing DoH services across the enterprise.
If you’re using a centralized DNS management platform like BlueCat, it’s easy to block DoH by adding known DoH resolvers to a response policy zone (RPZ). The longer-term challenge is adding any new DoH services that appear in the future to that block list.
BlueCat has made it easy by creating a new threat feed specifically for known DoH resolvers. BlueCat has long used threat feeds to bolster defense-in-depth. To disable DoH across the enterprise, all you have to do is enable this threat feed for DoH in either DNS Edge or DNS Integrity, and you’ll be all set.
How to deploy the DoH threat feed in DNS Integrity
- Log into BlueCat Address Manager.
- Select the DNS tab. Tabs remember the page you last worked on, so select the tab again to ensure you’re on the configuration information page.
- Under DNS Views, click a DNS View and then the Response Policy Zones sub-tab.
- Under Response Policy Zones, click New and select Response Policy Zone.
- Under General, add the name of the response policy zone.
- Under Type, select the “BlueCat Threat Protection DoH Public Servers” option and apply other deployment parameters as desired.
- Click update.
How to deploy the DoH threat feed in DNS Edge
- Log into the DNS Edge user interface.
- In the top navigation bar, select Policies.
- Select an existing policy that uses the BlueCat Threat Protection domain list, and click Edit.
- Select the BlueCat Threat Protection DoH Public Servers option.
- Click save and apply.
BlueCat is keeping an eye out for any new DoH resolvers and adding them to the threat feed. As a result, you’re covered even as DoH usage evolves.
Our care portal contains more information about DoH threat feed options, including detailed technical notes. You can also learn more about the pros and cons of DoH in a webinar with BlueCat’s Chief Strategy Officer Andrew Wertkin.