@lukass2000 

Sorry, I mistyped. The command was supposed to be:

dig @192.168.10.200 google.com

The @ means it will send the dns to the ip of your pihole. 

And yes, the cache is enabled on your instance of pihole. 

  @lukass2000 

Hello,

now I get the following result

  @lukass2000 

Based on this result, I want to make sure the Pi is on 192.168.10.200? In this response the DNS query was answered by 192.168.10.5

In the meantime, from the site dashboard, follow these steps:
 

Settings > Services > DNS Proxy > check Enable (and enter the Pi details)

  @BLTplays 

I assigned a fixed IP for the Raspberry in Omada and therefore PiHole now has the fixed IP 192.168.10.5 ;)

The DNS setting to change about
Settings > Services > DNS Proxy > check Enable (and enter the Pi details)

I don't think it's that good?
So all traffic is then routed through it, or?
However, only the traffic from one VLAN should be filtered :)
 

@Tescophil 
I do not understand it entirely?

....A better configuration is to set your PiHole's IP Address in your DHCP config. Set up and IP alias on your pihole so it has two UP addresses and use these as the primary and secondary DNS servers under the omada DHCP settings....

Didn't I do it that way?

Seen like that, everything works :)
The only problem is, which is not always used, but occasionally 1.1.1.1 is used as a DNS server,

however, this DNS should only be used if 192.168.10.5 is not available.

Thnaks :)

  @lukass2000 

Like I said, create an IP alias for the Pi so it has two (2) IP address, eg. 192.168.10.5 and 192.168.10.6, then use these as the Primary AND Secondary DNS servers in your DHCP configuration.

Lots of devices round robin between primary and secondary servers.

Some devices use their own DNS if a secondary is not set

Some devices ignore the DHCP settings all together and just use their own (yes Google, I'm looking at you...)

  @Tescophil 

That wouldn't be an advantage.
If the Raspberry fails, the network would be “dead” :(

Therefore, another (external) server should be entered as the secondary DNS, which if the Raspberry fails, intervenes.

 

Glad to see you got it working, I believe the reason pihole is occasionally not used is due to the delay from a first time lookup on the pi. Once it is cached in pihole it will probably beat cloudflare.

  @lukass2000 

If you set an alternate secondary DNS then it's going to get used. possibly up to 50% of the time, so it defeats the object of using network filtering in the first place.

Like I said. don't get hung up on this single point of failure stuff.., your going to have multiple single points of failure in your network anyway... , the router for a start...