When setting a manual update-interval for DynDNS, the router appears to send updates even if the public IP hasn't changed. This leads to unnecessary updates and can cause problems with services like No-IP, which softly require that updates are only sent when the IP actually changes—otherwise, users may hit rate limits or be flagged for abuse.
Suggested Improvements:
When update-interval is set, skip updates if the IP hasn’t changed.
This would align better with DDNS service expectations and reduce noise.
Add a CLI option to force update even if the IP is unchanged, for manual or scripted use.
This small change would make DDNS behavior more efficient and compliant with provider guidelines.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
Aleksandr D
Hi Keenetic team,
When setting a manual
update-intervalfor DynDNS, the router appears to send updates even if the public IP hasn't changed. This leads to unnecessary updates and can cause problems with services like No-IP, which softly require that updates are only sent when the IP actually changes—otherwise, users may hit rate limits or be flagged for abuse.Suggested Improvements:
When
update-intervalis set, skip updates if the IP hasn’t changed.This would align better with DDNS service expectations and reduce noise.
Add a CLI option to force update even if the IP is unchanged, for manual or scripted use.
This small change would make DDNS behavior more efficient and compliant with provider guidelines.
Thanks for your consideration!
Best regards
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.