Updating AAAA record fails, grabs IPv4 address instead of IPv6 about route53-dynamic-dns HOT 3 CLOSED

This container supports 2 different IP checker sites:

• ipify.org
• ifconfig.co

In your case you are using the ifconfig.co and I assume that this site by default responds with IPv4. I see from their say that you can pass arguments whether you want to force it to return IPv4 or IPv6 when using the command line. But currently the code in this container uses the HTTP.

So the short answer is that IPv6 is not supported currently. You are welcome to submit a PR with this feature.

from route53-dynamic-dns.

Actually, the default value returned by ifconfig.co is IPv6 when available.

Discussing this with a friend, he pointed out that to get the container out of host mode, the container would need an IPv6 address from docker to make sure the request goes out over IPv6, and that's what the IP checker would grab--not the host's IPv6, but the container's. Since grabbing the host's IPv6 is the desired behavior, network_mode: host is the appropriate solution.

from route53-dynamic-dns.

Good to know! Thanks for sharing the solution @ohshitgorillas!

from route53-dynamic-dns.