DNS resolution for OpenVPN cleints

GentleJoe

Are you accessing the hostname with the FQDN like printer.mydomain.com ?

chudak

@Gentle:

Are you accessing the hostname with the FQDN like printer.mydomain.com ?

i do now!!!!

seems working, thx a million !

GentleJoe

Great ! :)

chudak

@GentleJoe

Had to dig out this old post, but it's exactly the same issue, so hope can be resolved ...

I made a copy of my existing OpenVPN server and added a second one.
All same settings. But no matter what I do I can't get host names DNS resolutions on the second server !

Wonder WTH and how to troubleshoot it ?

chudak

Either I missing something or it's a bug in VPN sever setup

What else has to be set in order to pass host names to a VPN client?

Looking for experts...

dotdash

It's always worked for me with just the domain and the DNS servers specified. (No force cache update checked). What does ipconfig /all show on the TAP adapter client side?

chudak

@dotdash

I’m on iPhone OpenVPN client
Shows my tun ip

dotdash

@chudak said in DNS resolution for OpenVPN cleints:

I’m on iPhone OpenVPN client

Sorry, I've got nothing for that. I've only had to deal with the name resolution on Windows and Android devices.
Edit- the OpenVPN connect client (at least on Android) shows the domain and dns pulled in the connect log.

chudak

I think it would not matter what client.

In my case this is how I test. Connect to cellular network on iPhone, connect to VPN and ping host by name. And my 1st server works as expected, but the new server does not !!!

dotdash

@chudak said in DNS resolution for OpenVPN cleints:

my 1st server works as expected, but the new server does not !!!

This would seem to indicate a problem with the new server on the DNS server. If you're testing from the phone, maybe get an app that does nslookup or dig.

chudak

Well after lots of testing and trying here is why.

I had DNS Resolver options checked for:

'Enable Forwarding Mode'
'Use SSL/TLS for outgoing DNS Queries to Forwarding Servers'

Un-checking them and checking back fixed the problem!

I suspect that reboot will help as well, but I not very often reboot my router.

Hope maybe beneficial to somebody else.