Hurricane Electric's IPv6 Tunnel Broker Forums
May 24, 2013, 01:41:16 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to Hurricane Electric's Tunnelbroker.net forums!
 
   Home   Help Search Login Register  
Hurricane Electric's IPv6 Tunnel Broker Forums > Tunnelbroker.net Specific Topics > Questions & Answers > Automatic HE dynDNS update after IPv4 tunnel endpoint update
Pages: [1]
« previous next »
  Print  
Author Topic: Automatic HE dynDNS update after IPv4 tunnel endpoint update  (Read 1731 times)
trepex67
Newbie
*
Posts: 7


View Profile
« on: July 17, 2012, 11:52:07 pm »
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
Logged
kcochran
Sr. Network Engineer, Hurricane Electric
Administrator
Sr. Member
*****
Posts: 252



View Profile
« Reply #1 on: July 18, 2012, 11:21:42 am »
Quote
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.
Logged
trepex67
Newbie
*
Posts: 7


View Profile
« Reply #2 on: July 18, 2012, 10:25:48 pm »
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 Sad

R.
Logged
gtoso
Newbie
*
Posts: 2



View Profile
« Reply #3 on: August 21, 2012, 01:46:47 pm »
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.

Quote from: kcochran on July 18, 2012, 11:21:42 am
Quote
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.
« Last Edit: August 21, 2012, 01:59:06 pm by gtoso » Logged
gtoso
Newbie
*
Posts: 2



View Profile
« Reply #4 on: August 24, 2012, 07:02:42 pm »
Quote from: gtoso on August 21, 2012, 01:46:47 pm
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.
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!