Matthew Yeazel

Hello @ami-descope, thanks for opening this issue. The relevant difference between k8s 1.27 and k8s 1.28 on Bottlerocket is that we moved from `wicked` to `systemd-networkd` which includes using `systemd-resolved`...

Just a quick update. I did hear from that internal investigation that they still investigating, but I wanted to confirm with @Pluies if you are still experiencing this or if...

I've done some more investigation and following some basic guidance on [node local dns](https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/) I don't see the same issue as you are seeing on 1.28. This might be due...

From looking at this configuration, I'm pretty sure its the `bind 0.0.0.0` lines in the Corefile config. The main problem is that systemd-resolved is already listening on the loopback interface...

Thanks for the clarification @ami-descope. I think I have the right understanding for the local DNS caching. If believe the docs call out that [the preference for what to bind...

> But the issue is that the port is taken no? The port is only taken for the loopback interface which conflicts with 0.0.0.0 which attempts to bind on all...

Thanks for the extra info @theplatformer, I think this confirms that the local address works and I don't anticipate issues with upgrading to k8s 1.28 and beyond while binding on...

> But the issue is that the port is taken no? > > ``` > My local DNS address is 169.254.20.25 > ``` > > Is that conflicting with resolvd?...

> Hi, @yeazelm thanks in advance. Does `systemd-resolved` serve the same purpose as `node-local-dns` in caching pod DNS queries? Any docs about how the `systemd-resolved` worked? `systemd-resolved` is for host...

Hello @justdan96, it looks like you might be missing the `version = 3` at the top of the file. This cryptic message is a known issue: https://github.com/bottlerocket-os/bottlerocket/issues/2657. What this error...