@robbie3999 said:
IPv6 addresses not working?
Hi, I was wondering if there are any known issues with IPv6 addresses. When I try to connect to the api (api.themoviedb.org) using IPv6 addresses I get "connection timed out". IPv4 addresses work fine. Here are some that don't work for me: 2600:9000:2464:9e00:c:174a:c400:93a1, 2600:9000:2464:8600:c:174a:c400:93a1, 2600:9000:2464:5200:c:174a:c400:93a1

The reason I have IPv6 addresses is I am running cygwin (linux emulator) on windows 10, it uses the underlying windows for network requests. Windows appears to "prefer" IPv6 over IPv4 by default, so DNS requests for names in both spaces get the IPv6 addresses first and then the IPv4 addresses.

I don't know if it solves your problem, but...
Cloudflare's DNS server (1.1.1.1) has been causing some issues in and for some countries.
If you are using it try switching to Google (8.8.8.8)

Yes, I am currently using google dns for both ipv4/6. DNS seems to work fine. This site http://test-ipv6.com shows that I am configured to use ipv6 and I can ping some of the sites listed:

[~]>ping6 -c 2 he.net
PING he.net (2001:470:0:503::2): 56 data bytes
64 bytes from he.net: icmp_seq=0 ttl=51 time=76.515 ms
64 bytes from he.net: icmp_seq=1 ttl=51 time=55.896 ms
--- he.net ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 55.896/66.206/76.515/10.310 ms

but i just can't ping/wget/curl/perl-lwp connect to api.themoviedb.org using ipv6.

It occurs to me that you might want to see the actual commands I am running to get the issues. I have tried multiple times to post sample commands and output so you can see what I am doing, but I can't submit them to the forum, anytime I try to post anything more than a few lines of text, I get a big red square that says Error, there was a problem.

Here is a test url I have been using:

https://api.themoviedb.org/3/movie/630?api_key=xxxxxx

I will also add that the program has been working fine for months, the problem just started about last tuesday or wednesday.

So, another update... I have been using "tracert" to trace packets from my computer. It appears that the ipv6 packets to themoviedb.org are not getting out of my ISP network. So it appears there is nothing wrong with your server.

However, I tried numerous other ipv6 servers and I can send packets to them just fine. My ISP is Charter/Spectrum, which is a pretty big ISP, so I am kinda scratching my head wondering why they don't have dns information for themovedb.org. How long have the current ipv6 DNS entries been in place?

@robbie3999 said:
How long have the current ipv6 DNS entries been in place?

I understand very little about this issue.
I believe that only the administrator, Travis Bell, can inform.
Let's wait for him to come by.

I think I am going to close this issue. I am convinced it is an ISP issue. Spectrum says they support ipv6 but from reading various forums, it appears that a lot of people are having a lot of problems with it working properly on their network.

In case someone else has similar problems, here are some workarounds:

1) Some applications can force the type, for example wget and curl have command line options to force ipv4 or ipv6. I am using perl and the LWP library which has no such option.

2) My current workaround is to hard code the hostname and an ipv4 address in the local etc/hosts file. This forces that address for that hostname for all applications. This should work fine unless the ip address gets changed often.

3) Windows has a registry option to disable ipv6 (not recommend by ms) or set "prefer ipv4 over ipv6". Explained here https://learn.microsoft.com/en-US/troubleshoot/windows-server/networking/configure-ipv6-in-windows