Hi. I have

node-local-dns

enabled in the

rke2-core-dns

Helm Chart and it creates the

node-local-dns

Daemonset in my cluster, but if I exec into any pod and look at the

/etc/resolv.conf

it still points to the

10.43.0.10

IP which is the service IP for

core-dns

. My understanding is that it should be

169.254.20.10

. This is how it looks in our existing RKE1 clusters. Not sure if there are structural changes in RKE2's variant that I am unaware of. Any assistance will be appreciated.

it doesn’t change the dns server address… it just runs a local cache pod and adds iptables rules that redirect dns traffic to that pod. this is covered in the docs. https://docs.rke2.io/networking/networking_services#nodelocal-dnscache

Ooohhh okay, so it does not look the same as RKE1, got it. Thanks