# DNS is not resolving from VPN (Wireguard and OpenVPN) on Slate AX GL-AXT1800 **URL:** \ **Category:** VPN, DNS, Leaks\ **Tags:** KB\ **Created:** [August 4, 2024, 12:55pm UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573 "2024-08-04T12:55:55Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![hexx1746](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/ed655f/32.png) [@hexx1746](https://forum.gl-inet.com/u/hexx1746)\ **Post date:** [August 4, 2024, 12:55pm UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/1 "2024-08-04T12:55:55Z")
DNS is not resolving from VPN (Wireguard and OpenVPN) on Slate AX GL-AXT1800 Connecting to personal pfsense and running it with DNS resolver. Have been able to run it well with Android, Windows and Asus routers. Clients behind Asus routers will resolve without issues. Tried forcing client DNS to the required IP but I still cannot get it to resolve my custom hosts. One workaround I managed to do is to edit the hosts file on the Slate AX. Any suggestions so I do not need to rely on the hosts file? ---
**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\ **Post date:** [August 5, 2024, 2:29am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/2 "2024-08-05T02:29:50Z")
1. Have the configuration setup the custom DNS? and the DNS is your personal pfsense? 2. Mode: Automatic, will use VPN DNS first. ---
**Author:** ![hexx1746](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/ed655f/32.png) [@hexx1746](https://forum.gl-inet.com/u/hexx1746)\ **Post date:** [August 5, 2024, 6:10am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/3 "2024-08-05T06:10:46Z")
Hi Bruce, in short yes. my configuration for the Wireguard and OpenVPN clients are both pointing to the personal ip for DNS. Not different from how I have setup on an Asus router prior and the clients are able to get the resolves from the private DNS. Difference only being the keys. also, the Slate AX is on firmware 4.6.2 release2. I am able to have the clients establish a direct VPN connection and it works as expected but I hope to be able to make use of the Slate AX wireguard client to establish the tunnel for all connected clients. ---
**Author:** ![FrequentFlyer](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/f/d26b3c/32.png) [@FrequentFlyer](https://forum.gl-inet.com/u/FrequentFlyer)\ **Post date:** [August 5, 2024, 8:28am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/4 "2024-08-05T08:28:53Z")
Hi everyone, I received my Slate AX on Saturday and have exactly the same problem. I'm using WireGuard to establish a connection to my pfSense, but DNS isn't working. The tunnel itself is stable and pings go through in both directions. ---
**Author:** ![admon](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/admon/32/32880_2.png) [@admon](https://forum.gl-inet.com/u/admon)\ **Post date:** [August 5, 2024, 8:29am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/5 "2024-08-05T08:29:26Z")
If you test DNS from router against your pfSense, does it work then? ---
**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\ **Post date:** [August 5, 2024, 8:39am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/6 "2024-08-05T08:39:56Z")
> [@hexx1746](#): > > One workaround I managed to do is to edit the hosts file on the Slate AX. Do you mean the local dns names or all dns names? ---
**Author:** ![bruce](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/bruce/32/35649_2.png) [@bruce](https://forum.gl-inet.com/u/bruce)\ **Post date:** [August 5, 2024, 8:51am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/7 "2024-08-05T08:51:01Z")
May I know if this topology in my understanding is right? VPN Server & DNS Server: pfsense VPN Client: Android/Windows/Routers pfsense (VPN Server & DNS Server) —— ISP Modem —— Internet —— VPN Client ---
**Author:** ![FrequentFlyer](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/f/d26b3c/32.png) [@FrequentFlyer](https://forum.gl-inet.com/u/FrequentFlyer)\ **Post date:** [August 5, 2024, 12:34pm UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/8 "2024-08-05T12:34:13Z")
It seems to be working now. I created an entry in **Advanced Settings** under **DHCP and DNS** under **DNS forwardings** that forwards my "mylocaldomain.local" to my pfSense DNS resolver. Along with many other settings that I tinkered with, that seems to have been the decisive step. My planned setup is as follows: (GL-AXT1800) \<-\> (Hotel WIFI) \<-\> (WireGuard) \<-\> (pfSense) \<-\> (Local Services and Internet Breakout) My current test setup: (GL-AXT1800) \<-\> (WireGuard) \<-\> (pfSense) \<-\> (Local Services and Internet Breakout) ![grafik](https://forum-static.gl-inet.com/original/3X/9/3/93aed76a96e649374bb4cffd99e2d72ee3e85a53.png) ---
**Author:** ![hexx1746](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/ed655f/32.png) [@hexx1746](https://forum.gl-inet.com/u/hexx1746)\ **Post date:** [August 5, 2024, 2:19pm UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/9 "2024-08-05T14:19:31Z")
Here is the output from LuCI -\> Network -\> Diagnostics -\> Nslookup > Server: 127.0.0.1 > Address: 127.0.0.1#53 > > \*\* server can't find xyz.mydomain.lan: NXDOMAIN > \*\* server can't find xyz.mydomain.lan: NXDOMAIN ---
**Author:** ![hexx1746](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/ed655f/32.png) [@hexx1746](https://forum.gl-inet.com/u/hexx1746)\ **Post date:** [August 5, 2024, 2:22pm UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/10 "2024-08-05T14:22:37Z")
The VPN works so all IP address is reachable just the local names are not being resolved from the pfsense. So what I did was recreate the list of IPs and names in Slate -\> Network -\> DNS -\> Edit Hosts. @bruce, yes the typology is correct. I have been successful with having clients directed to the correct IPs through a similar setup with Asus Routers so I am sure it works. private servers -- pfsense (VPN + DNS) -- ISP Modem -- WAN -- _ **ISP Modem** _ -- _ **Asus Router** _ (VPN Client) -- clients In the case of what I want to do is for the clients connecting to Slate AX (instead of the Asus Router) to be able to resolve the host names of my private servers private servers -- pfsense (VPN + DNS) -- ISP Modem -- WAN -- _ **public wifi** _ -- _ **Slate AX** _ (VPN Client) -- clients @FrequentFlyer, I tried tinkering a lot of settings but failed to resolve it. I tried the similar under LuCI -\> Network -\> DHCP and NDS -\> DNS forwardings -\> **/mydomain.lan/_ipaddress_** but that did not work for me. What other settings do you think made a difference? ---
**Author:** ![alzhao](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/a/5f9b8f/32.png) [@alzhao](https://forum.gl-inet.com/u/alzhao)\ **Post date:** [August 5, 2024, 3:02pm UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/11 "2024-08-05T15:02:39Z")
What is the domain name? if it is “mydomain” pls change it to “mydomain.lan” and check. ---
**Author:** ![teleney](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/t/3be4f8/32.png) [@teleney](https://forum.gl-inet.com/u/teleney)\ **Post date:** [August 6, 2024, 2:18am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/12 "2024-08-06T02:18:56Z")
![image](https://forum-static.gl-inet.com/original/3X/7/7/7763c2ba4f8c423a260146f7afb8bfe40ebd83af.png) Have you enabled this option? If enabled, DNS reply messages from non-external networks will be blocked. path：NETWORK -\> DNS -\> DNS Rebinding Attack Protection. ---
**Author:** ![hexx1746](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/ed655f/32.png) [@hexx1746](https://forum.gl-inet.com/u/hexx1746)\ **Post date:** [August 6, 2024, 3:09am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/13 "2024-08-06T03:09:06Z")
Hi @alzhao, yes I am already using "hexx.lan" @teleney, I have the DNS settings exactly as your image, all off, and Mode -\> Automatic ---
**Author:** ![hansome](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/b5ac83/32.png) [@hansome](https://forum.gl-inet.com/u/hansome)\ **Post date:** [August 6, 2024, 8:45am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/14 "2024-08-06T08:45:34Z")
For .lan dns query to pass dnsmasq, please try copy and run the following command, ```auto uci set dhcp.@dnsmasq[0].local='/lan_chgd/' uci commit dhcp # restart dnsmasq /etc/init.d/dnsmasq restart # restart vpn dnsmasq . /usr/bin/route_policy handle_dns ``` ---
**Author:** ![hexx1746](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/ed655f/32.png) [@hexx1746](https://forum.gl-inet.com/u/hexx1746)\ **Post date:** [August 6, 2024, 9:40am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/15 "2024-08-06T09:40:53Z")
@hansome, that resolved it. Thank you. I had previously deleted Local server DHCP instead of changing it. Since my internal domain used .lan, looks like all I needed to change was LuCI -\> Network -\> DHCP and DNS -\> Local server -\> _ **/lan/** _ LuCI -\> Network -\> DHCP and DNS -\> Local server -\> _ **/lan\_chgd/** _ Do not need to add DNS forwardings. ---
**Author:** ![hexx1746](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/ed655f/32.png) [@hexx1746](https://forum.gl-inet.com/u/hexx1746)\ **Post date:** [August 8, 2024, 4:52pm UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/16 "2024-08-08T16:52:10Z")
@hansome, spoke too soon. Still having issues now that I'm traveling. Hard to troubleshoot now so resulting in individual VPN directly on each client ---
**Author:** ![hexx1746](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/ed655f/32.png) [@hexx1746](https://forum.gl-inet.com/u/hexx1746)\ **Post date:** [August 10, 2024, 4:22pm UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/17 "2024-08-10T16:22:23Z")
LuCI -\> Network -\> Diagnostics -\> nslookup Results in ;; connection timed out; no servers could be reached ---
**Author:** ![hansome](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/b5ac83/32.png) [@hansome](https://forum.gl-inet.com/u/hansome)\ **Post date:** [August 12, 2024, 4:25pm UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/18 "2024-08-12T16:25:24Z")
Sorry I missed a part setting of VPN dnsmasq: The updated full command is: ```auto # set dnsmasq uci set dhcp.@dnsmasq[0].local='/lan_chgd/' uci commit dhcp # restart dnsmasq /etc/init.d/dnsmasq restart # set VPN dnsmasq sed -i 's/local=\/lan/local=\/lan_chgd/' /etc/dnsmasq.conf.vpn # restart vpn dnsmasq . /usr/bin/route_policy handle_dns ``` ---
**Author:** ![hexx1746](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/ed655f/32.png) [@hexx1746](https://forum.gl-inet.com/u/hexx1746)\ **Post date:** [August 26, 2024, 8:23am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/19 "2024-08-26T08:23:52Z")
I have mixed success with this. Looks like it is working using OpenVPN but I cannot get it to work using WireGuard, which is the preferred method for performance. Here are the commands I have run to configure > uci set dhcp.@dnsmasq[0].local='/lan\_chgd/' > uci commit dhcp > /etc/init.d/dnsmasq restart > sed -i 's/local=/lan/local=/lan\_chgd/' /etc/dnsmasq.conf.vpn I believe this is the correct command > /usr/bin/route\_policy handle\_dns This command forced SSH to exit > . /usr/bin/route\_policy and this is an unknown command > handle\_dns nslookup from client resolves correctly but through LuCI console responds with this error message > ;; connection timed out; no servers could be reached ---
**Author:** ![hansome](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/b5ac83/32.png) [@hansome](https://forum.gl-inet.com/u/hansome)\ **Post date:** [August 27, 2024, 1:21am UTC](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573/20 "2024-08-27T01:21:53Z")
Please export log for analysis. [Next page](https://forum.gl-inet.com/t/dns-is-not-resolving-from-vpn-wireguard-and-openvpn-on-slate-ax-gl-axt1800/45573.md?page=2)