Adding local DNS cache

[danmx]

What I'd like:

So see a local DNS cache (e.g. dnsmasq) baked into the OS image to improve DNS resolution performance.

Any alternatives you've considered:

Adding it to my fork of bottlerocket but it seems like a such generic issue it could be addressed in the source.

[zmrow]

Hi @danmx!

Could you provide more details about your setup? Would you be wanting the DNS cache for the host or for the containers?

[danmx]

My team is looking into setting DNS cache for both OS and containers. The setup should look like this: dnsmasq (running locally) -> NodeLocal (running locally) -> CoreDNS (running remotely)

[chancez]

You can run a local DNS cache in a container and configure your containers to use it pretty easily. One example for running this type of setup on Kubernetes is https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/.

[WilboMo]

Hello! I wanted to check in and see if having DNS cache in containers was sufficient for you or if having DNS cache on the host ended up being a requirement?

[danmx]

In the end I moved to solutions like Istio's DNS sidecar or Cilium's DNS Proxy

[WilboMo]

Thanks for the update, I'm glad to hear you found a solution that works for you. We'll keep this issue open for consideration in future releases.

[ami-descope]

Does 1.28 release added something of DNS or resolver running on the same port 53?

i am running local-node-dns on the cluster and 1.27 was fine but with 1.28 i get

Listen: listen tcp 0.0.0.0:53: bind: address already in use