- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
incongruence dns set in ssl portal with those present on forticlient clients
Hello everyone,
i am writing to you because we have a strange problem about the dns of the vpn ssl. In the menu SSL-vpn setting we have specified the following dns to use: 172.1.1.20 - 172.1.1.30, unfortunately we have noticed that all the clients connected through forticlient inherit completely different dns, that is: 172.1.10.50 - 172.1.10.60. is there a way to understand why they take different dns although we are configured explicitly in the portal?
dns configuration in attachment, do i need to open a case or do i have do control something more specific?
Regards
Solved! Go to Solution.
- Labels:
-
6.2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You could verify there is not a per portal dns server set in the cli:
https://community.fortinet.com/t5/FortiGate/Technical-Tip-Configuring-DNS-servers-per-SSL-VPN-Portal...
if not you will probably need to open a case to verify the full configuration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You could verify there is not a per portal dns server set in the cli:
https://community.fortinet.com/t5/FortiGate/Technical-Tip-Configuring-DNS-servers-per-SSL-VPN-Portal...
if not you will probably need to open a case to verify the full configuration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
it was exactly the issue!
Thank you
Bye
