[systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

Itxaka Serrano Garcia itxaka.garcia at spectrocloud.com
Mon Dec 23 13:10:05 UTC 2024


Hallo there!

If using systemd-resolved, cant you just configure the DNS in
/etc/systemd/resolved.conf or /etc/systemd/resolved.conf.d/ directly so it
setups your desired address?
If using any other resolver/network manager, just remove the symlink from
/etc/resolv.conf to the systemd resolv.conf so your resolver creates the
proper file (you probably need that configured as well?)?

Doesn't seem that complex, or we are missing info here to make a proper
suggestion I think?

On Mon, Dec 23, 2024 at 1:23 PM Adam Nielsen <a.nielsen at shikadi.net> wrote:

> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20241223/ee5a79fb/attachment.htm>


More information about the systemd-devel mailing list