How No-DNS Detection Works
Your enforcement point forwards a copy of DNS response data (IP address and TTL pairs) to the
Advanced IP Defense cloud service. The cloud service builds a DNS Seen Table
unique to your tenant that tracks every IP address resolved through DNS and when that
resolution expires.
When your enforcement point queries the cloud service about an IP address, the service checks
whether that IP appears in your tenant's DNS Seen Table with a valid (non-expired)
entry. If the IP has no DNS history or the entry has expired beyond a grace period,
the cloud service returns a No-DNS verdict. The grace period (currently 300 seconds)
accounts for transmission delays and clients that use slightly expired cache
entries.
No-DNS detection applies only to publicly routable IP addresses in outbound traffic.
All private IP ranges are allowlisted, so protocols that operate exclusively on
internal networks (such as DHCP, mDNS, and NetBIOS) do not trigger false positives.
Do not apply No-DNS rules to inbound traffic — direct-to-IP detection is designed
for outbound sessions where a client initiates a connection without resolving the
destination through DNS.