Ok, so that makes a bit more sense. My setup I already have the DNS server running outside the cluster - so having to worry about node and cluster IP is not necessary since it's actually running on a public IP right now (ideally will be private later). What I'm reading from @white-piano-73111 is that if I take my deployment, let's say it's a deployment called "wordpress" for the sake of simplicity, and I want the pods for "wordpress" to be able to resolve my own DNS, what I need to do is have that netclient daemonset running already on the cluster nodes, then modify my wordpress deployment to also mount those volumes so that it does whatever magic with resolvectl to make the dns available?