<p>I am not able to curl/wget any URL with https. They're all giving connection refused errors. Here's what I've observed so far:</p>

<ol>
<li><p>When I curl any URL with https from any pod, the domain gets resolved to the different IP address than the intended one. I verified this with <code>dig domainname</code> and <code>curl</code>ing the same domainname. Both IP's were different</p></li>
<li><p>For debugging purpose, I tried the same scenario from a kubelet docker container and it worked. But if I tried the same from another app container, it fails.</p></li>
</ol>

<p>Any idea what might be wrong? I am sure, there is some issue with networking. Any more steps for debugging?</p>

<p>The cluster is setup with RKE on bare-metal which uses canal for networking.</p>

<p>The website I am trying to curl is updates.jenkins.io and here's the nslookup output</p>

<pre><code>bash-4.4# nslookup updates.jenkins.io
Server:     10.43.0.10
Address:    10.43.0.10#53

Non-authoritative answer:
updates.jenkins.io.domain.name  canonical name = io.domain.name.
Name:   io.domain.name
Address: 185.82.212.199
</code></pre>

<p>And nslookup from the node gives</p>

<pre><code>root@n4:/home# nslookup updates.jenkins.io
Server:     127.0.1.1
Address:    127.0.1.1#53

Non-authoritative answer:
updates.jenkins.io  canonical name = mirrors.jenkins.io.
Name:   mirrors.jenkins.io
Address: 52.202.51.185
</code></pre>

<p>As far as I can see, it is trying to connect to io.domain.name and not updates.jenkins.io.</p>

<p>Further inspection, all domains ending with .io are causing the issue. Here'a another one:</p>

<pre><code>bash-4.4# nslookup test.io
Server:     10.43.0.10
Address:    10.43.0.10#53

Non-authoritative answer:
test.io.domain.name canonical name = io.domain.name.
Name:   io.domain.name
Address: 185.82.212.199
</code></pre>

Shantanu Deshpande
<p>Well, there was some issue with <code>/etc/resolv.conf</code>. It was missing the correct nameserver entry. Once that was resolved, and the system components were restarted, everything was working.</p>
