I'll eventually buy another 1 or 2 mini PCs and do proxmox HA clusters, but I'm busy being a nigger.
"Oh, I should also mention, DNS is stupid. Primary and secondary doesn't mean anything. The system does not check for "aliveness" of the dns server, it also does not use the "primary" as the preferred DNS. IF you have a primary and secondary set it will pick one at random, randomly. If the one it picks times out it will try the other one. "
That may be true for windows, but it's definitely not true for Linux. I can watch the pihole query log and see all of my traffic go through there. Also, pihole isn't to block jewgle DNS or cloudflare. You still use them, after the DNS block happens. It fowards all DNS reuqests to an actual DNS server if a block doesn't happen.
TLDR; Not true. Both kind of go retard but in different ways.
Longer version.... Well, in my experience Linux systems are more likely to "pin" to a system it had a successful connection to previously.
If they are following spec, that is basically how dns is (currently) designed.
>The terms "primary" and "secondary" DNS are largely a misnomer when it comes to how operating systems like Windows or Linux actually handle DNS resolution. While DHCP can provide a list of DNS servers, the order in which they are listed does not guarantee a strict priority or failover sequence. For Windows clients, the system typically attempts to query the first DNS server in the list provided by DHCP. If there is no response within a short time frame (often around 1-2 seconds), it will then try the next server in the list. This behavior means that a secondary DNS server is used only after a timeout from the primary, but this is a client-side implementation detail, not a standard requirement. Linux systems, on the other hand, may use DNS servers in a different manner, such as round-robin fashion, depending on the specific implementation and configuration. There is no universal rule dictating the order of DNS server usage across all operating systems. Therefore, while the primary and secondary labels are commonly used in network configuration, they do not enforce a strict hierarchy or guaranteed failover behavior. The actual behavior depends on the client's operating system and its DNS resolver implementation.