Check the egress route and ARP

Show the real source address and interface for a destination; FAILED or INCOMPLETE neighbor entries mean an L2/ARP problem.

ip route get <ip>; ip neigh show | grep -E 'FAILED|INCOMPLETE'

tool
troubleshooting32 commands
tags
troubleshootingnetworkdebug

More troubleshooting commands

  • traceroute -T -p 443 <host>; nc -zv <host> 443

    TCP SYN traceroute gets through ICMP filtering; nc -zv confirms the port is open.

  • curl -sv --resolve <host>:443:<ip> https://<host>/healthz

    Send the request to a specific IP to test a backend while keeping the right SNI and Host header.

  • kubectl run dnsutils --image=tutum/dnsutils -it --rm --restart=Never -- nslookup kubernetes.default

    Start a throwaway pod to resolve a cluster name; this checks CoreDNS and the kube-dns service.

  • dig +short @$(kubectl -n kube-system get svc kube-dns -o jsonpath='{.spec.clusterIP}') <name>.<ns>.svc.cluster.local

    Send the query straight to the CoreDNS clusterIP; with ndots:5, short names cause many extra queries.

  • kubectl -n kube-system get cm coredns -o yaml; kubectl -n kube-system logs deploy/coredns --tail=50

    Check the Corefile (forward, cache) and the latest logs for SERVFAIL and upstream errors.

all 32 troubleshooting commands