Feature #14067
open
Force Dynamic DNS to fetch public IP instead of using WAN IP
0%
Description
Dynamic DNS has the ability to fetch the public IP via e.g. a service like dyndns.org. However, unless the IP on WAN is detected as being a "private IP", this check is not made in this way. The assumption is rather made that the WAN IP is valid and the one to be used.
Adding a checkbox to "force fetching public IP" would add beneficial in some cases.
One such case is solving an issue with UPnP not playing ball when WAN IP is RFC 1918. Using a random public IP, on the upstream router (for example a 5G router) solves this issue.
Related issues
Updated by Jim Pingle over 1 year ago
It would also be nice in some rare cases to force it the opposite way, to disable the check entirely so it will use the address it has no WAN no matter what.
So this could have three choices:
- Auto (current default, uses check IP service when WAN is "private")
- Always use Check IP Service
- Never use Check IP Service
Might make sense to implement #9063 alongside this (the ability to select a specific Check IP service for a DynDNS entry)
Updated by Jim Pingle over 1 year ago
- Related to Feature #9063: Allow dynamic DNS client entry to specify which Check IP service to use added
Updated by