Problem with ddns service

Routers
1

Hello,

I have the GL-AX1800 (Flint) router and I'm experiencing an issue with the DDNS service. Yesterday, I updated the router to the latest version 4.70, although I believe the problem existed before. When I log in, it says that the IP does not match the system IP, and when I perform an nslookup from a web service, it gives me an IP that is not mine. It's as if the router is not updating the IP. I have tried restarting the service from the web admin, turning the router off and on, but nothing works.

Is there any way to view the logs to get more information?

Thank you all very much.

2

I've been looking into the issue and I think it's due to the WireGuard client being enabled. The router is connected to another via WireGuard, and the IP address is coming from the other router. I've got MAC-based policies set up for device access,

The 'Services from GL.iNet Use VPN' option doesn't appear to be functioning as expected.

I also have AdGuard enabled, which seems to be causing additional issues, although I think it's a separate problem. With AdGuard enabled, I'm unable to update the firmware or packages, and when I access the router via SSH, I'm unable to ping external addresses. It's as if AdGuard is blocking all DNS requests from the router itself. However, all other clients seem to be working correctly.

Thank you

3

Hello,

I have more information, and I think the problem is related to the DNS and the Wireguard client connection.

When I run the Wireguard client, if I connect via SSH to the router and ping google.com, I see "ping: bad address 'google.es'". DDNS, package updates, and other router services don't work. The other clients on the LAN are working correctly; it's only the router that has issues. I think there be a problem with DNS configuration.

I configured the Wireguard client with VPN policies based on the client devices, and the Wireguard configuration file is as follows:

[Interface]
Address = 10.0.0.4/24
PrivateKey = 
DNS = 64.6.64.6
MTU = 1420

[Peer]
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = XXXXX.glddns.com:51820
PersistentKeepalive = 25
PublicKey =

I think the problem is with my router because the other clients are working correctly.

Any ideas?

Thanks

4

Hi,

About the DDNS IP issue, we are aware this on AXT1800 v4.7.0, here is the temp workaround, next firmware version will improve this issue.

  1. Download this file, and unzip it.
    gl_ddns.zip (539 Bytes)
  2. Upload the file "gl_ddns" to router AX1800/AXT1800 path "/root/" through WinSCP, and execute the commands on SSH:
mv /root/gl_ddns /etc/init.d/gl_ddns
chmod +x /etc/init.d/gl_ddns
/etc/init.d/gl_ddns restart
5

My router is GL-AX1800, not AXT1800. Can you confirm that I should try to execute the script on this model?

Thanks

Thanks

6

Finally, I was able to find the problem and a temporary solution. The issue is that the resolv.conf file has DNS entries that are not valid when the WireGuard client is enabled. When the client is disabled, everything works fine, but when it is enabled, the DNS resolution fails, causing the router's services to fail.

The solution is to modify the resolv.conf file with the correct configuration (127.0.0.1 to route through ADguard). The problem is that if I disable the client and re-enable it, the file gets overwritten and the DNS entries causing the failure reappear. I believe these DNS entries come from my ISP over PPPoE.

How can I modify the configuration so that the resolv.conf file does not get overwritten?

Thank you.

7

I run this script and now ddns is working fine.

Thanks.

8

Can you explain what this file is fixing. It appears that when a 1800 client is updated to 4.7.0 that Dynamic DNS is enabled on the client when it was not enabled on the previous versions of firmware. I can connect via IP to the wireguard server, but dynamic dns is failing on the wireguard client. The only update was to the client router. So is the issue on the client or the server?

9

Did you run the script on the client or server?

10

Hello,

I ran this script on the client router. My problem was that the DDNS update went through the VPN tunnel and updated with the IP of the other router. With the script, the update is now correct with my own IP.

11

Thanks for your update.

the same as AX1800 as your test.

12

DDNS will not be automatically enable if upgrading the firmware version.

May I know did you meet DDNS issue on your VPN server router?
If it also is AX1800/AXT1800 and installed v4.7.0 firmware, you need to follow the above guidelines to update gl_ddns if the AX1800/AXT1800 is as the VPN server router.