Bug #6990
closed
DDNS IPs not updating after a system restart
Added by Muchacha Grande over 7 years ago.
Updated over 6 years ago.
Description
When the system shuts down and then restarts (for example after a power failure) unsing a DSL connection with PPPoE, my IP changes on reconnection, but if for some reason my DDNSs fail the update on the first try, then they are not updated anymore and the only way to update them is accessing the web interface and force them to do it.
May be it could be possible to add a retry timeout in case the DDNSs update fail to update, and force them to keep retrying each X seconds until they succeed.
Files
- Status changed from New to Feedback
Not nearly enough detail.
What are the exact types and services used in your Dynamic DNS configuration? You can obscure passwords and hostnames but please provide more information about the specifics of your setup.
I'm using a no-ip and a he service. Both of them updating the same wan IPv4 address.
Could you please tell me what exact information you need?
I'm sending you two screenshots but I think is not enoght info.
The HE.net looks definitely wrong. As noted there, you should use the Tunnel ID, and NOT hostname.
HE.net has two kinds of service, the DDNS service and the IPv6 tunnel. You must be talking about HE.net Tunnelbroker service.
I'm using it in my own router and, of course, I put the tunnel id in the config, but with the DDNS service you have to use the hostname to tell HE where is that host.
In this case I'm using HE.net DDNS service and it works fine with the given hostname except in the case of a reboot as I explained before.
Jim Pingle wrote:
Not nearly enough detail.
What are the exact types and services used in your Dynamic DNS configuration? You can obscure passwords and hostnames but please provide more information about the specifics of your setup.
Please, tell me what information you need or would be usefull, and I'll look for it.
Nothing unusual in the settings, look for anything related to Dynamic DNS in the main system log, are there any errors there when it fails?
Jim Pingle wrote:
Nothing unusual in the settings, look for anything related to Dynamic DNS in the main system log, are there any errors there when it fails?
Now I have to wait till it happen again, because the last event took place on December 6 and the log file was cycled and doesn't contain info from that day.
Hi,
yesterday, January 8, my customers router shut down due to a power loss.
When the power returned the router booted up and here is the system log file.
The system booted up near 12:30 PM and the dynamic DNSs entries were updated today, January 9 near 1 AM, more than 12 hours after boot up.
- Status changed from Feedback to Not a Bug
This is working fine on current versions for myself and others, if there is still a problem with this on 2.4 it may be something else in your configuration or environment and not directly related to dynamic DNS. Closing.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Kill Bill 
