This message was deleted.
# k3da
adamant-kite-43734
12/11/2025, 6:19 PMThis message was deleted.
b
brainy-yak-5996
12/11/2025, 6:19 PMits as if coredns isn't able to resolve a service, not much helpful in the coredns log:
Copy code
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.override
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.server
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.override
[WARNING] No files matching import glob pattern: /etc/coredns/custom/*.server
repeatedbrainy-yak-5996
12/11/2025, 7:05 PMtried adding a local dns forwarder, but don't see how that's going to help resolve an internal k8s service to resolve
Copy code
$ cat coredns-custom.yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: coredns-custom
namespace: kube-system
data:
dns1.server: |
dns1:53 {
errors
cache 30
forward . redacted
}brainy-yak-5996
12/11/2025, 7:05 PMtried restarting the coredns pod, tried stopping the k3d cluster and starting the k3d cluster, no change
brainy-yak-5996
12/11/2025, 7:28 PMposted in the coredns slack channel, so far no response, but am guessing this is more k3d/k3s related?
brainy-yak-5996
12/11/2025, 7:40 PM Copy code
$ k -n default exec -it dnsutils -- bash
bash-5.0# ping <http://google.com|google.com>
ping: bad address '<http://google.com|google.com>'
bash-5.0# nslookup <http://google.com|google.com>
;; reply from unexpected source: 10.42.0.23#53, expected 10.43.0.10#53
;; reply from unexpected source: 10.42.0.23#53, expected 10.43.0.10#53
;; reply from unexpected source: 10.42.0.23#53, expected 10.43.0.10#53
;; connection timed out; no servers could be reached
bash-5.0# getent hosts argocd-repo-server
bash-5.0#brainy-yak-5996
12/11/2025, 8:50 PMIt almost seems like there isn't internal communication within the cluster, not that dns is failing, but that coredns just can't be reached.
Though ingresses work from the outside ... I don't get it.
brainy-yak-5996
12/12/2025, 5:50 PMI maybe have found the solution, working on it.
brainy-yak-5996
12/12/2025, 5:58 PMadding dns entries to docker and restarting docker fixed it:
/etc/docker/daemon.json
13 Views