dns timout

[gio-salvador]

Would you have any recommendations for those getting the following response from the DNS queries:

$ kubectl exec -ti $POD_NAME -- nslookup kubernetes
;; connection timed out; no servers could be reached

command terminated with exit code 1

[devopsprosiva]

Replace kubedns with coredns

…

On Sep 3, 2018, at 1:32 PM, Giovanni Salvador ***@***.***> wrote: Would you have any recommendations for those getting the following response from the DNS queries: $ kubectl exec -ti $POD_NAME -- nslookup kubernetes ;; connection timed out; no servers could be reached command terminated with exit code 1 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[omarrayward]

@gio-salvador
Have you tried the solution proposed here.
This issue may be a duplicate

[jonashackt]

@omarrayward is right, it´s just the busybox image is crap - see this fix #384

[strongjz]

I specified the version of busybox to 1.28.4 per this stack overflow and resolution started working for me

strongbad@controller-0:~$ kubectl describe deployment busybox
Name:                   busybox
Namespace:              default
CreationTimestamp:      Mon, 03 Sep 2018 23:04:11 +0000
Labels:                 run=busybox
Annotations:            deployment.kubernetes.io/revision=2
Selector:               run=busybox
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  1 max unavailable, 1 max surge
Pod Template:
  Labels:  run=busybox
  Containers:
   busybox:
    Image:      busybox:1.28.4
    Port:       <none>
    Host Port:  <none>
    Command:
      sleep
      3600
    Environment:  <none>
    Mounts:       <none>
  Volumes:        <none>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   busybox-78c8df6fd7 (1/1 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  43m   deployment-controller  Scaled up replica set busybox-78c8df6fd7 to 1
  Normal  ScalingReplicaSet  43m   deployment-controller  Scaled down replica set busybox-68654f944b to 0
strongbad@controller-0:~$ kubectl exec -it busybox-78c8df6fd7-p9q94 -- nslookup kubernetes
Server:    10.32.0.10
Address 1: 10.32.0.10 kube-dns.kube-system.svc.cluster.local

Name:      kubernetes
Address 1: 10.32.0.1 kubernetes.default.svc.cluster.local

[kelseyhightower]

KubeDNS has been replaced with CoreDNS and all examples have been tested with the new configuration and verified to be working with the latest release of this guide.