IPv6 and IPv4 at the same time not working

Help Community Help
1

Hi,

thanks for reading.

Expected Behaviour:

I want to be able to use my pihole on sertain devices (not network wide).
I tried to change both my ipv4 and ipv6 dns settings in windows to my pi dns. this should work

Actual Behaviour:

when changing both my ipv4 and ipv6 dns settings to my piholes dns no websites load, including google, netflix or youtube. when i have only one (ipv4 or ipv6) dns configured, it works, but i still see ads everywhere.

Debug Token:

https://tricorder.pi-hole.net/4p34f0bc2q

I hope someone can help me, as ive been stuck for days.

greetings,

Henri006

2

Why? Just use IPv4, any DNS server will happily server A and AAAA records. Having two routes the the same DNS server is going to do nothing but confuse and frustrate you.

3

Because adds still show up everywhere. I read somewhere that google still manages to serve you ads through ipv6

4

How did you install Pi-hole? Did you bypass the OS check?

*** [ DIAGNOSING ]: Operating system
[i] dig return code:  9
[i] dig response:  ;; connection timed out; no servers could be reached
[✗] Distro:  Raspbian
[✗] Error: Raspbian is not a supported distro (https://docs.pi-hole.net/main/prerequisites/)

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] 3820.tm.zedo.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] 3820.tm.zedo.com is 0.0.0.0 via Pi-hole (192.168.178.109)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] aventuras-picantes.com is :: via localhost (::1)
[✓] aventuras-picantes.com is :: via Pi-hole (PUBLIC IP ADDRESSES ARE REALLY BAD TO USE)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

It appears that you have some issues with your LAN.

5

Might be related to the script you are using to modify the database, seems to be rapidly flapping pihole-FTL

*** [ DIAGNOSING ]: contents of /var/log

