Browse Docs
-
Introduction
-
Deployment
- Deployment via RMM
- Operating System Agent
- Deployment via GPO
- Deployment via Intune
- VDI and Remote Desktop Services (RDS)
- Windows Manual Deployment
- Mac MDM Deployment
- Mac Manual Deployment
- Network Deployment
- Secure Mobile Browser
- Bypass Option
- SaaS Restrictions
- Bookmark Manager
- Remote Uninstall
- Bulk Create Customers
-
Management
-
Integrations
-
Nexi AI
-
Policy Management
-
Secure Access (ZTBA, formerly ZTNA)
-
Auto Pilot
-
Training Videos
-
Questions & Answers
-
MSP Automation
-
Feature Requests
ONLINE DOCUMENTATION
|
||
Using with Cloudflare WARPIn this document
OverviewCloudflare WARP (part of Cloudflare One / Zero Trust) and DefensX can conflict when both are installed on the same device. Depending on the WARP configuration, this conflict can cause intermittent DNS failures and prevent WARP from establishing a stable connection. Symptoms
CauseWARP and DefensX both use kernel-level drivers to intercept and handle DNS traffic. When both drivers are active, they interfere with each other:
Whether the check succeeds depends on whether DefensX already has the answer cached. This is why the problem appears intermittently rather than consistently. ResolutionA full resolution requires configuring each product to exclude the other’s traffic, so that neither driver intercepts the other’s DNS queries. Contact DefensX Support for guidance on the exclusions required for your environment. WorkaroundConfigure WARP to run in Traffic only mode instead of Traffic and DNS mode. In this mode, WARP no longer intercepts DNS traffic, which removes the conflict with the DefensX driver.
|
||