Bird
0
0

You run nslookup myservice inside a pod but get 'connection timed out'. What should you check first?

medium📝 Troubleshoot Q7 of 15
Kubernetes - Services
You run nslookup myservice inside a pod but get 'connection timed out'. What should you check first?
AIf the pod's image is up to date
BIf the service has endpoints
CIf the pod's DNS policy is set correctly
DIf the pod has enough CPU resources
Step-by-Step Solution
Solution:

  1. Step 1: Understand DNS timeout cause

    A timeout usually means the pod cannot reach the DNS server.

  2. Step 2: Check pod DNS policy

    If the pod's DNS policy is misconfigured, DNS queries fail, causing timeout.

  3. Final Answer:

    If the pod's DNS policy is set correctly -> Option C

  4. Quick Check:

    DNS timeout often due to DNS policy issues [OK]
Quick Trick: Check pod DNS policy first on DNS timeouts [OK]
Common Mistakes:
  • Checking service endpoints before DNS config
  • Assuming CPU or image issues cause DNS timeout
  • Ignoring pod network settings

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Namespaces - Resource quotas per namespace - Quiz 15hard Namespaces - Creating custom namespaces - Quiz 13medium Namespaces - Default namespaces overview - Quiz 8hard Pods - Sidecar container pattern - Quiz 11easy Pods - Pod lifecycle states - Quiz 12easy Pods - Viewing Pod details and logs - Quiz 4medium ReplicaSets and Deployments - Desired replicas vs actual replicas - Quiz 12easy kubectl Essential Commands - kubectl apply vs create - Quiz 2easy kubectl Essential Commands - kubectl exec for container access - Quiz 13medium kubectl Essential Commands - kubectl exec for container access - Quiz 5medium