Answers: <p>There are two main reasons for this issue to happen:</p>
  <ol>
  <li>Your dns are not exposed.</li>
  <li>Your code is redirecting to a https address (and since you are working in your local machine, most likely you don't have a secure certificate)</li>
  </ol>
  <h2>CASE 1 - Exposing DNS</h2>
  <p>On linux you can solve it like:</p>
  <ul>
  <li><p>minikube ip</p>
  </li>
  <li><p>vim /etc/hosts</p>
  </li>
  <li><p>Add the ip from the first step and the hostname you want to expose, and save the file.</p>
  <pre><code># For example
  192.168.39.70   elasticsearch-es-http
  </code></pre>
  </li>
  </ul>
  <p>No need to restart any service, it should work just like that. Add all the hostnames you need.</p>
  <h2>CASE 2 - HTTPS on minikube</h2>
  <p>If your problem is 2, then you have to find a way for you application to not use HTTPS while you are using minikube.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-02-08T20:49:54.167Z
Answers: 2021-02-24T15:14:00.050Z
Answers: 2021-02-24T15:14:00.050Z
Answers: Adrian Lopez
Body: <p>I have the next ingress (output of &quot;kubectl get ingress&quot;)</p>
  <pre><code>NAME   HOSTS   ADDRESS          PORTS   AGE
  main   *       192.168.39.190   80      46m
  </code></pre>
  <p>But when I try to visit that IP address in chrome I get</p>
  <pre><code>Cannot access the website. Check if there's a write error in name.local
  DNS_PROBE_FINISHED_NXDOMAIN
  </code></pre>
  <p>Any idea why? Everything is green on the dashboard, there are errors.</p>
  
Comments: CC BY-SA 4.0
Comments: 2021-02-22T20:56:52.547Z
Comments: Requests that sent directly to an IP address should not trigger a DNS probe, so you are probably using a domain name and it is `name.local` according to your error message. I am also having a hard time when resolving .local domains with chrome recently. It's probably because of secure dns configuration With this config, chrome bypasses your system resolver and sends queries to 3rd party over https. You may want to try to turn off "secure dns" in your google chrome settings.
Comments: yozel
Tags: <kubernetes><ingress><http><minikube>
Title: Ingress ip returns HTTP error DNS_PROBE_FINISHED_NXDOMAIN
UserDisplayName: Adrian Lopez
ThreadText: # Ingress ip returns HTTP error DNS_PROBE_FINISHED_NXDOMAIN
  
  (Asked by: username_0 on 2021-02-08)
  
  I have the next ingress (output of "kubectl get ingress")
  
  ```
  NAME   HOSTS   ADDRESS          PORTS   AGE
  main   *       192.168.39.190   80      46m
  
  ```
  
  But when I try to visit that IP address in chrome I get
  
  ```
  Cannot access the website. Check if there's a write error in name.local
  DNS_PROBE_FINISHED_NXDOMAIN
  
  ```
  
  Any idea why? Everything is green on the dashboard, there are errors.
  
  **Tags:** kubernetes, ingress, http, minikube
  
  > **Comments:**
  > **username_1**: Requests that sent directly to an IP address should not trigger a DNS probe, so you are probably using a domain name and it is `name.local` according to your error message. I am also having a hard time when resolving .local domains with chrome recently. It's probably because of secure dns configuration With this config, chrome bypasses your system resolver and sends queries to 3rd party over https. You may want to try to turn off "secure dns" in your google chrome settings.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2021-02-08. Score: 1
  
  There are two main reasons for this issue to happen:
  
  1. Your dns are not exposed.
  2. Your code is redirecting to a https address (and since you are working in your local machine, most likely you don't have a secure certificate)
  
  ## CASE 1 - Exposing DNS
  
  On linux you can solve it like:
  
  * minikube ip
  * vim /etc/hosts
  * Add the ip from the first step and the hostname you want to expose, and save the file.
  
    ```
    # For example
    192.168.39.70   elasticsearch-es-http
  
    ```
  
  No need to restart any service, it should work just like that. Add all the hostnames you need.
  
  ## CASE 2 - HTTPS on minikube
  
  If your problem is 2, then you have to find a way for you application to not use HTTPS while you are using minikube.
  
  
  ---
  
  