coredns can't resolve domain about deployment

[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 <[email protected]<mailto:[email protected]>> 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