DNS Resolution
39 incident problems about DNS Resolution. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (39)
LINUX-1364A Fedora host updates cleanly and containerized DNS failsA Fedora host updates cleanly and containerized DNS fails focuses on dns-resolution and asks the reader to isolate the key signal in Linux. Split-DNS failures often come from stale link association inside the resolver, not from ba...LinuxAdvanced14 minProNETWORK-1329A firewall path breaks oversized DNSSEC answersA security hardening change is followed by selective failures against DNSSEC-enabled domains while ordinary resolution remains fine.NetworkIntermediate14 minProNETWORK-1265Manual DNS tests over TCP succeed but real users still failNetwork incident scenario used for structured troubleshooting practice.NetworkIntermediate14 minProNETWORK-1270Manual DNS tests over TCP succeed but real users still failA DNS outage seems cleared after a successful test command, but applications continue failing because they never use the same transport that the operator tested.NetworkIntermediate14 minProNETWORK-1249A manual DNS test succeeds over TCP but real clients still failAn operator proves DNS with one command and later finds the application still cannot resolve names in production.NetworkIntermediate15 minProNETWORK-1254A manual TCP DNS test succeeds but real clients still failAn operator proves DNS with one command and later finds that the application still cannot resolve names in production.NetworkIntermediate15 minProK8S-1296A node becomes Ready but DNS for hostNetwork pods failsA node image update appears safe and later hostNetwork workloads alone begin failing name resolution.KubernetesIntermediate15 minProK8S-1278A pod can reach services by IP but not by nameA monitoring or system pod using hostNetwork starts failing service discovery even though raw IP connectivity is fine.KubernetesIntermediate15 minProNETWORK-1244DNS over TCP passes the manual test but users still failAn operator proves DNS works with one TCP command and later finds the production application still fails every ordinary lookup.NetworkIntermediate15 minProNETWORK-1234DNS over TCP succeeds but ordinary lookups still failOperators validate a DNS query using TCP and wrongly conclude the general resolver path has recovered.NetworkIntermediate15 minProK8S-1272CoreDNS runs but pods resolve external names incorrectlyAn EKS cluster starts returning odd external DNS results after a VPC-level network change, while CoreDNS remains Ready.KubernetesIntermediate16 minProNETWORK-1209Host DNS tests pass but the daemon still uses the old addressA backend IP changes and dig looks right, but one long-running process still talks to the old endpoint.NetworkIntermediate16 minProNETWORK-1219DNS over TCP works but UDP queries still failOperators validate a DNS query successfully over TCP and miss that ordinary client UDP traffic is still blocked.NetworkIntermediate17 minProNETWORK-1185DNS resolution fails only inside containersAn operator validates name resolution on the host and assumes the container will behave the same way, but the runtime resolver path is different.NetworkIntermediate17 minProNETWORK-1203Host DNS works but the proxy process keeps an old resolver view until it reloadsName resolution is fixed at the host level, yet one long-lived process still uses an older resolver state and continues sending traffic to the wrong backend.NetworkIntermediate17 minProNETWORK-1197Load balancer keeps reusing an old backend pathA cutover follows runbook timing, but the edge still uses the old backend because one layer caches the resolution path longer than the service owner assumed.NetworkIntermediate20 minProK8S-1336A pod resolves services on old nodes and times out on fresh nodesA DNS service migration completes and later only pods on newly added nodes see timeouts or stale resolution results.KubernetesIntermediate13 minProK8S-1329A Pod logs DNS timeouts only on fresh nodesA Pod logs DNS timeouts only on fresh nodes focuses on cluster-maintenance and asks the reader to isolate the key signal in Kubernetes. Node-specific DNS failures often point to bootstrap order rather than to cluster-wide resolver health.KubernetesIntermediate14 minProK8S-1301An initContainer loops on DNS for a dependency that already existsA rollout creates both a dependency service and a consuming workload, and only the first few pods never recover from DNS failures.KubernetesIntermediate14 minPro