Re: [systemd-devel] enable systemd-resolved in early boot (dracut)

2024-03-30 Thread Aleksandar Kostadinov
Thanks a lot! It worked like a charm. Because I didn't use systemd-networkd I had to add it manually $ cat /etc/dracut.conf.d/resolved.conf add_dracutmodules+=" systemd-resolved " Now mdns resolution works during early boot (clevis vs tang). On Thu, Mar 21, 2024 at 3:51 PM Andrei Borzenkov wrot

Re: [systemd-devel] enable systemd-resolved in early boot (dracut)

2024-03-21 Thread Andrei Borzenkov
On Thu, Mar 21, 2024 at 4:44 PM Cristian Rodríguez wrote: > > On Tue, Mar 19, 2024 at 7:44 AM Aleksandar Kostadinov > wrote: > > > > Hello, > > > > I want to enable systemd-resolved in early boot so that `clevis` can > > resolve `tang` address by mdns. This will simplify local network > > configu

Re: [systemd-devel] enable systemd-resolved in early boot (dracut)

2024-03-21 Thread Cristian Rodríguez
On Tue, Mar 19, 2024 at 7:44 AM Aleksandar Kostadinov wrote: > > Hello, > > I want to enable systemd-resolved in early boot so that `clevis` can > resolve `tang` address by mdns. This will simplify local network > configuration by not relying on static IP addresses. > > But it seems that is not en

Re: [systemd-devel] enable systemd-resolved in early boot (dracut)

2024-03-19 Thread Daan De Meyer
Hi Aleksandar, > I want to enable systemd-resolved in early boot so that `clevis` can > resolve `tang` address by mdns. This will simplify local network > configuration by not relying on static IP addresses. > But it seems that is not enabled by default. > Is there a way to tell dracut to also i

[systemd-devel] enable systemd-resolved in early boot (dracut)

2024-03-19 Thread Aleksandar Kostadinov
Hello, I want to enable systemd-resolved in early boot so that `clevis` can resolve `tang` address by mdns. This will simplify local network configuration by not relying on static IP addresses. But it seems that is not enabled by default. Is there a way to tell dracut to also include and start `