title: Docker container is using my host DNS instead of the docker internal DNS
body: <p>I have a docker-compose file that builds two basic application.
  A front-end with angular and a backend with adonis.</p>
  <pre><code>version: &quot;3.9&quot;
  services:
    backend_login:
      build: 
        context: ./apis/apis/login_api
      ports:
        - &quot;3333:3333&quot;
    
    sendit_frontend:
      build: 
        context: ./frontend/frontend/external
      ports:
        - &quot;4500:4200&quot;
      depends_on:
        - api_backend_login
  </code></pre>
  <p>When i run the docker-compose up the two applications go up and they work in their respective ports.
  The problems comes when i call the api from the front-end app using the name of the service (in this case backend_login).</p>
  <p>I attached my terminal to both containers and did a telnet test between them, they seems to work as the y resolve the name and connect to the respective ports</p>
  <p>Finally, i discovered that the front-end app, when is called from firefox, tries to resolve the name using the host dns and not the internal docker dns.</p>
  <p>Now i don't know where is the problem, if it is in the code or in the way that i build the container.</p>
  <p>Edit: I realize that the app is running in the browser of my host machine (i'm a newbie with containers) and obviously it uses my host DNS.</p>
  <p>Is there a way to workaround this?</p>