Encountering a problem whereby any domains I add to blacklist.txt are only blocked over IPv4, not IPv6. Confirmed by checking gravity.list, only contains redirect to IPv4 address.
If we could get output from pihole -d to start the debugger. And ls -la /proc/net/if_inet6 output. Thanks!
Confused what's happened with threads, new to Discourse 
But in response to DanSchaper's original post.
pihole -d
ls -la /proc/net/if_inet6
-r--r--r-- 1 root root 0 Oct 26 22:23 /proc/net/if_inet6
(Apologies, that was me messing things up! Your original thread is here, please continue the conversation)
Thanks, looks like there may be a problem with the IPv6 stack. What does ip -6 route look like?
Sorry to post here again! But the thing is I'm not able to post in my own thread currently. As far as I can tell
Sorry, thread was locked for some reason!
Somebody ban me before I do any more damage!!! (plz no)
1 Like
Hahaha 
No worries!
1 Like
ip -6 route
2a02:8010:60b0::/64 dev eth0 proto kernel metric 202 mtu 1492
fe80::/64 dev eth0 proto kernel metric 256
fe80::/64 dev wlan0 proto kernel metric 256
default via fe80::fa32:e4ff:fea7:8260 dev eth0 metric 202 mtu 1492
The strange thing is, otherwise, all AAAA ads are being blocked (non-blacklist domains).
I've made some updates to the debug script to track a few more things. Would you be okay with running the new script?
curl -sSL https://raw.githubusercontent.com/pi-hole/pi-hole/feature/debugUpdate/advanced/Scripts/piholeDebug.sh | sudo bash
And when you are prompted, try to browse and see if you can catch an IPv6 client being served an advertisement. Then send us the link.
Just FYI, when you curl to bash, none of the user input parts of the script fire. So you will not be able to upload the script. probably best to do:
curl -sSL https://raw.githubusercontent.com/pi-hole/pi-hole/feature/debugUpdate/advanced/Scripts/piholeDebug.sh > debug.sh`
sudo bash debug.sh
OK, so I ran the script following PromoFaux's instructions:
And pretty sure I caught myself some IPv6 ads at id.google.co.uk
http://termbin.com/jok6
Though actually checking, it would appear not 
I'll try again.
Yeah, we'll need to add some AAAA record checks in debug to test the resolver working correctly.
Yeah sorry, there definitely should've been some. Anyway http://termbin.com/xtv4
Thanks, looks like the basic functions work okay, getting all the traffic and hits. Is it only the manually blacklisted domains that are missing the IPv6 portion? And are you using the CLI or the web interface to add the domains to the blacklist?
Yes that's correct, only blacklisted domains. Initially the web interface until I noticed the problem and tested with the CLI, but same result unfortunately 
That narrows down where we need to search for the bug. Trying to duplicate it now...
OK, thanks. Please don't worry too much, only if you have time.