Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Not applicable

SSL VPN DNS Error

Hi i made up a ssl vpn, it seems to work, but i can ping o rdp all servers only by ip, when i try to use FQDN ive got the following error name server is not reachable because of dns error i read FortiGate® SSL VPNs FortiOS™ Handbook 4.0 MR1 unsuccessfully can someboy help me? Francesco
7 REPLIES 7
cgofish23
New Contributor

Do you have your internal DNS servers set in the SSL VPN config? VPN -> SSL, select the Config tab, at the bottom you will see Advanced (DNS and WINS Servers)
Not applicable

Yes i do
rwpatterson
Valued Contributor III

You have to edit the FortiSSLVPN network adapter and add the DNS domain to the advanced section of TCP/IP. This needs to be done on each install. This cannot be pushed with the SSL VPN IP information.

Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com

Bob - self proclaimed posting junkie!See my Fortigate related scripts at: http://fortigate.camerabob.com
cgofish23
New Contributor

We have seen this on some installs and some work fine without it.... one of the things on my list to look into as to why some installs require it. I always assumed it was something with the configuration/security of the internal DNZ server. 1) Anyone have any insight on this? or 2) Anyone know of a way to automate adding the DNZ suffix into the FortiSSL adapter?
rwpatterson
Valued Contributor III

ORIGINAL: cgofish23 2) Anyone know of a way to automate adding the DNZ suffix into the FortiSSL adapter?
As far as I know, it can' t be done, as of yet...

Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com

Bob - self proclaimed posting junkie!See my Fortigate related scripts at: http://fortigate.camerabob.com
Not applicable

Solved!! Configured my internal Dns on Fortigate
RachelGomez123
Contributor

Go to the Properties of that connection and then further go to TCP/IP Properties. Click on Advanced and make sure that " Use default gateway on remote network" is unchecked. Click on OK and OK again and close the connection properties. Now, connect to the tunnel again and the problem should be resolved.

 

This may help you,

Rachel Gomez

Labels
Top Kudoed Authors