Created on
11-16-2023
12:02 AM
Edited on
01-23-2025
11:43 AM
By
HarshChavda
| Description | This article discusses the behavior of DNS zone database view type (public and shadow) for explicit proxy in FortiGate. |
| Scope | FortiGate. |
| Solution |
The DNS database view can be set as 'public' or 'shadow'. For explicit proxy sessions, FortiGate will do the DNS lookup into the DNS database with the view set as 'shadow'.
For example, FortiGate works as an explicit proxy. A secondary DNS zone database 'xxxx.yy.com' is created in FortiGate to receive zone database entries from the internal DNS server.
FGTTEST # show sys dns
FGTTEST # show sys dns-database xxxx.yy.com
With view setting as 'shadow':
dia de app dnsproxy -1 dia de en [worker 0] dns_local_lookup()-2529: vfid=0, real_vfid=0, qname=truckbus.xxxx.yy.com, qtype=1, qclass=1, offset=39, map#=4 max_sz=512
If the HTTP Request URL does not match the DNS database domain, FortiGate will do the lookup with the DNS server set in FortiGate:
[worker 0] dns_local_lookup()-2529: vfid=0, real_vfid=0, qname=login.microsoft.com, qtype=1, qclass=1, offset=37,map#=3 max_sz=131072
When the view setting is 'public':
[worker 0] dns_local_lookup()-2529: vfid=0, real_vfid=0, qname=truckbus.xxxx.yy.com, qtype=1, qclass=1, offset=39, map#=4 max_sz=512
[worker 0] dns_local_lookup()-2529: vfid=0, real_vfid=0, qname=safebrowsing.googleapis.com, qtype=1, qclass=1, of |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.