I use networkmanager on my laptop. 99%+ of my linux machines are not laptops so I don't need network manager on them. I use dnsmasq on two servers, which has a

I use networkmanager on my laptop. 99%+ of my linux machines are not laptops so I don't need network manager on them. I use dnsmasq on two servers, which has a few local dns entries in its host (either to block lookups for some sites like dailymail.co.uk, or to have an entry for "nas" pointing to 192.168.0.51) and upstreams the rest of the queries. I don't need a forwarder on the other machines on the network, they are told by dhcp to use those two servers when they are on my network, when they're on another network dhcp tells them to use something else. I run syslog on a few servers listening to an anycast device, and syslog fires text to the local machine and that anycast IP. Had a problem last night with a systemd-resolvd server, I'd added an entry to DNS, and it wasn't working. Of course that's because the entry hadn't migrated from the main dns server to the backup one (the cronjob runs every 20 minutes as it has done for over a decade), and systemd decided to use the backup server (which is very rarely used). That costs me time. If I want fancy DNS resolving paths, I can choose to install a fancy forwarder. (For WFH I do have a router I can plug my laptop and other devices like a pi into and everything is forwarded through work, including routes to 0.0.0.0/0. No natting involved. When I bring my VPN up on the road, everything is routed via the VPN (other than the vpn end point obviously). I wouldn't bridge my network normally, why would I bridge it with a VPN?)