AX 1800 client vpn router DNS stops responding

Technical Support for Routers
1

I have 2 ax 1800 routers setup (3 actually; 2 wireguard servers and 1 client)

What happens is the client vpn router will work fine for a while and after a few hours DNS stops working for the clients connected to the router.

If I restart the router or disable the kill switch DNS is resolved.

I have tried a few things that I searched on the forum but nothing seems to fix it.

So usually everyday after a few hours the DNS stops resolving and I have to connect my devices to my other ISP router.

I am using wireguard, and cannot afford to not have the vpn kill switch disabled and exposing my real IP.

2

what firmware version do you use? Can you provide the full log? you can export log in system->log->export

3

firmware 4.1
attached is the log export. It just happened after a few hours being on.
From what I see it tried to renew something and then trays to keep using my ISP DNS.

Mon Apr 24 14:39:28 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=KEYPAIR-CREATED SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Mon Apr 24 14:39:36 2023 daemon.notice netifd: wan (7414): udhcpc: sending renew to 192.168.0.1
Mon Apr 24 14:39:36 2023 daemon.notice netifd: wan (7414): udhcpc: lease of 192.168.0.128 obtained, lease time 86400
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: using only locally-known addresses for domain test
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: using only locally-known addresses for domain onion
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: using only locally-known addresses for domain localhost
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: using only locally-known addresses for domain local
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: using only locally-known addresses for domain invalid
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: using only locally-known addresses for domain bind
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: using only locally-known addresses for domain lan
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: using nameserver 177.200.64.2#53
Mon Apr 24 14:39:36 2023 daemon.info dnsmasq[10714]: using nameserver 177.200.64.3#53
Mon Apr 24 14:41:28 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=KEYPAIR-CREATED SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Mon Apr 24 14:42:52 2023 user.err ddns-scripts[8677]: glddns: BusyBox nslookup error: '1'
Mon Apr 24 14:42:52 2023 user.warn ddns-scripts[8677]: glddns: Get registered/public IP for 'bj9c3a5.glddns.com' failed - retry 1/0 in 60 seconds
Mon Apr 24 14:43:29 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=KEYPAIR-CREATED SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Mon Apr 24 14:44:02 2023 user.err ddns-scripts[8677]: glddns: BusyBox nslookup error: '1'
Mon Apr 24 14:44:02 2023 user.warn ddns-scripts[8677]: glddns: Get registered/public IP for 'bj9c3a5.glddns.com' failed - retry 2/0 in 60 seconds
Mon Apr 24 14:45:12 2023 user.err ddns-scripts[8677]: glddns: BusyBox nslookup error: '1'
Mon Apr 24 14:45:12 2023 user.warn ddns-scripts[8677]: glddns: Get registered/public IP for 'bj9c3a5.glddns.com' failed - retry 3/0 in 60 seconds
Mon Apr 24 14:45:29 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=KEYPAIR-CREATED SHLVL=2 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/
Mon Apr 24 14:46:22 2023 user.err ddns-scripts[8677]: glddns: BusyBox nslookup error: '1'
Mon Apr 24 14:46:22 2023 user.warn ddns-scripts[8677]: glddns: Get registered/public IP for 'bj9c3a5.glddns.com' failed - retry 4/0 in 60 seconds
4

Please try to upgrade to the latest version 4.2.1.

5

updated ti 4.2.1 on both servers and client and DNS still stops working after a few hours.

1 Like