Pihole works only short, before it stops to block ads

The issue I am facing:

**Details about my system:**raspberry pi 4

What I have changed since installing Pi-hole: i dont know

I would recommend getting a debug log token posted (Tools/Generate Debug Log) so the devs here can help you out, while you're waiting anyway.

You have given us very little to work with.

A debug log would be helpful, along with a more detailed description of your problem.

You see ads on all device? Some devices? Only on certain websites or apps?

Sorry it took so long for me and thanks for your response: here is the debuggtoken: https://tricorder.pi-hole.net/CugEjGym/
Here is a better description of my problem:
I tried to set up the raspberry pi on our fritzbox.I had problems so I searched for a solution and found a video, which explained what I should do. Then it worked on my phone with 99% accuracy. Then I tried the same test side on my computer and it didn't work. One hour later it also stopped working on my phone.Perhabs it is Ip6? because I did the test on my computer and I had no positive response then I checked the Recent Queries log and it sort of works but not.It's like random (just know 74% Yesterday 3%) Please help

Now the adblocktest sey 90%

Where are you getting these numbers?

What problems?

1 Like

from this webside:Test Ad Block - Toolz

My pihole didn't work at all, as I set it as a Nas in our system. After the tutorial I changed settings: Never forward non-FQDN A and AAAA queries To not and Never forward reverse lookups for private IP ranges to not. It seems from the Query Types analysis, that my setup of Pihole cant block HTTPS

Your debug log shows Pi-hole is working and blocking:

Feb  2 00:00:03 dnsmasq[3657]: gravity blocked secure-eu.nmrodam.com is 0.0.0.0

But Not propebly somehow HTTPS doesnt get blocked
Perhabs its the reason its blocked randomly

And pihole/Admin also doesnt worked(Not important for me, perhabs it the same reason?)

What do you see if you access http://192.168.178.103/admin/?
Do you see any error message?

yes it is the way i communicate with pihole, but if i put :nslookup pi.hole
in my terminal of my window pc this is the output:
PS C:\Users\Julian> nslookup pi.hole
Server: fritz.box
Address: fd00::9a9b:cbff:fe0b:33

*** pi.hole wurde von fritz.box nicht gefunden: Non-existent domain.

The link workes, its the way I communicate with pihole. thanks for your efforts

It is likely that this device is not using Pi-hole for DNS. Only Pi-hole can resolve that domain name to the Pi-hole IP. From the PC, what is the complete output of the following command:

ipconfig /all

ipconfig /all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : DESKTOP-KQNG7F3
   Primäres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein
   DNS-Suffixsuchliste . . . . . . . : fritz.box

Unbekannter Adapter OpenVPN Wintun:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Wintun Userspace Tunnel
   Physische Adresse . . . . . . . . :
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Unbekannter Adapter LAN-Verbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : TAP-Windows Adapter V9
   Physische Adresse . . . . . . . . : 00-FF-40-17-5F-DC
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physische Adresse . . . . . . . . : 32-C9-AB-9E-D9-59
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 2:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
   Physische Adresse . . . . . . . . : B2-C9-AB-9E-D9-59
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter WLAN:

   Verbindungsspezifisches DNS-Suffix: fritz.box
   Beschreibung. . . . . . . . . . . : Realtek 8822CE Wireless LAN 802.11ac PCI-E NIC
   Physische Adresse . . . . . . . . : 30-C9-AB-9E-D9-59
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   IPv6-Adresse. . . . . . . . . . . : 2003:c9:2f2e:1000:2eba:a17b:86bf:b96e(Bevorzugt)
   Temporäre IPv6-Adresse. . . . . . : 2003:c9:2f2e:1000:c9c7:adad:5c12:7624(Bevorzugt)
   Verbindungslokale IPv6-Adresse  . : fe80::311c:c6f1:2aa6:fa0a%9(Bevorzugt)
   IPv4-Adresse  . . . . . . . . . . : 192.168.178.85(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Freitag, 3. Februar 2023 20:41:07
   Lease läuft ab. . . . . . . . . . : Dienstag, 14. Februar 2023 03:13:56
   Standardgateway . . . . . . . . . : fe80::9a9b:cbff:fe0b:33%9
                                       192.168.178.1
   DHCP-Server . . . . . . . . . . . : 192.168.178.1
   DHCPv6-IAID . . . . . . . . . . . : 607177131
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-2A-CF-A2-67-30-C9-AB-9E-D9-59
   DNS-Server  . . . . . . . . . . . : fd00::9a9b:cbff:fe0b:33
                                       192.168.178.103
   NetBIOS über TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physische Adresse . . . . . . . . : 30-C9-AB-9E-D9-5A
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

What is this DNS server? It is not an IPv6 associated with your Pi-hole.

Its only Ip4 DNS Server, could it be, that i have to Set it up as an Ip6 DNS Server also?

Yes, of course.
The Fritzbox has a setting for IPv4 and ipv6.

This is also valid if your internet provider only support ipv4.

Did you follow the Fritzbox instructions here in the board?