coredns can't resolve domain

[lvs071103]

deploy setup:

./deploy.sh -s -r 10.254.0.0/16 -i 10.254.0.2 -d clouster.local > coredns.yaml
kubectl create -f coredns.yaml
kubectl get pods,svc -n kube-system 
NAME                           READY   STATUS    RESTARTS   AGE
pod/coredns-55c956c95c-2k928   1/1     Running   0          10h
pod/coredns-55c956c95c-d685d   1/1     Running   0          10h

NAME               TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)         AGE
service/kube-dns   ClusterIP   10.254.0.2   <none>        53/UDP,53/TCP   10h

another pod can't resolve domains, for example:

[root@k8s-master ~]# kubectl get pods,svc --all-namespaces
NAMESPACE     NAME                           READY   STATUS    RESTARTS   AGE
default       pod/nginx-774d74897-47zbm      1/1     Running   0          11h
default       pod/nginx-774d74897-jt6rj      1/1     Running   0          11h
default       pod/test-dns-d854db9-8s8w9     1/1     Running   1          10h
kube-system   pod/coredns-55c956c95c-2k928   1/1     Running   0          10h
kube-system   pod/coredns-55c956c95c-d685d   1/1     Running   0          10h

NAMESPACE     NAME                      TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)         AGE
default       service/example-service   NodePort    10.254.139.43   <none>        80:30163/TCP    11h
default       service/kubernetes        ClusterIP   10.254.0.1      <none>        443/TCP         16h
kube-system   service/kube-dns          ClusterIP   10.254.0.2      <none>        53/UDP,53/TCP   10h
[root@k8s-master ~]# kubectl exec -it test-dns-d854db9-8s8w9 /bin/sh
/ # nslookup kubernetes.default
Server:		10.254.0.2
Address:	10.254.0.2:53

** server can't find kubernetes.default: NXDOMAIN

*** Can't find kubernetes.default: No answer

/ # nslookup kube-dns
nslookup: write to '10.254.0.2': Connection refused
;; connection timed out; no servers could be reached

/ # nslookup example-service
Server:		10.254.0.2
Address:	10.254.0.2:53

** server can't find example-service: NXDOMAIN

*** Can't find example-service: No answer

my deployment method correct?

[chrisohaver]

./deploy.sh -s -r 10.254.0.0/16 -i 10.254.0.2 -d clouster.local > coredns.yaml

"clouster.local" looks like a typo.

[lvs071103]

change to cluster.local, but still not resolve

# kubectl exec -it dnstools -- /bin/sh
dnstools# nslookup example-service
;; connection timed out; no servers could be reached

[chrisohaver]

You’re getting inconsistent results, sometimes a timeout, sometimes an answer (NXDOMAIN) which implies network connectivity issues, perhaps only on some nodes or between nodes. There are two coredns replicas by default, and it’s possible that your client pod (dnstools) may have a route to one but not the other depending on which nodes they get scheduled on. On Nov 22, 2018, at 9:59 AM, zhoufurong <notifications@github.com<mailto:notifications@github.com>> wrote: change to cluster.local, but still not resolve # kubectl exec -it dnstools -- /bin/sh dnstools# nslookup example-service ;; connection timed out; no servers could be reached — You are receiving this because you commented. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_coredns_deployment_issues_111-23issuecomment-2D441055057&d=DwMCaQ&c=CWsWqoUynJrLESJQduOsxQ&r=fqtOgeJR6kXT8siDsioK_cuszjJxxWjoOLsT1wkHy5k&m=wSf0HenNgRzyfcZ9izoYs4Lo74gDP3eNw8qCeJKhmYc&s=Dqd2-7TP4UEVoa_zH6owOE-syK9ciLv9uY0x_QHvCqs&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ANq-2DNVoebSVuYUT2cSTvJWxvw6LrCHzCks5uxru6gaJpZM4YsSq-5F&d=DwMCaQ&c=CWsWqoUynJrLESJQduOsxQ&r=fqtOgeJR6kXT8siDsioK_cuszjJxxWjoOLsT1wkHy5k&m=wSf0HenNgRzyfcZ9izoYs4Lo74gDP3eNw8qCeJKhmYc&s=d7sLx-L4HuZ3-ChhS4jnFqwRCmnuBX17mxN-QJtdXXE&e=>.

[lvs071103]

cool, internal is OK! thanks a lot

# kubectl run -it --rm --restart=Never --image=infoblox/dnstools:latest dnstools
If you don't see a command prompt, try pressing enter.
dnstools# nslookup example-service
Server:		10.254.0.2
Address:	10.254.0.2#53

Name:	example-service.default.svc.cluster.local
Address: 10.254.26.98

[lvs071103]

public cloud is not OK! I will continue try, thank you

[Davidrjx]

@chrisohaver hi, i am facing same problem but both internal & external domain do not work