just one server can't access coredns IP + 53 Port

33 views
Skip to first unread message

피까추

unread,
Sep 19, 2023, 4:15:34 AM9/19/23
to cni-dev
In a closed-network environment consisting of 32 RHEL 8.4 Linux servers, we are using Kubernetes 1.24.1, CRI-O, Podman, and Calico v3.25.0. Out of these 32 servers, 31 are able to access 10.96.0.10 (via telnet 10.96.0.10 53), but there is one server that cannot access it. Are there any potential reasons for this issue? Additionally, there are no anomalies in the logs for CoreDNS and kube-proxy. Also, upon running the 'calicoctl node status' command on the problematic server, it shows an 'established' status with all other servers.
Reply all
Reply to author
Forward
0 new messages