DynDNS for IPv4 and IPv6

no

Hi,

I have the issue that my DNS provider offers a single URL to update my records:
https://dyndns.inwx.com/nic/update?myip=<ipaddr>&myipv6=<ip6addr>
The problem here is if I create a "Custom" and "Custom (v6)" DynDNS client entry the last one called will be the valid one.
This means that if IPv6 updated last I wont be able to reach the system from most places.

It would be really nice to have a "Custom (both)" option which offers %IP% and %IPv6% or so.
Or would you have an alternative solution?

Greetings

JKnott

@no

Why do you need dynamic DNS for IPv6? Your prefix should be stable, so you don't need a dynamic DNS for it. Just use static config.

no

no, not really

with every pppoe reconnect i get a new /56 with prefix delegation, so a static config wouldn't help

JKnott

@no

Do you have Do not allow PD/Address release set?

no

@JKnott

doesn't seem to help

Gertjan

Well, first, rebuild the check-list you use when you market for a DNS provider and ISP.
Who is your ISP ?

True, dyndns is often IPv4 only, which permits you to call home when your WAN IPv4 changed again.
Having a random /56 for IPv6 is even less fun.

What about creating a
ipv4.your-dynd-dns.tld for IPv4
and
ipv6.your-dynd-dns.tld for IPv6 ?

Or, what I did : I use the Pro version of a box, of Franc's biggest historical operator. Pro means : big, slow, black, supports phone ( ?? ) and TV ( ????) (we are a companies with 8 outside lines, a fax line - soon to be abandoned) .... and this box doesn't know what IPv6 is ....
So I decided years ago to use tunnel.he.net and never regretted it. I'll move away from them when the day I find a local ISP that offers the same IPv6 facilities. I guess I will have to transmit that mission to the next generation.

Today, I can access my Syno Diskstation NAS using a hostname using IPv6 from all over the world - no need for dyndns because he.net never changes the /48 pool.
And the best part : no NAT needed

no

@Gertjan said in DynDNS for IPv4 and IPv6:

Well, first, rebuild the check-list you use when you market for a DNS provider and ISP.
Who is your ISP ?

Telekom / Germany

True, dyndns is often IPv4 only, which permits you to call home when your WAN IPv4 changed again.
Having a random /56 for IPv6 is even less fun.

What about creating a
ipv4.your-dynd-dns.tld for IPv4
and
ipv6.your-dynd-dns.tld for IPv6 ?

With a limited number of hosts that doesn't really workout and moving a hole set of domains somewhere else isn't what I'd like to do besides splitting them up

Or, what I did : I use the Pro version of a box, of Franc's biggest historical operator. Pro means : big, slow, black, supports phone ( ?? ) and TV ( ????) (we are a companies with 8 outside lines, a fax line - soon to be abandoned) .... and this box doesn't know what IPv6 is ....
So I decided years ago to use tunnel.he.net and never regretted it. I'll move away from them when the day I find a local ISP that offers the same IPv6 facilities. I guess I will have to transmit that mission to the next generation.

Today, I can access my Syno Diskstation NAS using a hostname using IPv6 from all over the world - no need for dyndns because he.net never changes the /48 pool.
And the best part : no NAT needed

I don't need NAT here either, but I guess he.net won't be routing 100 MBit/s and above(?) and if so not with the latency(?)

Gertjan

@no said in DynDNS for IPv4 and IPv6:

routing 100 MBit/s and above(?) and if so not with the latency(?)

Can't tell. It maxes out for me, but my ISP gives my 22Mbits/sec down, 2,2 Mbits up ....
It's free to try, though.