# IPv6 not resolving hostnames

**URL:** <https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643>\
**Category:** Help\
**Created:** [August 9, 2018, 1:56am UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643 "2018-08-09T01:56:50Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 9, 2018, 1:56am UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/1 "2018-08-09T01:56:50Z")

</div>

So I set up Pi-Hole to filter IPv6 DNS hostnames with the pi's DNS set to Cloudflare's DNS ([https://1.1.1.1](https://1.1.1.1)). My Pi itself has IPv6 access (ping google.com shows google's IPv6 address and traceroute works as well).

As for what actually is happening is Pi-Hole (or some setting on my Pi) might be preventing IPv6 DNS queries from "passing through." (I do have PiVPN installed).

Thank you for reading.

Debug Token: px3ydz8wjt

---

<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:** [August 9, 2018, 5:55pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/2 "2018-08-09T17:55:22Z")

</div>

Do a traceroute on your IPv6 address (`2605:6000:1500:83d4:1129:a2bd:9c48:fccd`)

You can also try updating to Pi-hole 4.0

---

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 9, 2018, 8:34pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/3 "2018-08-09T20:34:01Z")

</div>

![image](https://discourse.pi-hole.net/uploads/default/original/2X/6/61f2cc8bc12abb19cdf3a22f00b4c972923a47d9.png)  
This was the result. I will update Pi-Hole when I get home.

---

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 10, 2018, 4:24pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/4 "2018-08-10T16:24:51Z")

</div>

Edit: I updated Pi-Hole to 4.0 and did another traceroute and got the same result (I also pinged my pi from my computer in cmd and it pings it but DNS still does not resolve; I am testing this by disabling IPv4).

---

<div class="post-metadata">

**Author:** ![Ronnick](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/74df32/32.png) [@Ronnick](https://discourse.pi-hole.net/u/Ronnick)\
**Post date:** [August 10, 2018, 8:14pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/5 "2018-08-10T20:14:05Z")

</div>

Yup, I’m seeing the same thing. IPv6 addresses are not being resolved to hostnames. Trace route from windows, Mac and Linux boxes resolve correctly.

---

<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:** [August 11, 2018, 7:37pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/6 "2018-08-11T19:37:21Z")

</div>

@Ryan1 make a new debug token since you updated Pi-hole.  
@Ronnick make a debug token.

---

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 11, 2018, 7:44pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/7 "2018-08-11T19:44:12Z")

</div>

@Mcat12 81awt7i15k

---

<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:** [August 11, 2018, 8:48pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/8 "2018-08-11T20:48:28Z")

</div>

What is the output of `cat /etc/pihole/pihole-FTL.conf`

---

<div class="post-metadata">

**Author:** ![Ronnick](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/74df32/32.png) [@Ronnick](https://discourse.pi-hole.net/u/Ronnick)\
**Post date:** [August 12, 2018, 12:11am UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/9 "2018-08-12T00:11:08Z")

</div>

Cat output:  
#RESOLVE\_IPV4  
RESOLVE\_IPV4=yes

#RESOLVE\_IPV6  
RESOLVE\_IPV6=yes

#AAAA\_QUERY\_ANALYSIS  
AAAA\_QUERY\_ANALYSIS=yes

#PRIVACYLEVEL  
PRIVACYLEVEL=0

token hiv9cjkvnj

---

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 12, 2018, 1:42pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/10 "2018-08-12T13:42:56Z")

</div>

I have no output.

 ![image](https://discourse.pi-hole.net/uploads/default/original/2X/5/5ac6f813a7e69bd30b6c423031e40baa18c37a08.png)

---

<div class="post-metadata">

**Author:** ![Ronnick](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/74df32/32.png) [@Ronnick](https://discourse.pi-hole.net/u/Ronnick)\
**Post date:** [August 12, 2018, 2:19pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/11 "2018-08-12T14:19:59Z")

</div>

The standard install doesn’t have anything that in the file. I purposely put those 4 options in just to see if it made a difference.

---

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 15, 2018, 8:50pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/12 "2018-08-15T20:50:07Z")

</div>

bump (just making sure this post is still active)

---

<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:** [August 20, 2018, 12:34am UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/13 "2018-08-20T00:34:04Z")

</div>

Make a new debug token, sorry for the late reply.

---

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 20, 2018, 2:23am UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/14 "2018-08-20T02:23:17Z")

</div>

All good: 96ibkjkpab

---

<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:** [August 20, 2018, 9:17pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/15 "2018-08-20T21:17:54Z")

</div>

You have IPv6 queries in the log, but the debugger was unable to resolve domains over IPv6:

```auto
*** [DIAGNOSING]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve view.atdmt.com.70892.9519.302br.net via localhost (::1)
[✗] Failed to resolve view.atdmt.com.70892.9519.302br.net via Pi-hole (2605:6000:1500:83d4:1129:a2bd:9c48:fccd)
[✓] doubleclick.com is 2607:f8b0:4000:811::200e via a remote, public DNS server (2001:4860:4860::8888)

```

Do you have multiple network interfaces on the device?

---

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 20, 2018, 11:23pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/16 "2018-08-20T23:23:11Z")

</div>

Yes I do. lo, eth0, wlan0, and tun0.

---

<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:** [August 21, 2018, 12:43am UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/17 "2018-08-21T00:43:09Z")

</div>

Try going to the web interface settings -\> DNS -\> "Interface listening behavior" and set it to listen on all local interfaces.

---

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 21, 2018, 4:27am UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/18 "2018-08-21T04:27:06Z")

</div>

I already have it set to listen on all interfaces and permit all origins (for the vpn).

---

<div class="post-metadata">

**Author:** ![Ryan1](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/3da27b/32.png) [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)\
**Post date:** [August 27, 2018, 8:39pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/19 "2018-08-27T20:39:44Z")

</div>

bump (again, sorry)

---

<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:** [September 1, 2018, 11:47pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/20 "2018-09-01T23:47:05Z")

</div>

What is the output of `sudo netstat -tulpn | grep pihole-FTL`

[Next page](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643.md?page=2)