Request additional DNS support.
Request additional DNS support.
It wasn't apparent that direct use of 1.1.1.1 by a client device would be impacted by your pihole configuration. The goal should be ensuring all devices route through your pihole, which then handles DNS queries it doesn’t recognize—most of them. To define local hosts in DNS, you’d add them to the pihole, not to your router or other systems directly.
They act as DNS servers handling various tasks. They can support an Active Directory setup. Yes, a pihole can use them as DNS servers, which would then route traffic through Cloudflare.
Choose Pi-hole as your main DNS resolver and 1.1.1.1 as a backup. This ensures connectivity even if Pi-hole fails. For additional routing, add the other IP addresses to Pi-hole's upstream custom fields. Alternatively, set up a Windows Server with DNS roll as primary and configure it as a forwarder, with Pi-hole handling the rest.
The issue lies in how Windows typically uses DNS, whereas routers usually don’t rely on it. They tend to switch between multiple DNS servers to balance the load. A safer approach would be to use a second PiHole for redundancy. However, if the PiHole frequently goes offline, it might not be reliable. In my case, I prefer DNS management through pfSense, which only fails during updates.
As discussed earlier, the issue lies with the router you don’t control and its DNS selection. On Linux systems, things usually become problematic even if a secondary server is available. If you need to use both, consider running a tool that performs many DNS queries to verify consistency and see which server it prefers. I’m still unclear about how the Steam cache fits in—everything should point to the same server for it to function properly.