Nameserver Limits Exceeded Warning #190
Replies: 5 comments 4 replies
-
Never come across this but generally speaking to reduce load on CoreDNS I always recommend to install NodeLocal DNS Cache https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/ |
Beta Was this translation helpful? Give feedback.
-
I'm gonna convert this into a discussion since it's not an issue with the tool. |
Beta Was this translation helpful? Give feedback.
-
The cause is due to the netplan, if you look at the path /etc/netplan/50-cloud-init.yaml it configures the IPv6 and also adds two DNS servers. If you look at /etc/resolv.conf you will see that you will have a total of 4 DNS servers, this causes your k3s to emit a constant event indicating that you have exceeded the number of DNS servers. To stop this event, simply edit /etc/netplan/50-cloud-init.yaml by deleting one of the two addresses in the nameservers section and then apply netplan apply. This makes /etc/resolv.conf to be configured correctly. Do you think you can apply this here in your repository? In my case I finally had to use ansible. But if you do it from here it would be better. |
Beta Was this translation helpful? Give feedback.
-
Hello, we hit the same problem.
Regards |
Beta Was this translation helpful? Give feedback.
-
Me too, ubuntu 22.04 |
Beta Was this translation helpful? Give feedback.
-
Nameserver limits were exceeded, some nameservers have been omitted, the applied nameserver line is: 2a01:4ff:ff00::add:1 2a01:4ff:ff00::add:2 185.12.64.2.
kubectl get events -n kube-system
Warning DNSConfigForming pod/coredns-74fb7c7dfd-7wxxf
I don't think anything is wrong because it's a Warning, but I tried to solve it and couldn't. Is it a k3s configuration problem or a hetzner problem or is it something I'm doing wrong?
Does anyone else have this problem?
Beta Was this translation helpful? Give feedback.
All reactions