Custom DNS not working over OpenVPN (2.27, AR300M)

martingerdes · 2018-09-07T06:10:33.042Z

I have bought a 300M Mini Smart Router (Model: GL-AR300M16-ext) a few days ago, with the idea to use it to provide openVPN to a few devices, so as to not have to fight setting that up on each of them.

I have got the OpenVPN itself working (getting the password for the key stored was a bit tricky).
What is not yet working is using the DNS Server over the VPN.

The DNS Server behind the VPN has the IP 192.168.0.254
If I am connected with the VPN over the Smart Router, and then locally do
“nslookup .local 192.168.0.254” I can resolve the DNS name (which only the VPN DNS Server knows), so obviously the VPN works, the IP is correct, and no firewall is interrupting me.

However, as soon as I set under Settings/Internet Settings/Internet Settings/DNS Settings
“DNS Server 1” to the value 192.168.0.254 and tick “Force all clients to use”
no resolution of DNS names works anymore.

I tried setting 8.8.8.8 there and leaving “Force all clients to use” ticked, and that worked. So its obviously only a problem if the IP is behind the VPN. Maybe a routing problem in the router?

One of the first things I tried to do is updating the Firmware to 2.27, which is the newest one.
I found the thread Can't use my internal DNS over OpenVPN with GL-AR300M with 2.27 firmware - #17 by alzhao
which seems to run into the same problem.

That thread contains the suggestion to use the 3.0 firmware beta, but that does not appear to exist for ar300m yet:
http://download.gl-inet.com/firmware/ar300m/nand/clean/ → offers 2.264

Where am I going wrong?
Help?

alzhao · 2018-09-07T08:15:59.379Z

Can you actually ping the DNS server when the VPN is on?

martingerdes · 2018-09-07T09:16:34.485Z

Yes, I can. “ping 192.168.0.254” works.

As I wrote, I can even get DNS Answers from it.
“nslookup somehost.local 192.168.0.254” goes over the VPN as established by the 300M device, and gets the correct answer. (Command executed on my linux desktop, not on the router)

martingerdes · 2018-09-13T08:07:25.691Z

Does nobody have any idea what is going on?

Is there any more information from my side I could provide to help figure this out?
Any hints would be much appreciated!

glitch · 2018-09-13T11:12:31.598Z

No idea what’s “going on” but why do you use 192.168.0.254? That looks like a local address, anyway.
Try cloudfare’s, DNS 1.1.1.1.

martingerdes · 2018-09-13T12:32:50.096Z

You misunderstand what I am trying to do:
192.168.0.254 IS a local adress, on the other side of the VPN.
It will only resolve if the VPN is up, which it is.
And from everything I understood, the device should be able to route the DNS traffic to a DNS Server sitting inside of the VPN I am connected to. Am I mistaken in that?

I can not just use a public DNS Server because I want to resolve DNS entries only that private DNS Server knows about.

kingwilliam · 2018-09-22T14:20:05.299Z

May be below link can solve your problem

AR750 as OpenVPN client, no DNS for far network Technical Support for Routers

Hi All I do have AR750 configured as OpenVPN client, which I’m using when traveling. My home router act as OpenVPN server, where I have terminated other two stationary routers. So far so good, in server config I’m “pushing” my internal domain with internal DNS server IP. And it works for other two routers, or OpenVPN software. It doesn’t for AR750, when trying to resolve address which is in my home network, AR750 instead asking through tunnel, goes via internet (I do have split-dns). How I can …