Recommendations for use

If content filters and BPJM filters are to be used together, both rules must be configured with different priorities so that they are run through one after the other.

Likewise, for the first rule, care must be taken to ensure that the item "Observe further rules, after this rule matches" is activated.

In rare cases, the BPJM module may block desired domains because only (DNS) domains and not URL directory levels can be checked due to TLS. In this case, these desired domains can be added to the "BPJM Allow list", e.g. *.example.com.

The LANCOM router must serve as DNS server or DNS forwarder in the network, i.e. clients in the local network must use the router as DNS server. In addition, the direct use of DNS-over-TLS and DNS-over-HTTPS (possibly browser-internal) with external DNS servers by clients must be prevented.

This can be achieved as follows:
Note:

Notes on synchronizing the firewall's DNS database:

Because the firewall learns its information from client DNS requests, in certain situations the DNS database may not yet be complete. This can happen in the following situations:
  • A new firewall rule is added, but the client still has a DNS record cached.
  • Shortly after the router reboots and the client still has a DNS record cached.

In these cases, clearing the DNS cache on the client, rebooting the client, or timing out the DNS record on the client will help.

Note: If different DNS names resolve to the same IP address, then they cannot be distinguished. In this case, the first rule that references one of these DNS names always applies. This should not be a problem with large service providers. However, it could occur with small websites hosted by the same provider.

www.lancom-systems.com

LANCOM Systems GmbH | A Rohde & Schwarz Company | Adenauerstr. 20/B2 | 52146 Wuerselen | Germany | E‑Mail info@lancom.de

LANCOM Logo