Unable to browse through IPv6 unless making DNS requests

[ToasterPC]

Hey there!

First time poster here, so please tell me if I'm missing anything!

I've been enjoying my time with an ASUS GT-AX-11000 for about two years now, and about two weeks ago I finally got native IPv6 support with my ISP!

However, for some reason the only traffic I'm able to get is DNS related, as any attempt to connect to an IPv6 based website ends in a timeout.

Aside from the router, the only unusual thing that comes to mind is that I'm using a Raspberry Pi 4B as a Pi-Hole, and thus after going over the issue on their Discourse forum I thought perhaps it would be a good idea to check on over here.

Just to be sure, I'll link the thread made over there as a point of reference.

Thanks for the help!

 

[toaruScar]

How do you make an DNS request? is the query sent to an IPv4 or IPv6 address?

 

[dave14305]

Reading the Discourse thread, being able to resolve AAAA names is not the same as having IPv6 functional. You can resolve AAAA names through an IPv4 DNS server. Your last post over there suggests your ISP doesn’t support IPv6.

 

[ColinTaylor]

Your last post over there suggests your ISP doesn’t support IPv6.

Indeed. Shame he didn't bother updating this thread.

Pi-Hole Host is able to connect through IPv6, but the rest of the network can't

Okay, just got off the phone with my ISP. Turns out they don't know how I got a connection in the first place 🥴. According to them, no client of them within the country has IPv6 enabled on residential connections, and they advised me to simply ignore it, so at this point I'm just plain...

discourse.pi-hole.net

 

[ToasterPC]

Being honest, I'm not quite sure if the person that helped me over at the ISP help desk really understood what I was asking for, which is why I thought about asking around (for context, the last time I called they wanted me to pay for an enterprise bill to enable bridge mode).

When I perform a dig request for an IPv6 address I'm able to receive a valid answer:

dig AAAA ipv6.google.com @127.0.0.1 -p 5335 ; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> AAAA ipv6.google.com @127.0.0.1 -p 5335 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6500 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1472 ;; QUESTION SECTION: ;ipv6.google.com. IN AAAA ;; ANSWER SECTION: ipv6.google.com. 86398 IN CNAME ipv6.l.google.com. ipv6.l.google.com. 300 IN AAAA 2607:f8b0:4012:80a::200e ;; Query time: 3131 msec ;; SERVER: 127.0.0.1#5335(127.0.0.1) ;; WHEN: Tue Oct 06 09:07:05 CDT 2020 ;; MSG SIZE rcvd: 93

being able to resolve AAAA names is not the same as having IPv6 functional.

While this is true (and something I was not aware of, so thanks!) what leads me to believe there might be a chance of perhaps a configuration mistake on my side, is the fact that all of my network devices have been assigned a valid, pingable IPv6 address aside from the link local one, add to this that the prefix of said addresses coincide with the value of my ISPs prefix and that I even get a PTR record alongside them.

I'm not sure how to do this, but if there's a safe way to post one of them in the forum please tell me so.

 

[ToasterPC]

I'll go ahead and bump the thread, it seems that the Raspberry Pi is able to successfully ping through IPv6 while no other device in the network can.

PING ipv6.google.com(qro02s15-in-x0e.1e100.net (2607:f8b0:4012:80b::200e)) 56 data bytes 64 bytes from qro02s15-in-x0e.1e100.net (2607:f8b0:4012:80b::200e): icmp_seq=1 ttl=119 time=28.3 ms 64 bytes from qro02s15-in-x0e.1e100.net (2607:f8b0:4012:80b::200e): icmp_seq=2 ttl=119 time=11.6 ms 64 bytes from qro02s15-in-x0e.1e100.net (2607:f8b0:4012:80b::200e): icmp_seq=3 ttl=119 time=10.5 ms 64 bytes from qro02s15-in-x0e.1e100.net (2607:f8b0:4012:80b::200e): icmp_seq=4 ttl=119 time=10.2 ms 64 bytes from qro02s15-in-x0e.1e100.net (2607:f8b0:4012:80b::200e): icmp_seq=5 ttl=119 time=12.10 ms 64 bytes from qro02s15-in-x0e.1e100.net (2607:f8b0:4012:80b::200e): icmp_seq=6 ttl=119 time=12.7 ms 64 bytes from qro02s15-in-x0e.1e100.net (2607:f8b0:4012:80b::200e): icmp_seq=7 ttl=119 time=12.3 ms ^C --- ipv6.google.com ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 11ms rtt min/avg/max/mdev = 10.238/14.099/28.348/5.897 ms

I have already tried to perform the same test on other devices even after assigning static routes, but so far no dice.

On a laptop that has an IPv6 address, I receive the following results:

Pinging ipv6.l.google.com [2607:f8b0:4012:80b::200e] with 32 bytes of data: Destination host unreachable. Destination host unreachable. Destination host unreachable. Ping statistics for 2607:f8b0:4012:80b::200e: Packets: Sent = 3, Received = 0, Lost = 3 (100% loss), Control-C

But the Raspberry is even able to successfully pass the test using Chromium:

What should I check to solve the issue?