Project

General

Profile

Actions

Bug #6990

closed

DDNS IPs not updating after a system restart

Added by Muchacha Grande about 8 years ago. Updated about 7 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
-
Start date:
12/06/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.2
Affected Architecture:

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

no-ip.png (56.6 KB) no-ip.png Muchacha Grande, 12/07/2016 05:36 AM
he.png (56.9 KB) he.png Muchacha Grande, 12/07/2016 05:36 AM
system log.txt (40.3 KB) system log.txt System boot log Muchacha Grande, 01/08/2017 11:29 PM
Actions #1

Updated by Jim Pingle about 8 years ago

  • 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.

Actions #2

Updated by Muchacha Grande about 8 years ago

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.

Actions #3

Updated by Kill Bill about 8 years ago

The HE.net looks definitely wrong. As noted there, you should use the Tunnel ID, and NOT hostname.

Actions #4

Updated by Muchacha Grande about 8 years ago

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.

Actions #5

Updated by Muchacha Grande about 8 years ago

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.

Actions #6

Updated by Jim Pingle about 8 years ago

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?

Actions #7

Updated by Muchacha Grande about 8 years ago

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.

Actions #8

Updated by Muchacha Grande almost 8 years ago

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.

Actions #9

Updated by Jim Pingle about 7 years ago

  • 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.

Actions

Also available in: Atom PDF