### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [September 2, 2018, 12:11am UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/21 "2018-09-02T00:11:43Z")
And check below one on one of your **client** PC's (Linux,Windows or Mac):
`nslookup -type=txt -class=chaos version.bind `
Here's mine (ipv4 though):
```
C:\>nslookup -type=txt -class=chaos version.bind 10.0.0.2
Server: noads.dehakkelaar.nl
Address: 10.0.0.2
version.bind text =
"dnsmasq-pi-hole-2.79"
```
EDIT: If get `pihole-FTL` running again 😉
---
### Author:  [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)
#### Post date: [September 2, 2018, 7:04pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/22 "2018-09-02T19:04:44Z")
Here is the output of my netstat (IPv4/6)
```
root@pi-hole-r-pi:~# netstat -tulpn | grep pihole-FTL tcp 0 0 127.0.0.1:4711
0.0.0.0:* LISTEN 922/pihole-FTL
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 922/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 922/pihole-FTL
tcp6 0 0 :::53 :::* LISTEN 922/pihole-FTL
udp 0 0 0.0.0.0:53 0.0.0.0:* 922/pihole-FTL
udp6 0 0 :::53 :::* 922/pihole-FTL
```
---
### Author:  [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)
#### Post date: [September 2, 2018, 7:07pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/23 "2018-09-02T19:07:00Z")
Output of nslookup:
```
C:\>nslookup -type=txt -class=chaos version.bind 192.168.0.10
Server: pi-hole-r-pi
Address: 192.168.0.10
version.bind text =
"dnsmasq-pi-hole-2.79"
```
EDIT: IPv6 (obviously) does not work:
```
C:\>nslookup -type=txt -class=chaos version.bind **** :1129:a2bd:9c48:fccd
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: (new prefix, hiding it) **** :1129:a2bd:9c48:fccd
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
```
---
### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [September 3, 2018, 8:24pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/24 "2018-09-03T20:24:47Z")
Does that exact same ipv6 `nslookup` run on Pi-hole work ?
The `pihole-FTL` binary is listening on all ipv6 addresses "`:::53`" as can be seen from the `netstat` output.
If dont get response, then something is still not setup correctly with the ipv6 IP address.
If do get proper response, your router might be blocking with some sort of safety mechanism:
> [@\[SOLVED\] Pi-hole on Amazon EC2 not filtering ads](https://discourse.pi-hole.net/t/solved-pi-hole-on-amazon-ec2-not-filtering-ads/11111/12):
>
> I just found out that my Vodafone router had an option enabled called Safe DNS which prevent usage of custom DNS servers. I disabled it and now I see Pi-hole logging queries. It's still not blocking ads though frowning_face
> [@Why won't Pi-hole work with DNS rebind protection enabled?](https://discourse.pi-hole.net/t/why-wont-pi-hole-work-with-dns-rebind-protection-enabled/3142):
>
> What is DNS rebind protection? If your router has an option called DNS rebind protection enabled, you may run into issues when trying to use Pi-hole as your DNS server. The reasons for this are quite technical, but to summarize what this option does in one sentence: DNS rebind protection does not allow DNS queries to be answered with a local IP address. Why does this interfere with Pi-hole? DNS rebind is meant to be a [countermeasure to an attack on your network](http://www.techrepublic.com/blog/it-security/public-ip-dns-rebinding-another-reason-not-to-use-default-passwords/). So in many cases, it's actu…
---
### Author:  [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)
#### Post date: [September 4, 2018, 1:54pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/25 "2018-09-04T13:54:49Z")
This is what I got:
```
root@pi-hole-r-pi:~# nslookup
type=txt -class=chaos version.bind
**** :1129:a2bd:9c48:fccd
;; connection timed out; no servers could be reached
```
---
### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [September 4, 2018, 5:14pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/26 "2018-09-04T17:14:42Z")
Does a `nslookup` run on Pi-hole addressing the internal loopback interface ipv6 IP "`::1`" work ?
`nslookup -type=txt -class=chaos version.bind ::1`
Can you SSH to that ipv6 address from one of your PC's ?
The sshd daemon binds in a same manner to ipv6 as pihole-FTL does (listening on all ipv6 addresses "`:::22`"):
```
pi@noads:~ $ sudo netstat -nltup | grep sshd
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 587/sshd
tcp6 0 0 :::22 :::* LISTEN 587/sshd
```
Do you have a firewall active on Pi-hole ?
`sudo iptables -L -n`
---
### Author:  [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)
#### Post date: [September 4, 2018, 5:24pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/27 "2018-09-04T17:24:57Z")
> Does a `nslookup` run on Pi-hole addressing the internal loopback interface IP “ `::1` ” work ?
I got the same result (connection timed out, etc)
I am able to SSH into my Pi with IPv6.
Iptables output:
```
root@pi-hole-r-pi:~# iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
```
---
### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [September 4, 2018, 5:30pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/28 "2018-09-04T17:30:36Z")
I'm out of ideas ... for now.
I must say that I am not that familiar with ipv6 so dont know what to look for.
Maybe someone else does ???
EDIT: one more thing to check, is the ipv6 address correct in below Pi-hole config file ?
`sudo grep 'IPV' /etc/pihole/setupVars.conf`
If not, run below one to repair:
`pihole -r`
---
### Author:  [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)
#### Post date: [September 4, 2018, 5:37pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/29 "2018-09-04T17:37:07Z")
Yep, it is the same as in the interfaces config.
Could it be OpenVPN (I am not too familiar with running a VPN)? It is set up to only run IPv4.
---
### Author:  [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)
#### Post date: [September 4, 2018, 5:38pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/30 "2018-09-04T17:38:05Z")
Dont thinks so ... but I dont know everything so could be wrong 😉
---
### Author:  [@Ryan1](https://discourse.pi-hole.net/u/Ryan1)
#### Post date: [September 4, 2018, 5:41pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/31 "2018-09-04T17:41:04Z")
Oh well. If you think of anything, let me know. Thanks for the help though.
---
### Author:  [@Ronnick](https://discourse.pi-hole.net/u/Ronnick)
#### Post date: [September 5, 2018, 5:27pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/32 "2018-09-05T17:27:08Z")
See my post in this thread about a solution to ipv6 hostname resolution.
> [@Pi-hole as a DHCP / Dual Stack IPv4 & IPv6 and Clients Hostnames + - FritzBox Settings Help](https://discourse.pi-hole.net/t/pi-hole-as-a-dhcp-dual-stack-ipv4-ipv6-and-clients-hostnames-fritzbox-settings-help/12347):
>
> Expected Behaviour: Blocking (IPv4 and IPv6) and DHCP are working well, however, in the Pi-hole dashboard clients are showing the correct hostname only for IPv4. IPv6 names are not resolving. Network and Hardware Router: Fritzbox 7390 Firmware: 06.83 DNS Rebind Protection Domain name exceptions: pi.hole lan IPv6 Settings: Odroid C2 OS: DietPi v.6.13 Pi-hole version is v4.0 AdminLTE version is v4.0 FTL version is v4.0 Pi-hole as DNS and DHCP My ISP supports IPv4…
Ronnick
---
### Author:  [@system](https://discourse.pi-hole.net/u/system)
#### Post date: [September 26, 2018, 5:27pm UTC](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643/33 "2018-09-26T17:27:15Z")
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
[Previous page](https://discourse.pi-hole.net/t/ipv6-not-resolving-hostnames/11643.md?page=1)