I have installed the pritunl server on the one of my container inside the kubernetes cluster. Right now I'm using enterprise version with trial mode to test all functionalities. The problem which I'm trying to resolve is dns issue.

After connection to the server I have an access to the internal kubernetes network (10.0.4.0/24) but all internal domains like ip-10-0-4-11.eu-central-1.compute.internal are not resolved to the local ip even that dns server is set in the pritunl server. This issue doesn't occur inside of pritunl container.

From local

➜  ~ ping 10.0.4.11                                 
PING 10.0.4.11 (10.0.4.11) 56(84) bytes of data.
64 bytes from 10.0.4.11: icmp_seq=1 ttl=254 time=24.3 ms
64 bytes from 10.0.4.11: icmp_seq=2 ttl=254 time=24.3 ms
64 bytes from 10.0.4.11: icmp_seq=3 ttl=254 time=23.7 ms
64 bytes from 10.0.4.11: icmp_seq=4 ttl=254 time=22.7 ms

➜  ~ ping ip-10-0-4-11.eu-central-1.compute.internal
ping: ip-10-0-4-11.eu-central-1.compute.internal: Name or service not known

Has anyone ever encountered this problem?

Thanks for helping me, Kind regards

Edit:

I found a solution that DNS Search Domain must be set in the Pritunl server so I set it to the vpn.svc.cluster.local, svc.cluster.local, cluster.local, eu-central-1.compute.internal. It's the same configuration which is in the /etc/resolv.conf in the container.

now error message is different

➜  ~ ping ip-10-0-4-11.eu-central-1.compute.internal
ping: ip-10-0-4-11.eu-central-1.compute.internal: Temporary failure in name resolution