Guides

Stopping people from getting around the filter

How to make sure devices can't simply switch to another DNS server, a VPN or a private relay.

A determined student or user can try to avoid filtering by pointing their device at a public DNS server such as 8.8.8.8, or by using a VPN. Linda closes these gaps in three layers.

1. Redirect all DNS on the router

The router rules your portal generates send every DNS request leaving your network to Linda, even if a device has a different server typed in. MikroTik, Cisco, Juniper, Fortinet, pfSense and other guides include this step.

2. Block encrypted DNS to other providers

Browsers can send DNS over HTTPS directly to public resolvers. The generated rules block DNS over TLS (port 853) and the addresses of well-known public resolvers.

3. Turn on "Block DNS bypass" in your policy

This blocks the names of public resolvers, VPN services, proxies and private relays, and tells Firefox not to switch on its own encrypted DNS. It works even on simple home routers that can't run custom rules.

Check it works

From a device on the network, run nslookup phishing-test.linda.example 8.8.8.8. If the router redirect is in place, the answer comes from Linda and the test domain is blocked.

Ready to try it? Linda protects your first network free for 14 days.

Start free trial