# Policy Management and Filtering Features

#### <span style="font-weight: 400;">How can I block all subdomains of a specific domain?</span>

<span style="font-weight: 400;">To block all subdomains of a certain domain, you should add the specific record to your </span>**Denylist**<span style="font-weight: 400;">. You must add the domain without the leading WWW to ensure the block is effective. For instance, if your goal is to block subdomains of the </span><span style="font-weight: 400;">https://www.google.com</span><span style="font-weight: 400;"> domain, you would simply enter </span><span style="font-weight: 400;">google.com</span><span style="font-weight: 400;"> into the Denylist.</span>

---

#### <span style="font-weight: 400;">What is NAT DNS, and is it included in my plan?</span>

[Network Address Translation over DNS (NAT DNS)](https://docs.safedns.com/books/installation-guides/page/nat-dns-setup)<span style="font-weight: 400;"> is a specialized feature used for identifying and filtering traffic in specific network environments. However, this feature is not included in all service tiers; it is </span>**not available for the Safe Home and Basic plans**<span style="font-weight: 400;">.</span>

---

#### <span style="font-weight: 400;">How can I create a custom schedule for blocking content?</span>

<span style="font-weight: 400;">SafeDNS provides a </span>[Schedule](https://docs.safedns.com/books/installation-guides/page/schedule-setup)<span style="font-weight: 400;">[ ](https://docs.safedns.com/books/installation-guides/page/schedule-setup)feature that offers more granular control than standard filtering systems. While many systems utilize simple schedules that completely block internet access during set times, the SafeDNS system allows for </span>**content filtering schedules**<span style="font-weight: 400;">. This allows administrators to adjust what types of content are blocked at different times of the day without cutting off internet access entirely.</span>

---

#### <span style="font-weight: 400;">How do I configure the block page that users see when a website is filtered?</span>

<span style="font-weight: 400;">The </span>**block page**<span style="font-weight: 400;"> is the landing page displayed to a user whenever they attempt to access a website that is restricted by your active filtering rules. The documentation includes a dedicated </span>[Block Page Setup](https://docs.safedns.com/books/installation-guides/page/block-page-setup)<span style="font-weight: 400;"> guide to assist administrators in configuring this interface.</span>

---

#### <span style="font-weight: 400;">How can I use the same list of domains across multiple policies?</span>

<span style="font-weight: 400;">To avoid manually entering the same information multiple times, you can use the </span>[Allow/Denylists and Named Lists](https://docs.safedns.com/books/installation-guides/page/allowdenylists-and-named-lists)<span style="font-weight: 400;"> feature. This feature is specifically designed for situations where you need to </span>**apply the same list of domains to different policies**<span style="font-weight: 400;"> across your network, streamlining the management of multiple user groups or filtering levels.</span>

---

#### <span style="font-weight: 400;">How can I prevent users from bypassing web filtering?</span>

<span style="font-weight: 400;">To maintain the integrity of your network policies, SafeDNS offers several </span>[Web Filtering Bypass Prevention](https://docs.safedns.com/books/installation-guides/page/web-filtering-bypass-prevention)<span style="font-weight: 400;"> recommendations. A primary recommendation is to </span>**block the "Proxies &amp; Anonymizers" category**<span style="font-weight: 400;">, which prevents users from accessing external services designed to circumvent DNS-based filters.</span>

<span style="font-weight: 400;">Additionally, administrators should </span>**block specific browser settings or "flags"**<span style="font-weight: 400;"> in Google Chrome and Mozilla Firefox that enable DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT) directly within the browser. Because these browser-level settings can sometimes bypass system-wide DNS configurations, disabling them is a critical step in ensuring all traffic remains filtered.</span>