@ZoloNN For me that LAN-DNS worked better than all other DNS services, especially PI-Hole and AdGuard home had such a delay that watching Discovery+ was not working shutter free on my smart TVs. I get what you mean by redundancy but, to my experience Synology's power supplies break way more often than e.g. the ones of a network switch.. so if there is a redundant function, it would be great though.

Hi @Julian2111,

the streaming problem with piHole is quite strange. Streaming doesn't require repeated DNS querying.....

My setup is:

Via DHCP are my two AD integrated DNS servers assigned for clients. They resolve local fixed IPs and dynamic ones which are able to register itself (windows clients)

If not resolved, request is forwarded to one of two piHole instances (Debian VM on ESX) looks in cache first, then in blacklist and when not found, the request is forwarded to locally (on the same VM) installed unbound, configured to use root hints instead of ISP DNS. What means, unbound has to ask root hints server for authoritative DNS, where he can ask for final answer.

btw: unbound is natively running on Omada routers, but is configured as forwarder relying on ISP DNS servers (or any upstream server) and you can fill the static part via LAN-DNS feature.

Have done some tests in my setup now, never got over 100ms for a query.... And I have no problems with streaming (using Amazon Fire sticks 4K)

  @ZoloNN I will try that, my NAS and PC running these DNS software always had static IPs not dynamic ones, not even over DHCP since the though is if something breaks they can be reachable still (the IP is of course reserved in the routers DHCP server).

btw. Interesting fact with unbound.

Thanks for your help I will try that out 

Hi @Julian2111,

I use fixed addresses for my VMs, and any infrastructure stuff.

Using fixed IPs for all devices makes IP address management extremely difficult, needs manual intervention for each new device.

I use DHCP for all clients, mobile phones, IoT devices, etc.... It's much more easier to manage the IP address space - and you can centrally push in bulk lot of additional network parameters to clients, e.g. parameters for BOOTP, additional static routes, etc....

  @ZoloNN That is how I do it as well besides for the controller and my core nas obviously. Fixed over the DHCP server