> Thanks Daniel, that has been my work-around, a systemd timer checking > for 127.0.0.53 and doing a sed on /etc/resolv.conf > > So I came here looking for a more "official" work-around, e.g. some > config file param I missed. > > But it looks like there isn't, so I guess I'll just leave my > work-around in place. Maybe something to add in a future release ? :) But what's the underlying issue? Maybe there's a different fix? Have a read of "Pounding a Nail: Old Shoe or Glass Bottle?"[1]. It's a bit harsh, but it sounds like this is the type of question you might be asking. You mentioned DNSSEC causing you problems, so perhaps disabling that could help, for example. But without knowing the real underlying problem you're trying to solve, there's no way to offer any better solutions. Cheers, Adam. [1]: https://asp-blogs.azurewebsites.net/alex_papadimoulis/408925