Can you run: $ dig @MASTER_IP -p 53 kubernetes.default.svc.cluster.local
from the host and verify it works? And if so, then try $ dig @MASTER_IP -p 53 www.google.com On Thu, Mar 23, 2017 at 12:35 PM, Rishi Misra <[email protected]> wrote: > Hi there, > > I am having difficulty getting DNS to work on OpenShift 1.4. > > When I start all-in-one server now I get following two messages which I > presume are generated for master and node running on same server: > > /==========================================/ > openshift start > /tmp/openshift.log 2>&1 > > W0323 11:30:52.170724 4883 run_components.go:207] Binding DNS on port > 8053 instead of 53, which may not be resolvable from all clients > I0323 11:30:52.171051 4883 logs.go:41] skydns: ready for queries on > cluster.local. for tcp4://0.0.0.0:8053 [rcache 0] > I0323 11:30:52.171059 4883 logs.go:41] skydns: ready for queries on > cluster.local. for udp4://0.0.0.0:8053 [rcache 0] > I0323 11:30:52.271301 4883 run_components.go:224] DNS listening at > 0.0.0.0:8053 > ...... > > I0323 11:30:53.894747 4883 *node.go:358*] Starting DNS on x.xx.xx.xx:53 > I0323 11:30:53.897994 4883 logs.go:41] skydns: ready for queries on > cluster.local. for tcp://9.23.30.33:53 [rcache 0] > I0323 11:30:53.898003 4883 logs.go:41] skydns: ready for queries on > cluster.local. for udp://9.23.30.33:53 [rcache 0] > I0323 11:30:53.926202 4883 start_master.go:703] Started Kubernetes > Controllers > > /==========================================/ > > How do these two DNS communicate? (8053 and 53) > > However for some reason my pods are unable to resolve services by name (IP > works just fine whether pod ip or external IP). Running these images > directly on Docker also work fine. I have disabled firewall, configured > iptables as per docs to no avail. > > Here is how my pod behaves: > > /=========================================/ > # oc rsh vote-1-0hl7j > root@vote-1-0hl7j:/app# cat /etc/resolv.conf > search votingapp.svc.cluster.local svc.cluster.local cluster.local > nameserver x.xx.xx.xx <---- (This is my server IP where both master and > node are running) > options ndots:5 > > root@vote-1-0hl7j:/app# apt-get update > 0% [Connecting to httpredir.debian.org] [Connecting to security.debian.org > ]^C > root@vote-1-0hl7j:/app# apt-get update > Err http://security.debian.org jessie/updates InRelease > > Err http://security.debian.org jessie/updates Release.gpg > Could not resolve 'security.debian.org' > /=========================================/ > > # netstat -tulpn | grep 53 > tcp 0 0 9.23.30.33:53 0.0.0.0:* > LISTEN 4883/openshift > tcp 0 0 0.0.0.0:8053 0.0.0.0:* > LISTEN 4883/openshift > udp 0 0 0.0.0.0:8053 0.0.0.0:* > 4883/openshift > udp 0 0 9.23.30.33:53 0.0.0.0:* > 4883/openshift > > > > Please let me know what else to look for .. I am pretty sure it has > something to do with DNS but I can't figure out how to debug this further. > I must be missing some config settings. > > Thanks. > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
