Configure a DNS Proxy Object
If your firewall is to act as a DNS proxy, perform this task to configure a DNS Proxy Object. The proxy object can either be shared among all virtual systems or applied to a specific virtual system.
When the firewall is enabled to act as a DNS proxy, evasion signatures that detected crafted HTTP or TLS requests can alert to instances where a client connects to a domain other than the domains specified in the original DNS query. As a best practice, Enable Evasion Signatures after configuring DNS proxy to trigger an alert if crafted requests are detected.
- Configure the basic settings for a DNS Proxy object.
- SelectandNetworkDNS ProxyAdda new object.
- Verify thatEnableis selected.
- Enter aNamefor the object.
- ForLocation, select the virtual system to which the object applies. If you selectShared, you must specify at least aPrimaryDNS server address, and optionally aSecondaryaddress.
- If you selected a virtual system, forServer Profile, select a DNS Server profile or else clickDNS Server Profileto configure a new profile. See Configure a DNS Server Profile.
- For Inheritance Source, select a source from which to inherit default DNS server settings. The default isNone.
- ForInterface, clickAddand specify the interfaces to which the DNS Proxy object applies.
- If you use the DNS Proxy object for performing DNS lookups, an interface is required. The firewall will listen for DNS requests on this interface, and then proxy them.
- If you use the DNS Proxy object for a service route, the interface is optional.
- (Optional) Specify DNS Proxy rules.
- On theDNS Proxy Rulestab,AddaNamefor the rule.
- Turn on caching of domains resolved by this mappingif you want the firewall to cache the resolved domains.
- ForDomain Name,Addone or more domains, one entry per row, to which the firewall compares FQDN queries. If a query matches one of the domains in the rule, the query is sent to one of the following servers to be resolved (depending on what you configured in the prior step):
DNS Proxy Rule and FQDN Matching describes how the firewall matches domain names in an FQDN to a DNS proxy rule. If no match is found, default DNS servers resolve the query.
- ThePrimaryorSecondaryDNS Server directly specified for this proxy object.
- ThePrimaryorSecondaryDNS Server specified in the DNS Server profile for this proxy object.
- Do one of the following, depending on what you set theLocationto:
- If you chose a virtual system, select aDNS Server profile.
- If you choseShared, enter aPrimaryand optionally aSecondaryaddress.
- (Optional) Supply the DNS Proxy with static FQDN-to-address entries. Static DNS entries allow the firewall to resolve the FQDN to an IP address without sending a query to the DNS server.
- On theStatic Entriestab,AddaName.
- Enter the Fully Qualified Domain Name (FQDN).
- ForAddress,Addthe IP address to which the FQDN should be mapped.You can provide additional IP addresses for an entry. The firewall will provide all of the IP addresses in its DNS response and the client chooses which address to use.
- (Optional) Enable caching and configure other advanced settings for the DNS Proxy.
- On theAdvancedtab, selectTCP Queriesto enable DNS queries using TCP.
- Max Pending Requests—Enter the maximum number of concurrent, pending TCP DNS requests that the firewall will support (range is 64-256; default is 64).
- ForUDP Queries Retries, enter:
- Interval (sec)—The length of time (in seconds) after which another request is sent if no response has been received (range is 1-30; default is 2).
- Attempts—The maximum number of UDP query attempts (excluding the first attempt) after which the next DNS server is queried (range is 1-30; default is 5.)
- SelectCacheto enable the firewall to cache FQDN-to-address mappings that it learns.
- SelectEnable TTLto limit the length of time the firewall caches DNS resolution entries for the proxy object. Disabled by default.
- EnterTime to Live (sec), the number of seconds after which all cached entries for the proxy object are removed. After the entries are removed, new DNS requests must be resolved and cached again. Range is 60-86,400. There is no default TTL; entries remain until the firewall runs out of cache memory.
- Cache EDNS Responses—Select this if you want the firewall to cache partial DNS responses that are greater than 512 bytes. If a subsequent FQDN for a cached entry arrives, the firewall sends the partial DNS response. If you want full DNS responses (greater than 512 bytes), don’t select this option.
- Commit your changes.ClickOKandCommit.
Recommended For You
Recommended videos not found.