- Products
- Learn
- Local User Groups
- Partners
- More
The State of Ransomware Q1 2026
Key Trends and Their Impact
Good, Better, Best:
Prioritizing Defenses Against Credential Abuse
AI Security Masters E7:
How CPR Broke ChatGPT's Isolation and What It Means for You
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
CheckMates Go:
CheckMates Fest
I have a workaround for you that had been tested at a customers.
To achieve this, you can add the following commands into userScript file:
# cpwd_admin stop -name WSDNSD # cpwd_admin detach -name WSDNSD
No DNS queries will be sent when this is set - just test it on-the-fly using the commands on CLI!
This WSDNSD behaviour was internally considered a bug by R&D (WSDNS is used as DNS resolver when the appliance is used as a HTTP/HTTPS proxy and WSDNSD makes requests for smartAccel, but it does the same requests even if both HTTP/HTTPS proxy and smartAccel is not used/disabled), but i am not sure if this has already been fixed in current firmware...
The case in which this information has been collected was resolved by using internal objects in WebGUI - if you define FQDN objects as object something.com 8.8.8.8, no DNS request for this FQDN will be sent, but it will make more sense to disable WSDNSD than to define 935 internal objects here...
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY