I believe it's saying your DNS server inside the installation isn't working. I'm still getting familarized with rancher, but udp 53 is DNS, as you've noted this is the key error:
dial tcp: lookup itzg.github.io on 10.43.0.10:53: read udp 10.42.0.72:35627->10.43.0.10:53:
Find out who owns the IP 10.42.0.72 and you will know what is trying to hit the resolver that isn't running on 10.43.0.10
https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/ may be of some use. You could k run busybox --image=busybox & do some nslookup action. IE k exec -it busybox -- nslookup some.address.com
Checkout the Kubernetes docs for sysctls: https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/.
Note that you can add command line arguments to the kubelet for a "rancher launched" cluster by editing the cluster yaml.
The host is optional, I think this wasn't always the case though, so you can do a catch-all ingress for all hosts as a fallback where no host is matched
https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-rules
Your suggestion does not work for Kubernetes, I will copy the answer of a person far smarter than me:
>You might have noticed that so far I've been using the terms "multi-region" and "multi-cluster" essentially interchangeably. Kubernetes is not designed to support a single cluster that spans multiple regions on the wide area network. For quite a while, it wasn't even recommended to have a single cluster span multiple availability zones within a region. The community fought for that capability, and now it is a recommended configuration called a "multi-zone cluster".
>
>But running a single Kubernetes cluster that spans regions is definitely done at your own risk. I don't know anyone who would recommend it. So I'm going to keep using these terms - “multi-cluster” and “multi-region” - mostly interchangeably. If you want to run something like CockroachDB across multiple regions, you are necessarily going to have multiple Kubernetes clusters, at least one in each region.
Source: https://www.cockroachlabs.com/blog/experience-report-running-across-multiple-kubernetes-clusters/