Feature #1825
closedDynamic DNS client IPv6 support
50%
Description
DynDNS client needs IPv6 support for registering AAAAs.
Updated by Seth Mos over 12 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.
Updated by Jim Pingle over 12 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.
Updated by Jim Pingle over 12 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.
Updated by Chris Buechler about 12 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.
Updated by Jim Pingle about 12 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"
Updated by Daniel Becker about 11 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.
Updated by Jim Pingle about 11 years ago
It would, but how would we test it? I still am not aware of any DynDNS providers doing IPv6 updates.
Updated by Daniel Becker about 11 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
Updated by Jim Pingle about 11 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.
Updated by Daniel Becker about 11 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.
Updated by Daniel Becker about 11 years ago
Can you point me to where in the repository the code for this lives?
Updated by Daniel Becker almost 11 years ago
Pull requests here: https://github.com/pfsense/pfsense/pull/703
Updated by Ermal Luçi almost 11 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 4624f50fce5f1f41306d6852ca2922079b9d1694.
Updated by Jim Pingle almost 11 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)
Updated by Doktor Notor over 10 years ago
freedns.afraid.org also works, http://freedns.afraid.org/dynamic/update.php?<Authentication Token>&address=<IPv6>
Updated by Jim Pingle over 4 years ago
- Status changed from New to Resolved
Various providers have working IPv6 support, there is no longer a general issue here.