Resolving Potential Conflicts

Article author
Josh L
  • Updated

Trouble with DNS Queries

When you're trying to implement DNSFilter on your network, various issues can arise that may interrupt or block its operation. One common sign that something's amiss is a drop in query traffic to our servers. This means that the DNS (Domain Name System) queries—essentially, the internet 'lookup' requests that your network makes—are not reaching us.

There are several reasons this could be happening, but a frequent culprit is hardware security appliances that may have conflicting settings or firewall rules. Simply put, these rules may block DNS traffic from either leaving your network (egress) or coming back to it (ingress).

If you've checked your hardware and are confident that it's correctly configured, consider looking into two other possible sources of conflict:

Software Conflicts

Anti-malware applications, certain browser settings, and even some virtualization software can include default configurations that clash with DNSFilter. These settings can unintentionally prevent DNSFilter from working as expected. We have a separate guide on resolving these Software Conflicts that shows how to tweak these settings to eliminate the conflict.

Transparent Proxying

If you've set up DNSFilter but notice that the changes aren't taking effect—like blocked sites still being accessible or no recorded query traffic appearing on your dashboard—your Internet Service Provider (ISP) may be a part of the problem. Some ISPs use a method called "Transparent Proxying," which reroutes DNS traffic without your knowledge. This rerouting can interfere with DNSFilter's operation. For more information and troubleshooting steps, take a look at our Transparent Proxying guide.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Article is closed for comments.