Problem with no Hostnames and less blockings

[Timi]

Hello I'm new in the Pihole Business,

I started weaks ago with a RPI4 and a local installation. That works fine.
Yesterday I started with a new Image and installed Portainer and Pihol on it.

I don't know If the Pihole is working fine, I think I see more advertising as with my old setup.(Imported all Settings via Teleporter)

Sometimes I get this Error:
pihole maximum number of concurrent dns queries reached (max 150)

And see below for some Clients the Pihole show no Hostname.

Actual Behaviour:

Debug Token:

https://tricorder.pi-hole.net/5LpubgJc/

Can someone have a look?

Thanks in advance

[Timi]

no one can help?

[Bucking_Horn]

Your debug log shows your Pi-hole container to be operational.

Run from a client machine in your network, please share the output of the following commands (preferably as text):

nslookup pi.hole

nslookup flurry.com

[Timi]

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

PS C:\Users\dennwer> nslookup pi.hole
Server:  fritz.box
Address:  fd00::<redacted>a8

*** Keine internal type for both IPv4 and IPv6 Addresses (A+AAAA)-Einträge für pi.hole verfügbar.

PS C:\Users\dennwer> nslookup flurry.com
Server:  fritz.box
Address:  fd00::<redacted>a8

I don't know why but all Querys runs via Fritzbox not on every client self. (Settings in the Fritzbox are the same as the onprem install of pihole)

When I activate CF DHCP (FritzBox) the Hostnames were shown.

[Bucking_Horn]

Your FritzBox router propagates its own IPv6 address as DNS server.

Since the request for pi.hole is not answered with Pi-holes IP addresses, the FB obviously is neither using Pi-hole as upstream DNS server.

In that scenario, your client is by-passing Pi-hole completely, which would match your observation of less blocking.

You may want to refer to Fritz!Box (DE) - Pi-hole documentation for configuration recommendations.
To avoid IPv6 by-passes, you may also have a look at Unresolved ipv6 adress in my top list - #4 by Bucking_Horn.

If your other observation of maximum number of concurrent dns queries would still reoccur once you've settled for a clean router configuration, feel free to provide a fresh debug token.

[Timi]

I don't want to use IPV6, in my fritzbox is only IPV4 configured. Is there a other option?

[Bucking_Horn]

Please have a thorough read through the links I've provided above.

Your nslookup results clearly show that your FB is advertising its own IPv6 address as local DNS server.

You'll find the necessary steps to stop it from doing so in the second link.

[Timi]

PS C:\Users\dennwer> nslookup pi.hole
Server: raspberrypi.fritz.box
Address: 192.168.178.59

Name: pi.hole
Address: 0.0.0.0

PS C:\Users\dennwer> nslookup flurry.com
Server: raspberrypi.fritz.box
Address: 192.168.178.59

Name: flurry.com
Addresses: ::
0.0.0.0

https://tricorder.pi-hole.net/yrocPfpw/

And I get this error

[Bucking_Horn]

That's looking better.

Your nslookups now show that your client is using your Pi-hole at 192.168.178.59 for DNS, and that Pi-hole is blocking flurry.com.

Your Pi-hole container isn't aware of its host's IP address yet.
You should set that container's recommended environment variable FTLCONF_LOCAL_IPV4 to 192.168.178.59.

As for the maximum number of concurrent dns queries:
Those are most often seen as a result of a DNS loop.
As your Pi-hole is using your FB as upstream, would your FritzBox perhaps be using Pi-hole as upstream as well?

Please share a screenshot from your router's upstream configuration from Internet/Zugangsdaten/DNS-Server.

[Timi]

@Bucking_Horn

FTLCONF_LOCAL_IPV4

Thanks

[Bucking_Horn]

Your FritzBox is indeed using Pi-hole as its upstream, which in turn would close a full DNS loop.
What's your intention for that?

As your previous nslookup results show that your FB is already distributing Pi-hole's IPv4 as local DNS server, your clients would use Pi-hole for DNS as soon as they acquire a fresh DHCP lease from your FB.
This would allow you to switch your FB upstream DNSv4-Servers to some public resolvers.

[Timi]

Sorry my fault, I set it to the default of my provider. Thank you for your help

[Timi]

After nearly 2 week, it seems that there is no query reset every 7 days. On my onprem installation it was the default.

Do you have a idea for that?