No internet on LAN

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

Actual Behaviour:

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] tophotnudeactress.blogspot.si is :: via localhost (::1)
[✗] Failed to resolve tophotnudeactress.blogspot.si via Pi-hole (2603:<redacted>:4500:5ed8:<redacted>:cf8c)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

Debug Token:

[https://tricorder.pi-hole.net/rtuqs4xhg6]

EDIT: Your Pi-hole seems fully operational for IPv4, receiving, filtering and forwarding queries (click for details)
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] jeansporn.blogspot.hk is 0.0.0.0 via localhost (127.0.0.1)
[✓] jeansporn.blogspot.hk is 0.0.0.0 via Pi-hole (192.168.0.21)
[✓] doubleclick.com is 142.250.189.14 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: contents of /var/log
-rw-r--r-- 1 pihole pihole 21345 Jun 25 18:23 /var/log/pihole-FTL.log

   -----tail of pihole-FTL.log------
   [2021-06-25 18:20:07.080 24829M] Imported 53518 queries from the long-term database
   [2021-06-25 18:20:07.084 24829M]  -> Total DNS queries: 53518
   [2021-06-25 18:20:07.084 24829M]  -> Cached DNS queries: 6128
   [2021-06-25 18:20:07.084 24829M]  -> Forwarded DNS queries: 35386
   [2021-06-25 18:20:07.084 24829M]  -> Blocked DNS queries: 11805
   [2021-06-25 18:20:07.085 24829M]  -> Unknown DNS queries: 0
   [2021-06-25 18:20:07.085 24829M]  -> Unique domains: 2625
   [2021-06-25 18:20:07.085 24829M]  -> Unique clients: 18
   [2021-06-25 18:20:07.085 24829M]  -> Known forward destinations: 1

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the wlan0 interface:
   192.168.0.21/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the wlan0 interface:
   2603:8000:ce03:4500:f4e9:66dc:61a7:d7e5 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)

The IPv6 interface identifier for your Pi-hole's host machine has changed.
Also, you've configured Pi-hole for one of your host's public IPv6 addresses (GUA), where the IPv6 prefix is subject to be changed by your ISP also (either regularly or initiated by certain events like power-cycling your router).

If possible, configure your router to distribute an IPv6 ULA prefix as well, and Use IPv6 ULA addresses for Pi-hole.

Regardless whether you are using a GUA, ULA or link-local IPv6 address:
In either case, in order to make Pi-hole aware of a changed address, run

pihole -r

and choose Reconfigure.

1 Like

Hi, Thanks for the help! But I'm currently using pihole DHCP function for my LAN and disabled the DHCP server in router. How can I do ipv6 ULA then? It looks like it can only be done through the DHCP server is that correct?

DHCP is strictly an IPv4 protocol.

The corresponding equivalent for IPv6 is DHCPv6.
Note that it's not a direct match - it is a different protocol in its own right, using different ports.

Even with DHCPv6, it is still your router that would advertise the IPv6 prefixes.

A DHCPv6 server would make use of any such a prefix and assign an IPv6 address by combining such a prefix with an interface identifier (where only the latter is issued by the DHCPv6 server).

You'd still have to configure your router to advertise a ULA prefix.

If your router cannot be configured for that, you could consider to use your Pi-hole host's link-local address. However, note that link-local addresses are only accessible by machines connected to the same link (or network segment) - any L3 switching equipment like L3 switches or additional L3 wifi APs on your network, and clients connecting through those won't be able to access Pi-hole via its IPv6 link-local address.

In such a case, or if you do not feel comfortable with IPv6 yet, you may also consider to disable IPv6 in your router altogether.

1 Like

Hi, I've finally successfully set it up like as you instructed using ULA. Now devices on my network which uses ipv6 are showing that they're using the DNS server from ISP even though I've set the DNS server to be PiHole on my router. And in the query log of PiHole it only shows devices connected using ipv4. On the router's side, the DNS server setting only allows to enter ipv4 address. Also on the devices who're using PiHole as DNS server, I checked the ipv6test.google.com and it says no ipv6. Is it a problem with the router or PiHole setup? There appears no DHCPv6 on my router though. Thanks!

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