Hello all,
this request regards to DNS name resolution on the fortigate local only!
The configuration of the firewall was changed to per-VDOM dns, because FQDN objects in that vdom should be resolved by an external nameserver. But unfortunately this leads to problems with the resolution of configured firewall users. The fortigate needs to resolve names for the following purposes:
1. Names of local configured servers (LDAP, RADIUS, etc)
2. Names from configured FQDN policy objects
1. must be resolved from the internal nameserver
2. should be resolved from an external nameserver
Is there a way to fix this?
Version 6.2.2
Many thanks in advance. Regards, Hakan
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hi,
You can define the primary dns server as your internal nameserver, define the local domain name, and use as secondary an external DNS server:
Hi pa_iva, many thanks for your reply.
Yes, actually this works. I built this in a lab and did packet captures. The Fortigate is always asking both, the primary and secondary, regardless which domain is asked, and it will get an answer of one of both servers. But with this configuration I would loose the redundancy of the namservers. Means, if the primary fails, resolution of internal names would fail. Even if this works, I cannot implement this in our productive network.
Best regards, Hakan
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1712 | |
1093 | |
752 | |
447 | |
231 |
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 2024 Fortinet, Inc. All Rights Reserved.