-rw-r--r-- 1 pihole pihole 73358 Feb 24 17:26 /var/log/pihole-FTL.log
   -----head of pihole-FTL.log------
   [2021-02-24 03:59:37.776 12409M] Reloading DNS cache
   [2021-02-24 03:59:37.777 12409M] Blocking status is enabled
   [2021-02-24 03:59:39.592 12409/T12413] SQLite3 message: file unlinked while open: /etc/pihole/gravity.db (28)
   [2021-02-24 03:59:39.722 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 3 clients in 0.5 msec
   [2021-02-24 07:46:10.065 12409M] Resizing "FTL-queries" from 229376 to (8192 * 56) == 458752 (/dev/shm: 1.1MB used, 978.9MB total, FTL uses 1.1MB)
   [2021-02-24 07:51:20.872 12409M] Resizing "FTL-strings" from 8192 to (12288 * 1) == 12288 (/dev/shm: 1.3MB used, 978.9MB total, FTL uses 1.3MB)
   [2021-02-24 08:05:30.124 12409M] Received: Real-time signal 0 (34 -> 0)
   [2021-02-24 08:05:31.789 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 3 clients in 1.3 msec
   [2021-02-24 08:10:25.429 12409M] Reloading DNS cache
   [2021-02-24 08:10:25.430 12409M] Blocking status is enabled
   [2021-02-24 08:10:27.338 12409/T12413] SQLite3 message: file unlinked while open: /etc/pihole/gravity.db (28)
   [2021-02-24 08:10:27.461 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 3 clients in 0.8 msec
   [2021-02-24 08:12:38.967 12409M] Resizing "FTL-dns-cache" from 12288 to (1024 * 16) == 16384 (/dev/shm: 1.3MB used, 978.9MB total, FTL uses 1.3MB)
   [2021-02-24 08:21:30.593 12409M] Received: Real-time signal 0 (34 -> 0)
   [2021-02-24 08:21:33.925 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 4 clients in 1.2 msec
   [2021-02-24 08:21:41.031 12409M] Received: Real-time signal 0 (34 -> 0)
   [2021-02-24 08:21:42.145 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 4 clients in 1.2 msec
   [2021-02-24 08:21:47.535 12409M] Received: Real-time signal 0 (34 -> 0)
   [2021-02-24 08:21:49.047 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 4 clients in 1.2 msec
   [2021-02-24 08:22:14.448 12409M] Received: Real-time signal 0 (34 -> 0)
   [2021-02-24 08:22:16.085 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 4 clients in 1.2 msec
   [2021-02-24 08:22:27.314 12409M] get_client_groupids("192.168.178.46") - SQL error step: database is locked
   [2021-02-24 08:22:27.315 12409M] ERROR: Gravity database not available, assuming domain is not whitelisted
   [2021-02-24 08:22:27.315 12409M] get_client_groupids("192.168.178.46") - SQL error step: database is locked
   [2021-02-24 08:22:27.315 12409M] ERROR: Gravity database not available, assuming domain is not blacklisted
   [2021-02-24 08:22:27.315 12409M] get_client_groupids("192.168.178.46") - SQL error step: database is locked
   [2021-02-24 08:22:27.315 12409M] ERROR: Gravity database not available, assuming domain is not gravity blocked
   [2021-02-24 08:22:28.170 12409M] Received: Real-time signal 0 (34 -> 0)
   [2021-02-24 08:22:29.673 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 4 clients in 1.2 msec
   [2021-02-24 08:22:59.049 12409M] Received: Real-time signal 0 (34 -> 0)
   [2021-02-24 08:23:00.487 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 4 clients in 1.2 msec
   [2021-02-24 08:23:09.419 12409M] Received: Real-time signal 0 (34 -> 0)
   [2021-02-24 08:23:13.500 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 4 clients in 1.2 msec
   [2021-02-24 08:23:40.586 12409M] Received: Real-time signal 0 (34 -> 0)
   [2021-02-24 08:23:41.910 12409/T12413] Compiled 0 whitelist and 0 blacklist regex filters for 4 clients in 1.2 msec
6

i installed it on Raspberry Pi OS Lite. i used the linustechtips guide to get me further.
before installing pihole i made sure to do sudo apt upgrade. when installing Pihole i indeed got some error, which got fixed by bypassing the oscheck.
should i install another os?
I just connected my pi straight to my modum using an ethernet cable (also already tried multiple cables, first one was broken). so i cant see why there is a problem with it.

7

to be honest i have no clue what that flapping means. any tips on how to resolve?
I have only added a whitelist and adlist to the pi, and added ipv6 google dns upstreams

8

Then you have an OS level problem that needs to be resolved.

9

Did you use some script to add the whitelists? Like GitHub - anudeepND/whitelist: A simple tool to add commonly white listed domains to your Pi-Hole setup. ?

10

yes i have used that exact one

11

Then you'll need to ask them for support.

1 Like
12

okay thank you!

15

alright,

the following fixed it. it is some problem with my provider.

dutch:
" jep. ik gebruik echt een Pi, met Rapbian. Lijkt me niet dat dat verschil uitmaakt.

Op de Fritz heb ik bij home network-->overview-->settings-->IPv4addresses en ipV6addresses de IP's van de Pi-Hole ingegeven als local DNS. Wellicht wist je dit al, maar ten overvloede: dit moet je dus niet doen bij Internet-->account information-->DNS server. Dat gaat niet werken.

Op de Pi heb ik de Ipv4 en Ipv6 adressen van de Fritz ingegeven , bij custom 1 en custom 2 beide 192.168.178.1 en bij custom3 en 4 de bijbehorende ipv6

Er vormt zich geen loop. De fritz herkent DNS queries afkomstig van de Pi en stuurt die door naar upstream via een andere poort. Zie ook dit artikel

ik heb niet gekeken hoe de query op het lokale netwerk wordt verwerkt tot aan de fritz, wat betreft gebruikte poorten

dus: -->Fritz(lokaal)-->Pi-hole-->Fritz-->Upstream -- en weer terug"

english:
"ep. I'm really using a Pi, with Rapbian. Doesn't seem to make a difference to me.

On the Fritz I entered the IP's of the Pi-Hole as local DNS at home network -> overview -> settings -> IPv4addresses and ipV6addresses. You may already know this, but unnecessarily: you should not do this at Internet -> account information -> DNS server. That is not going to work.

On the Pi I entered the Ipv4 and Ipv6 addresses of the Fritz, at custom 1 and custom 2 both 192.168.178.1 and at custom3 and 4 the corresponding ipv6

No loop forms. The fritz recognizes DNS queries from the Pi and forwards them upstream via a different port. See also this article

I have not looked at how the query on the local network is handled up to the fritz, in terms of ports used

so: -> Fritz (local) -> Pi-hole -> Fritz -> Upstream - and back again"

Im posting this so that other people may find this solution

16

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