Issues with DNS configuration on Debian based release

[massimogallina]

I am having issues using the DNS configuration option as per documentation with image kairos-debian-v1.5.1-k3sv1.26.1+k3s1.
Tested with two possible configurations:

stages:
  initramfs:
    - files:
        - path: /etc/systemd/network/10-config.network
          permissions: 0644
          content: |
            [Match]
            Name=enp1s0

            [Network]
            Address=192.168.11.55/24
            Gateway=192.168.11.250
            DNS=192.168.1.181 8.8.8.8

stages:
  boot:
    - name: "Setup dns"
      dns:
        nameservers:
        - 192.168.1.181
        - 8.8.8.8
        path: "/etc/resolv.conf"

In both cases the file /etc/resolv.conf is not created. Instead it is a symbolic link another file (something like run/systemd/resolve/...) that does not exist.

[mudler]

👋 this is due to the fact that systemd-based systems are using systemd-resolved, see also https://wiki.archlinux.org/title/systemd-resolved

[massimogallina]

Yes, this is what I think too. But systemd-resolved is disabled by default on the image.

[sdwilsh]

You should be able to enable it like the docs show for timesyncd as well: https://kairos.io/docs/reference/configuration/#timesyncd

If that works, a PR to update the docs would be great, but a confirmation will help confirm that worked so someone else can come along and update the docs :)

[massimogallina]

I finally had the chance to test it today, but also adding this piece of configuration it does not work:

boot:
    - name: "Enable systemd-resolved"
       systemctl:
         enable:
         - systemd-resolved

[mudler]

@massimogallina try "start" - enable would work only in the initramfs stage which is the earliest, before systemd starts. the boot stage happens later, when the system is full up and running, so you would need to start the service instead.

[mudler]

however, note that a new release is supposed to be out very soon, which should have the following fixed already

[massimogallina]

I have tested it with release 2.0.3 and I can confirm it is fixed.

Thanks,
M