Project

General

Profile

Feature #1825

Dynamic DNS client IPv6 support

Added by Chris Buechler almost 8 years ago. Updated 4 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
-
Start date:
09/01/2011
Due date:
% Done:

50%

Estimated time:

Description

DynDNS client needs IPv6 support for registering AAAAs.

Associated revisions

Revision 4624f50f
Added by Ermal Luçi about 6 years ago

Merge pull request #703 from razzfazz/dyndns_custom_v6

Add support for HE.net AAAA record updates. Fixes #1825.

History

#1 Updated by Seth Mos over 7 years ago

Briefly looked at it, but DynDNS didn't have backend support for submitting these. Not even in beta.

You can manually enter a v6 address on the service center but that's as far as it goes.

#2 Updated by Jim Pingle over 7 years ago

Namecheap appears to only go by hostname and has nothing in the FAQ [re: IPv6], but they have been very responsive to support queries in the past. I opened a ticket with them to ask about doing AAAA dyndns. We'll see what they say.

#3 Updated by Jim Pingle over 7 years ago

Reply from Namecheap is that they currently don't support it, but they submitted the request upward and they are supposed to let me know if/when they hear something back.

#4 Updated by Chris Buechler over 7 years ago

  • Target version changed from 2.1 to 2.2

pushing to 2.2 since it seems it's not supported by any of the providers yet.

#5 Updated by Jim Pingle over 7 years ago

Just noticed that https://dns.he.net/ supports IPv6 for DynDNS now. Update format is identical to IPv4, just send the IPv6 IP instead.

I suppose we could either have a drop-down that activates for certain providers that says "Update IPv4, Update IPv6, Update Both" or a pair of checkboxes, or take the easier way and have the IPv6 provider be considered separately in the master drop-down. For example "HE.net, HE.net IPv6, HE.net Tunnelbroker, and so on"

#6 Updated by Daniel Becker over 6 years ago

Would it be possible to at least add support for an IPv6 token to the update URL field for the "custom" service type? That seems like a fairly simple, non-intrusive change.

#7 Updated by Jim Pingle over 6 years ago

It would, but how would we test it? I still am not aware of any DynDNS providers doing IPv6 updates.

#8 Updated by Daniel Becker over 6 years ago

What about dns.he.net? From the example on their website:

http://dyn.example.com:password@dyn.dns.he.net/nic/update?hostname=dyn.example.com&myip=2001:db8:beef:cafe::1

#9 Updated by Jim Pingle over 6 years ago

Not so easy to test that one as it requires directing DNS for an entire domain at HE.net, it isn't really a DynDNS service so much as a dynamic way to update hosted DNS (like Namecheap).

If someone actually has a DNS account setup with he.net for a domain and is willing to test/help code, then it may be possible sooner rather than later.

#10 Updated by Daniel Becker over 6 years ago

I do have a domain with them, and I'll be happy to help test, but I'm probably not in a position to actually help code. I could also just set up a dynamic AAAA record for you to play with; let me know if that would be of interest, and if so, how to best get the hostname and hash to you.

#11 Updated by Daniel Becker over 6 years ago

Can you point me to where in the repository the code for this lives?

#13 Updated by Ermal Luçi about 6 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#14 Updated by Jim Pingle about 6 years ago

  • Status changed from Feedback to New
  • % Done changed from 100 to 50

Since this works for RFC2136 and he.net now, we can set it to partially done, but not completely done. (Redmine automatically toggled the status)

#15 Updated by Doktor Notor about 6 years ago

freedns.afraid.org also works, http://freedns.afraid.org/dynamic/update.php?&lt;Authentication Token>&address=<IPv6>

#16 Updated by Chris Buechler almost 5 years ago

  • Target version deleted (2.2)
  • Affected Documentation 0 added

#17 Updated by Jim Pingle 4 days ago

  • Status changed from New to Resolved

Various providers have working IPv6 support, there is no longer a general issue here.

Also available in: Atom PDF