Hello, have a question about DNS on my harvester cluster. I’m trying to add my harvester cluster to my rancher deployment. I’ve set the cluster-registration-url in harvester to the url created from my rancher cluster. In rancher the cluster is stuck in a pending state. Looking at the harvester logs i’m seeing the following error message:

2022-08-08T16:18:03.274063754Z time="2022-08-08T16:18:03Z" level=error msg="error syncing 'cluster-registration-url': handler harvester-setting-controller: Get \"<https://kube.blah.dev/v3/import/zvk4bvccqsvrjh5fpck6vm9tzgrbfjvgtgrh4wtq7r9mmtnk7s9l4j_c-m-mzc7k67k.yaml>\": dial tcp: lookup <http://kube.blah.dev|kube.blah.dev> on 10.53.0.10:53: no such host, requeuing"

its seems like harvester is trying to use 10.53.0.10 for DNS lookup? Thats not the DNS server we have configured on the server. any idea why harvester is trying to use that IP for DNS lookup instead of the server/address configured in the /oem/99_custom.yaml file?

harvester is running k8s under the hood, and will be using coredns for dns resolution for the k8s specific workloads like pods.. so that is what is is being passed to the cattle cluster agent

Thanks for the help here. The issue turned out to be with my consul setup. it was not forwarding one of our domains. Fixing the consul issue fixed the issue I was seeing in harvester.

👍