Automatic HE dynDNS update after IPv4 tunnel endpoint update

[trepex67]

Hello,

I configured the automatic dynDNS update inside the HE DNS system for a hostname "trepex.he-dynDNS.picocell.de".
It did work out good for some tests (DSL router got new IPv4 address, tunnel endpoint update with "ipv4.tunnelbroker.net/ipv4_end.php?ipv4b=<ipaddr>&pass=<pass>&user_id=<username>&tunnel_id=xxxxxx", new
IP address seen with DNS query).
But the last 2x this was done at night (between 4-5am GMT), it did not work.

Today in the morning (Europe), my router complained again that the dynDNS mapping is wrong. So I
checked out the status:

I checked all 4 HE nameservers (ns[2-5].he.net) and they still had the OLD mapping.
I checked on my tunnel status page (advanced tab) and this one did show the wrong entry as well.
I clicked "update" there and saw the correct (new) IP.
Some seconds later the HE nameservers also had the correct new IP.

Any idea what might have happened?

Ralf

[kcochran]

These settings will be used to automatically update the hostname below whenever you update your tunnel's IPv4 endpoint using the DynDNS-compatible mechanism at https://ipv4.tunnelbroker.net/nic/update. This is only for hostnames set dynamic with dns.he.net.

The ipv4_end.php method is still supported, but it is considered legacy, as it's its own beast, whereas /nic/update uses a well-defined and widely implemented API.

[trepex67]

Hi!

So you mean the "old" tunnel-update script does not update the dynDNS entry?
Does the new nic/update allow http traffic? My router can't do https for dynDNS :(

R.

[gtoso]

Hi to all,
is it possible to automatically update the hostname using old ipv4_end.php?
I tried but at the moment it doesn't work and need manual refresh in Tunnel Details.

I need to use http (not https) and i prefer not to use login/password,
does the new method support hash of password?

I tried to use https url in Cisco IOS "ip ddns update method ..." but it failed.

These settings will be used to automatically update the hostname below whenever you update your tunnel's IPv4 endpoint using the DynDNS-compatible mechanism at https://ipv4.tunnelbroker.net/nic/update. This is only for hostnames set dynamic with dns.he.net.

The ipv4_end.php method is still supported, but it is considered legacy, as it's its own beast, whereas /nic/update uses a well-defined and widely implemented API.

[gtoso]

Hi to all,
is it possible to automatically update the hostname using old ipv4_end.php?
I tried but at the moment it doesn't work and need manual refresh in Tunnel Details.

I just tried again, it works fine.
Maybe a temporary problem or something has changed.