DDNS not working properly

[redblack]

Hi Guys,

I just received my new Flint3, and happily set it up, yet the DDNS service is not working properly, showing no IP binded, could some one help please?

[alen5193]

Hi there:

1. Check WAN IP: Make sure it’s public (not 192.168.x.x).

2. Verify DDNS Settings:
   

   

3. Try to reconfigure and enable DDNS, then export the log for analysis

Let me know your WAN IP type and log errors and the router's version.

[JeffAu]

Same here for my flint 3...

[JeffAu]

[redblack]

mine is DHCP , WanIP for sure.
i can use it directly by copying the IP address to wireguard server config file.
rebooted 4 times.
logread.tar (284.5 KB)

[harryttl]

Hi all,

My flint 3 also facing the same, tried to reboot and amending command in ssh per another thread mentioned, but still no luck. Attached my log here, thanks.
logread.tar (356.5 KB)

[bruce]

Hi,

Please SSH to the router, and try to execute this command to check:

lua /usr/lib/gl_ddns/get_ddns_post_cmd.lua | sh

[harryttl]

Hi Bruce,

Tried to do so with a power recycle, but still no luck...

logread-2.tar (220.5 KB)

[bruce]

The syslog recorded only WI-FI information, and only 16 lines.

Please SSH to the router, and execute this command to check:
lua /usr/lib/gl_ddns/get_ddns_post_cmd.lua | sh

Please post the result here.

[redblack]

Chatgpt told me.
Your router is stuck using an expired or broken DDNS token, and the Web UI refuses to regenerate it even after toggling DDNS.

i've tried to disable and re-enable, i've tried to delete
uci delete gl_ddns.glddns
uci commit gl_ddns
nothing changed
新建 テキスト ドキュメント.tar (3.5 KB)

[redblack]

root@GL-BE9300:~# lua /usr/lib/gl_ddns/get_ddns_post_cmd.lua | sh
badauthroot@GL-BE9300:~#
root@GL-BE9300:~#

here is Chatgpt Final Diagnosis:

• Your DDNS hostname: valid (dc2c79a.glddns.com)
• Your router’s IP: correct
• Your password/token: invalid (expired or revoked)

[redblack]

Hello,

I'm using a GL.iNet Flint 3 (GL-BE9300) router. After resetting the router, the DDNS domain dc2c79a.glddns.com is still bound to my router and returns badauth. Even after factory reset, the token 5ee96a3bb15b04d2 remains the same and no new domain or token is issued.

Please help reset my DDNS domain or assign a new one, so I can continue using GL.iNet DDNS features.

Thank you,

[skatzone]

Hi Guys,

I have the same problem with the DDNS, but on the Slate Plus. The problem has only been occurring for about 3 months. Before that it worked for a very long time without any problems. There were no changes to the network, apart from the regular FW updates (Stable)

If I activate DDNS, the service works for approx. 12-24 hours, after which it no longer works and I can only access the WAN IP directly via VPN.

If I deactivate DDNS on the router and reactivate it or switch it on again and confirm the terms of use, DDNS access works again for the above-mentioned time.

It seems to me that the problem here is not the Gl.inet DDNS service, but rather a problem in the firmware. The service itself is available.

I also have the same problem with the GL-AR300M16-Ext.

I have not yet tested it on my Opal 1200.

Perhaps my observation will help.

[harryttl]

Hi Bruce,
After I entered this command, no output shown...

[redblack]

It shows bad authentication.. same as mkne

[bruce]

@redblack @harryttl
Please PM me your router MAC address, SN, device ID.

@skatzone Please PM me the issue syslog including DDNS.

[redblack]

how to send PM please? i dont see an msg box. thanks

[bruce]

Hi,

Your issue is already being processed by colleagues.

Please try to re-enable DDNS later.

[harryttl]

PMed you