Optional Services
DNS Proxy
original DNS server (destination IP) of the query is. For the case that a provider only deploy their servers in one ISP
network, DNS Proxy is helpless to resolve the congestion resulted from the usage of Optimum Route for resolving ISP
peering issue.
DNS Proxy redirects a DNS request sent from LAN or DMZ to the external DNS servers with better response time.
There are two phases included in the DNS Proxy, auto routing among multiple WAN links and redirecting a DNS
request to the DNS servers specified on the WAN link. Usually, the DNS servers specified on the WAN link are located
in the ISP’s network which the WAN link connects to. Therefore, DNS Proxy routes a DNS request to a WAN link with
the best quality and sends it to the DNS servers specified on the WAN link whatever the original destination is.
Enable DNS Proxy
Turn on/off DNS Proxy.
Algorithm
4 algorithms for routing (See "
Load Balancing & Fault Tolerance
"):
l
By Weight: route the connections on every WAN link by weight.
l
By Down Stream: always route the connection to the WAN link that has the lightest
downstream traffic.
l
By Up Stream: always routes the connection to the WAN link that has the lightest
upstream traffic.
l
By Total Traffic: always route the connection to the WAN link that has the lightest
total traffic.
WAN
Select the WAN links for specifying DNS servers and weight.
Weight
Give a weight on each WAN link. This field is visible when By Weight is selected in
Algorithm.
Server 1
Specify the first DNS server on the WAN link.
Server 2
Specify the second DNS server on the WAN link. This is an optional.
Server 3
Specify the third DNS server on the WAN link. This is an optional.
Source
Connections established from the specified source will be matched. Keep it blank
for any source.
Domain Name
DNS requests for the specified domain name will be matched. A wildcard
character is accepted for the left-most label of a domain name, e.g.
*.fortinet.com
or
*fortinet.com
.
Note that other formats such as
www.*.com
,
www.fortinet.*
or
*.fortinet.*
are not
supported. Keep it blank for any domain name.
Make sure that Optimum Route Detect is appropriately configured, and corresponding Auto Routing (See "
") policy and filters are created for routing traffic by the algorithm: By Optimum Route. Without these
configurations, the basic peering issue does not get resolved, and DNS Proxy becomes meaningless for this.
242
FortiWAN Handbook
Fortinet Technologies Inc.