Skip to main content
Maerre
Explorer III
October 14, 2021
Solved

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

 

distillednetwork
Explorer II
February 23, 2023

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/ta-p/194780
if not you will probably need to open a case to verify the full configuration. 

2 replies

distillednetwork
Explorer II
February 23, 2023

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/ta-p/194780
if not you will probably need to open a case to verify the full configuration. 

Maerre
MaerreAuthor
Explorer III
June 15, 2023

Hello,

 

it was exactly the issue!

 

Thank you

Bye

Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT