I use the Pfsense DNS forwarder to forward DNS requests from clients on my network to Pi-hole, Google, and Cloudflare sequentially. The forwarded DNS lookup only times out after more than 100ms (unsure what the actual timeout is). This setting is not configurable in the Pfsense UI. This can lead to a couple of issues:
- Slow network performance when Pi-hole is unavailable
- Failure to pull container images when Pi-hole is unavailable (because the kubelet DNS client timeout is lower than the Pfsense DNS client timeout so it gives up pulling images before the request can be forwarded to an alternate DNS service)
Potential solutions:
- Find a way to configure a smaller timeout for the Pfsense DNS client
- Run some sort of DNS proxy that is more configurable and run that somewhere in the network (but then we are moving the problem from pi-hole unavailable to DNS proxy unavailable)
I use the Pfsense DNS forwarder to forward DNS requests from clients on my network to Pi-hole, Google, and Cloudflare sequentially. The forwarded DNS lookup only times out after more than 100ms (unsure what the actual timeout is). This setting is not configurable in the Pfsense UI. This can lead to a couple of issues:
Potential solutions: