A combination of Quad9 and OpenDNS, Both have dual-stack support (servers operating on IPv6 and IPv4 addresses) and both can optionally provide a basic level of blocking on known malware domains by filtering the DNS results returned.
I try to avoid relying on a single DNS provider, but if you are a registered user customising their DNS blocking you may need to do this.
I mostly only configure DNS at the network (router or DHCP server) level rather than per device, as I expect devices to request their DNS config from the network (DHCP and/or RDNSS).
When using VPN tunnels to other systems I factor in whether only certain domains should be queried to an remote LAN DNS server over the tunnel such as where it's a private DNS namespace (e.g. Split DNS).
A router or gateway device is often best placed to determine whether a particular DNS query should use a LAN server or forward to an external service or use the root servers, unless you have a dedicated DNS server on your LAN.
Note that indiscriminately setting all your individual devices to use an external DNS service may result in lookups for your LAN hostnames or FQDNs being inadvertently visible to the wider Internet, unless your router filters outgoing DNS requests for private resources.
For similar reasons it's important for users on domain-joined work computers not to mess with their DNS settings as they almost always need to favour domain-controlled DNS services so that internal services resolve correctly and without timeouts.
prlzx on Zen: FTTC (VDSL) at ~40Mbps / 10Mbps
with IP4/6 (no v6? - not true Internet)
Edited by prlzx (Mon 15-Jan-24 20:59:26)