| Description | This article describes how to Implement FortiGate as a Local DNS server database. |
| Scope | FortiGate DNS feature. Version 6.4.10. |
| Solution |
Scenario: 1) FortiGate will be used as a local DNS server database.
2) Global DNS server will be used to resolve global domain.
Local domain name : 40gate.co.id DNS interface (port4) : 172.16.10.254
FortiGate DNS config: no firewall policy rule is required.
 
User testing:
Local DNS can successfully be resolved.
Global DNS can successfully be resolved.
DNS request process on FortiGate –-> for local entry, FortiGate will check its own database – cause FortiGate is aware of its local domain name.
'40gate.co.id'.
DNS cache: local entry database will not be cached.
Dumb DNS database.
Related documents: https://docs.fortinet.com/document/fortigate/6.2.0/cookbook/960561/fortigate-dns-server https://docs.fortinet.com/document/fortigate/6.2.0/cookbook/121810/using-a-fortigate-as-a-dns-server Technical Tip: Implement split DNS for Local and G... - Fortinet Community |
