WireGuard with DDNS not working on AXT 1800 after upgrade to version 4.7.0

Routers VPN, DNS, Leaks
1

Hi, for some reason, if I configure the DDNS on the AXT1800 client, it does not connect to the WireGuard server. If you ping the DDNS it can resolve the same IP address, I also tried with other DDNS I use in the server workplace and is the same result.

I can connect with my phone WireGuard client with no problem using the DDNS.

Below you can see the log, first I connected configuring the server IP address, later I turn off, configure the DDNS of the server (that works on the WireGuard from my phone and was working before this update), and it stays on that loop.

This is a know bug of this version?
Please let me know if any more information is needed to check this out.

Sun May 18 10:53:10 2025 daemon.notice netifd: Interface 'wgclient' is now up
Sun May 18 10:53:10 2025 user.notice wgclient-up: env value:T_J_V_ifname=string J_V_address_external=1 USER=root ifname=wgclient ACTION=KEYPAIR-CREATED N_J_V_address_external=address-external SHLVL=2 J_V_keep=1 HOME=/ HOTPLUG_TYPE=wireguard T_J_V_interface=string J_V_ifname=wgclient T_J_V_link_up=boolean LOGNAME=root DEVICENAME= T_J_V_action=int TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin CONFIG_LIST_STATE= J_V_interface=wgclient K_J_V= action ifname link_up address_external keep interface J_V_link_up=1 J_V_action=0 T_J_V_address_external=boolean N_J_V_link_up=link-up T_J_V_keep=boolean PWD=/ JSON_CUR=J_V CONFIG_SECTIONS=global AzireVPN Mullvad FromApp group_3002 group_2320 group_5287 group_3505 peer_5449 peer_7183 peer_6891 peer_1366 PIA Surfshark NordVPN Hideme IPVanish group_6495 group_9462 group_8780 group_1747 group_4714 peer_2005 peer_7896 CONFIG_cfg030f15_ports=
Sun May 18 10:53:10 2025 user.notice firewall: Reloading firewall due to ifup of wgclient (wgclient)
Sun May 18 10:54:30 2025 daemon.notice netifd: Network device 'wgclient' link is down
Sun May 18 10:54:30 2025 daemon.notice netifd: Interface 'wgclient' is now down
Sun May 18 10:54:31 2025 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Sun May 18 10:54:40 2025 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun May 18 10:54:40 2025 user.notice root: disable GRO on wgclient
Sun May 18 10:54:45 2025 daemon.notice netifd: wgclient (14791): Try again: ksxxxxx.glddns.com:51820'. Trying again in 1.00 seconds... Sun May 18 10:54:51 2025 daemon.notice netifd: wgclient (14791): Try again: ksxxxxx.glddns.com:51820'. Trying again in 1.20 seconds...
Sun May 18 10:54:57 2025 daemon.notice netifd: wgclient (14791): Try again: ksxxxxx.glddns.com:51820'. Trying again in 1.44 seconds... Sun May 18 10:55:04 2025 daemon.notice netifd: wgclient (14791): Try again: ksxxxxx.glddns.com:51820'. Trying again in 1.73 seconds...
Sun May 18 10:55:05 2025 daemon.notice netifd: Interface 'wgclient' is now down

2

Hi,

Thanks for your feedback, I would like to know more about this issue:

  1. May I know what is the router model and firmware which is the WireGuard VPN server?

  2. Confirm that ping <ddns_domain_name>, result the resolved IP, is same as the WAN IP of the VPN server router?

  1. May I know Does the VPN server router have VPN client enabled?
4
  1. Same version * 4.7.0 * Firmware Typerelease8
  2. Yes, it resolves the IP but don't reply because the port 80 is not answering there.
  3. It's enable only the Wireguard and OpenVPN server (not in use)
5

Could you please share the network topology image? Since I did not reproduce this issue on my AXT1800.

If AXT1800 enable DDNS, then its WG client cannot connect to another one router WG server, right?

What is the router model which is WG server? Is it GL router?

6

Hi, how can I share the topology image?

Server AXT1800 is with DDNS enable, no Client, only Wg server.

AXT1800 client, have no Wg server or ddns enable.

AXT1800 client can not connect when using the DDNS from the AXT1800 server, only with the direct IP.

7

Hi,

  1. Topology diagrams can be written by hand or online topology diagram websites. After editing, the screenshot can be posted here.

  2. You can get in Client AXT1800 ping <ddns_domain_name> is the Server AXT1800 WAN IP, right? it is weird, would you mind sharing your Server and Client AXT1800 for us to check via GoodCloud?
    Technical Support via GoodCloud - GL.iNet Router Docs 4

Please let me know the 2* AXT1800 MAC address and Web UI password.