Is the 404 page from Traefik or the backend service?
jbloggs777
joined 2 years ago
I'd be surprised if it's still kubedns.. the service name is still kubedns, but there will probably be CoreDNS pods behind it. To debug this, you should first ensure that you can resolve DNS by directly pointing to an external DNS server from a pod, and then from the node if that fails. eg. dig @1.1.1.1 google.com, or host google.com 1.1.1.1. It might be a routing/firewall/nat issue more than DNS, and this would help track that down.
Ok... so your actual issue is with CoreDNS, and you are asking here for a more complicated, custom, untested, alternative?
What is your issue with CoreDNS?
You want to resolve *.cluster.local addresses outside of the cluster/on your LAN, on that domain? This would only be useful if you can route to them... Right?
So... assuming you can route to them, you probably want to configure your powerdns DNS server to forward requests for this zone to the CoreDNS service in the cluster, which should have a static IP.
Puff didn't just live by the sea, apparently.
"Hold my unlocked phone while I chug this beer!"
《criminal mastermind journalist adds himself to confidential chat group》
Lock 'em up! Lock 'em up!
Meanwhile, the flu knocked everyone I know off their feet this year. Our last two covid bouts were mild knocks on wood.
Kalingrad and Belarus are two large areas.
Caesar only got popularised as a tyrant after his death. Trumpy-boy is getting ahead of himself.
Do you have any NetworkPolicies configured that could block ingress (to kubedns, in kube-system) or egress (in your namespace) ? If any ingress or egress networkpolicy matches a pod, it flips from AllowByDefault to DenyByDefault.
You should also do kubectl get service and kubectl get endpoints in kube-system, as well as kubectl get pods | grep -i dns