So I'm in the situation now where I'd like to have pods on my cluster that have netclient installed on the node be able to resolve netmaker internal DNS calls. I can do so perfectly fine from in the netclient pod but I want random pod xyz running on the node to also be able to do so. What's the recommended way to do this? Few thoughts, none of which seem super great 1. Specify my nameserver as an upstream nameserver in the kube-system coredns (https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/). The drawback here is that I still want to fall back on other dns for outside calls and it doesn't look like you can set a policy with this that tells the kube-system coredns that you want to try your own nameserver and then fall back to something like 8.8.8.8 when it fails (it looks like if you specify multiple upstream servers it just picks one at random). I guess I can set up that forwarding on the Netmaker server itself in the coredns config alternatively, which would mean I would specify my nameserver in the kubectl coredns, then when my nameserver (the netmaker server) failed to resolve it would forward the call to some public dns like 8.8.8.8 2. Somehow mount the /etc/hosts config from the node into the pod i'm using. Seems error prone and problematic but maybe I'm wrong. 3. Build the image I need this to work on top of the netclient docker image. Seems like a lot of extra work and bloated container to achieve what i'm trying to achieve. 4. Some other type of automation I haven't considered yet?