Global Bypass List for MSPs with Configurable DNS Servers
Deon
As an MSP, we currently have the ability to set bypasses at the site level for various tools (e.g., Office 365, NinjaRMM, Huntress) to ensure specific traffic is routed to an alternate DNS resolver, such as Cloudflare. However, this process is cumbersome to manage across multiple sites.
A global "Bypass" list feature would allow us to specify bypasses at the MSP level, similar to how Allow/Block lists are managed, streamlining this process across all sub-organizations. This would significantly reduce the manual overhead of applying the same bypass rules to each site.
Additionally, we suggest making the global bypass list configurable with a custom DNS server, so any bypassed traffic could automatically be routed to a defined DNS server. Since bypassed traffic isn’t being filtered by DNSFilter, this would help reduce unnecessary DNS requests and improve overall efficiency.
Potential impact:
- Easier management of DNS bypass rules for MSPs with multiple clients/sites.
- Improved efficiency in handling traffic that doesn’t require DNSFilter’s filtering, potentially reducing the volume of DNS requests.
- Could open the possibility of moving to request-based billing models, as this feature would help control noisy traffic from tools or services that don’t need to be filtered.