<p>I followed this <a href="https://www.techrepublic.com/article/how-to-install-openshift-origin-on-ubuntu-18-04/" rel="nofollow noreferrer">link</a> to install openshift v3 on ubuntu everything works fine, I have two services like this which are pointing to deployment containers. They work fine when I use their ips.</p>
<pre><code>NAME       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
test1   ClusterIP   172.30.98.103    &lt;none&gt;        5055/TCP   22m
test2   ClusterIP   172.30.156.106   &lt;none&gt;        5555/TCP   23m
</code></pre>
<p>but my pods cannot resolve service names, I did not have this problem while using cloud openshift services and as I have read openshift has a built-in dns server (<a href="https://docs.openshift.com/enterprise/3.0/architecture/additional_concepts/networking.html" rel="nofollow noreferrer">Link</a>). Maybe I'm missing something?
Thanks for any help in advance.</p>

Arman Momeni
<p>I found the problem, for anyone reaching here, when I installed openshift after I searched on the internet when my build-configs couldn't pull from github I followed this <a href="https://github.com/openshift/openshift-ansible/issues/5249#issuecomment-659559682" rel="nofollow noreferrer">post</a> which added dns to both nodes and kubedns, after I sshed into pods and checked the /etc/resolv.conf file I figured out the <code>8.8.8.8</code> would come prior to <code>172.30.0.2</code> which was causing the service name not to be resolved. Remove the <code>&quot;dnsIP&quot; : &quot;8.8.8.8&quot;</code> from <code>openshift.local.clusterup/node/node-config.yml</code> if you've added it or find a way to put it below <code>172.30.0.2</code> and problem will be solved.</p>
