Skip to content
DnsLister Forum

Where domain hunters compare notes

Vodafone is filtering IPv6 DNS queries

I'm using Vodafone as my ISP and I'm seeing what appears to be DNS filtering/interference.

The IPv6 resolver works perfectly:

$ dig -t AAAA google.com @2001:4860:4860::8888 ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58402 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;google.com. IN AAAA ;; ANSWER SECTION: google.com.177 IN AAAA 2a00:1450:4003:810::200e ;; Query time: 20 msec ;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888) (UDP) ;; WHEN: Wed Sep 02 21:22:41 CEST 2026 ;; MSG SIZE rcvd: 67 

However, querying Google's DNS server over IPv4:

$ dig -t AAAA google.com @8.8.8.8 ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1220 ;; QUESTION SECTION: ;google.com. IN AAAA ;; Query time: 16 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP) ;; WHEN: Wed Sep 02 21:26:53 CEST 2026 ;; MSG SIZE rcvd: 67 

But with trace, the AAAA register appears:

$ dig -t AAAA google.com @8.8.8.8 +trace ;; global options: +cmd .6789INNSl.root-servers.net. .6789INNSc.root-servers.net. .6789INNSa.root-servers.net. .6789INNSi.root-servers.net. .6789INNSj.root-servers.net. .6789INNSk.root-servers.net. .6789INNSg.root-servers.net. .6789INNSe.root-servers.net. .6789INNSf.root-servers.net. .6789INNSd.root-servers.net. .6789INNSb.root-servers.net. .6789INNSm.root-servers.net. .6789INNSh.root-servers.net. .7122INRRSIGNS 8 0 518400 20260915050000 20260902040000 57780 . LWJGyncex/6vaD/0AWFuPl2Ng7NFGVERJ7xgwJ/P75OBT8suIB0TnK5E 7RowXHInpGA2UcDK/AxCOKUXsUtSd1OeUnQBZLE4m0YWKjlCQ6+F0UrG oMWTGZuJMSrj9WxolONFlWCfm2cnGOF6ZNirmYzc7L5ZqNd6zDFtJE/E jcBvUdvFsj90Yq7ac59GrXMAP9lzY2E95YNI6atc0lwcN+IHXIzhzQWx HR9Df8SjP64V+4vujb61r2m8V0zxUYom4Fx9M572zuS3o0G9mVfqFNaW KLGQGiWA1fvD/Rd5YcBhCW2d+f5iWb1lNJ8i5PpCp88zk25Zsku8J4pd PuBarg== ;; Received 693 bytes from 8.8.8.8#53(8.8.8.8) in 4 ms com.172800INNSg.gtld-servers.net. com.172800INNSa.gtld-servers.net. com.172800INNSc.gtld-servers.net. com.172800INNSe.gtld-servers.net. com.172800INNSb.gtld-servers.net. com.172800INNSk.gtld-servers.net. com.172800INNSf.gtld-servers.net. com.172800INNSm.gtld-servers.net. com.172800INNSj.gtld-servers.net. com.172800INNSd.gtld-servers.net. com.172800INNSh.gtld-servers.net. com.172800INNSi.gtld-servers.net. com.172800INNSl.gtld-servers.net. com.86400INDS19718 13 2 8ACBB0CD28F41250A80A491389424D341522D946B0DA0C0291F2D3D7 71D7805A com.86400INRRSIGDS 8 1 86400 20260915170000 20260902160000 57780 . sR14KQ7PJ5pG/gi0HseqXQGU1m6cNAQ58TsDeo3Ua2J5r5GAU4feKjOg 7VsdMFLHyoP8hZRg4+FXTPb0qOt1tHUqAtReiZ7E7OTeFAxPtm4nb9V/ aE3AvGCxR+sUC8OWa1R7nswb/+QlTwiu8NyywxyKA+XvHDHcflANfqTC qLlYsutoOmGtB9KGYCq25aauhy1/FpqLVPkKJ7ERWmIjyLR4RXdnbcvp QmCxFkJMVMNqVeHTaGH9PgDzn1zeCwchUru+yPQn/JUL4+SPSpUirJcw 1kcIx8ROliCCeSwmrpcMYZQTpvl/k08eZK5+IYsmI9yJdl5QKhpjs3Fn J8VZow== ;; Received 1198 bytes from 2001:500:2f::f#53(f.root-servers.net) in 12 ms google.com.172800INNSns2.google.com. google.com.172800INNSns1.google.com. google.com.172800INNSns3.google.com. google.com.172800INNSns4.google.com. CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 900 IN NSEC3 1 1 0 - CK0Q35HRS4H76G6CHNB9414CJN6S5UPL NS SOA RRSIG DNSKEY NSEC3PARAM CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 900 IN RRSIG NSEC3 13 2 900 20260907002613 20260830231613 41446 com. sg9EOEcu6SU4/ORJtbNXqgcb5RzZqJQmdWxcqkGAZOQ3FLF/Sx7pE1hn Yv/Skldv5Z0zZJ0G4tqCovTBylPKdQ== S84BOR4DK28HNHPLC218O483VOOOD5D8.com. 900 IN NSEC3 1 1 0 - S84BR9CIB2A20L3ETR1M2415ENPP99L8 NS DS RRSIG S84BOR4DK28HNHPLC218O483VOOOD5D8.com. 900 IN RRSIG NSEC3 13 2 900 20260908012131 20260901001131 41446 com. xUh2VrKslVK6kTUnET647tTAQSz+xF0jbkDAik9EXrcXeC+SiAxOrNEC xMd9ksojMnBs6+Ursf+99GmTxlpnjg== ;; Received 644 bytes from 2001:503:d2d::30#53(k.gtld-servers.net) in 44 ms google.com.38332INNSns4.google.com. google.com.38332INNSns2.google.com. google.com.38332INNSns1.google.com. google.com.38332INNSns3.google.com. ;; BAD (HORIZONTAL) REFERRAL ;; Received 139 bytes from 216.239.34.10#53(ns2.google.com) in 8 ms ;; communications error to 216.239.34.10#53: timed out google.com.38327INNSns2.google.com. google.com.38327INNSns3.google.com. google.com.38327INNSns1.google.com. google.com.38327INNSns4.google.com. ;; BAD (HORIZONTAL) REFERRAL ;; Received 139 bytes from 216.239.34.10#53(ns2.google.com) in 4 ms google.com.300INAAAA2a00:1450:400c:c02::65 google.com.300INAAAA2a00:1450:400c:c02::64 google.com.300INAAAA2a00:1450:400c:c02::8a google.com.300INAAAA2a00:1450:400c:c02::8b ;; Received 151 bytes from 2001:4860:4802:38::a#53(ns4.google.com) in 36 ms 

With other DNS servers, like 1.1.1.1 or 9.9.9.9 equal response, Answer: 0.

Is there a way to confirm it from the client side in any other way?

Thanks,

Source: r/ipv6 · by /u/rfmoz

Leave a Reply

Your email address will not be published. Required fields are marked *