# IPv6 domains not blocked?

**URL:** <https://discourse.pi-hole.net/t/ipv6-domains-not-blocked/3914>\
**Category:** Help\
**Created:** [July 1, 2017, 2:26pm UTC](https://discourse.pi-hole.net/t/ipv6-domains-not-blocked/3914 "2017-07-01T14:26:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Creedy](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/james_creedy/32/1627_2.png) [@James\_Creedy](https://discourse.pi-hole.net/u/James_Creedy)\
**Post date:** [July 1, 2017, 2:26pm UTC](https://discourse.pi-hole.net/t/ipv6-domains-not-blocked/3914/1 "2017-07-01T14:26:36Z")

</div>

#### Please follow the below template, it will help us to help you!

## Expected Behaviour:

Domains on the block list should be blocked even over IPv6.  
I have full IPv6 connectivity to the internet and my PI Hole (which is working wonderfully for IPv4 thank you) is not blocking domains over IPv6.

## Actual Behaviour:

Resolving www.google-analytics.com I get two entries in the query log IPv4 says Pi-holed IPv6 says OK (forwarded).  
I have run pihole -r again to ensure both IPv4 and IPv6 blocking is enabled.  
I have also ran sudo apt-get upgrade to ensure I am running the latest version of Raspbian Jesse Lite.

## Debug Token:

p6kfobmoub

Thank You!

---

<div class="post-metadata">

**Author:** ![James\_Creedy](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/james_creedy/32/1627_2.png) [@James\_Creedy](https://discourse.pi-hole.net/u/James_Creedy)\
**Post date:** [July 1, 2017, 2:31pm UTC](https://discourse.pi-hole.net/t/ipv6-domains-not-blocked/3914/2 "2017-07-01T14:31:13Z")

</div>

I'm assuming this FAQ does not apply as I do in fact want FTL to analyse AAAA queries as my internet connection is IPv6 enabled?

> [@Why do blacklisted domains show IPv4 as "Pi-holed" but not IPv6 in the query log?](https://discourse.pi-hole.net/t/why-do-blacklisted-domains-show-ipv4-as-pi-holed-but-not-ipv6-in-the-query-log/3652?source_topic_id=3581):
>
> This behavior can be fixed by setting AAAA\_QUERY\_ANALYSIS=no in /etc/pihole/pihole-FTL.conf (you need to [create this file if it doesn't exist](https://github.com/pi-hole/FTL#ftls-config-file)). If you still see blacklisted IPv6 domains show as forwarded in your query log but don't have IPv6 enabled, you may see a false positive like the image below, where the IPv4 version of the domain is blocked, but not the IPv6 version. root@pihole:~ $ cat /etc/pihole/gravity.list | grep edge.quantserve.com 192.168.1.126 edge.quantserve.com [image] I…

Cheers,

---

<div class="post-metadata">

**Author:** ![Mcat12](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mcat12/32/20_2.png) [@Mcat12](https://discourse.pi-hole.net/u/Mcat12)\
**Post date:** [July 1, 2017, 3:35pm UTC](https://discourse.pi-hole.net/t/ipv6-domains-not-blocked/3914/3 "2017-07-01T15:35:37Z")

</div>

You're probably encountering a current bug in how we generate gravity.list. Your IPv6 address in `/etc/pihole/setupVars.conf` includes the `/64` at the end, which we are not accounting for when generating gravity. This leads to invalid entries, which are ignored, effectively removing any IPv6 blocking. Remove the `/64` from the end of your IPv6 address in `setupVars.conf` and run `pihole -g`. This will be fixed in the next release.

---

<div class="post-metadata">

**Author:** ![James\_Creedy](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/james_creedy/32/1627_2.png) [@James\_Creedy](https://discourse.pi-hole.net/u/James_Creedy)\
**Post date:** [July 1, 2017, 3:52pm UTC](https://discourse.pi-hole.net/t/ipv6-domains-not-blocked/3914/4 "2017-07-01T15:52:38Z")

</div>

Hi Mcat12,

This worked immediately! Thanks for your help 😄