IPv6 not resolving hostnames

Help
14

All good: 96ibkjkpab

15

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

*** [ 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?

16

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

17

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

18

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

19

bump (again, sorry)

20

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

21

And check below one on one of your client PC's (Linux,Windows or Mac):

nslookup -type=txt -class=chaos version.bind <PIHOLE_IPV6_ADDRESS>

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 :wink:

22

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
23

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
24

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:

25

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
26

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

27

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
28

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

29

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.

30

Dont thinks so ... but I dont know everything so could be wrong :wink:

31

Oh well. If you think of anything, let me know. Thanks for the help though.

1 Like
32

See my post in this thread about a solution to ipv6 hostname resolution.

Ronnick

33

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.