GL-MT6000 Flint 2 4.6.8 - Dynamic DNS Will Not Work when Using Weak Password

Just sharing what appears to be an undocumented issue I ran into when configuring a new Flint 2 for Dynamic DNS. Per the GUI instructions, I confirmed my external IP address is public, then I enabled Dynamic DNS using the GUI. The DDNS Test results showed an empty IP address, and using "nslookup" also confirmed there was no IP address assigned to my assigned domain name. Reviewing to the System log in the LUCI GUI, I was seeing a message from the DDNS task stating it was unable to add an IP address each time I ran the DDNS Test..

After several hours of trial and error, I figured out that the issue was due to disabling the "Prevent Weak Password" security option in the router via the Security section of the GUI. After first changing the router admin password to something that matched the complex password rules, I then re-enabled "Prevent Weak Password" and finally disabled and re-enabled DDNS. The DDNS Test passed after a couple of tries, and my IP address was shown as expected.

Hope this saves others some effort if they run into this one. It would be very helpful to add this to the documentation web pages as well.

1 Like

It may be related to the recent issue encountered with GL DDNS service (issue in server side).

GL firmware does not restrict weak passwords that refuses to report/update IP to DDNS server.

The above issues on the GL DDNS server side have been fixed.
If the GL DDNS of the client in GL router encounters similar issue, such as the IP has not been updated or reported, please manually re-enable GL DDNS in GL GUI.

Thank you.

2 Likes

My apologies. You are correct. I tested again today after going back to the weak password enabled setting, and DDNS Test now resolves to my public IP address as expected. I should have considered the DDNS server could have been down, and did not. Sorry to all for the confusion.

That is ok.
Since the GL DDNS server issue, to cause this misunderstand for the router password, that is our issue, but now the GL DDNS server work well, please do not worry.