Always private
DuckDuckGo never tracks your searches.
Learn More
You can hide this reminder in Search Settings
All regions
Argentina
Australia
Austria
Belgium (fr)
Belgium (nl)
Brazil
Bulgaria
Canada (en)
Canada (fr)
Catalonia
Chile
China
Colombia
Croatia
Czech Republic
Denmark
Estonia
Finland
France
Germany
Greece
Hong Kong
Hungary
Iceland
India (en)
Indonesia (en)
Ireland
Israel (en)
Italy
Japan
Korea
Latvia
Lithuania
Malaysia (en)
Mexico
Netherlands
New Zealand
Norway
Pakistan (en)
Peru
Philippines (en)
Poland
Portugal
Romania
Russia
Saudi Arabia
Singapore
Slovakia
Slovenia
South Africa
Spain (ca)
Spain (es)
Sweden
Switzerland (de)
Switzerland (fr)
Taiwan
Thailand (en)
Turkey
Ukraine
United Kingdom
US (English)
US (Spanish)
Vietnam (en)
Safe search: moderate
Strict
Moderate
Off
Any time
Any time
Past day
Past week
Past month
Past year
  1. stackoverflow.com

    Since using 127.0.1.1 within docker doesn't work, docker falls back to Google's public DNS, which do not work either. There may be several reasons why DNS is broken within docker containers. This question (and answers) covers the case where: dnsmasq is used. To check whether this is the case: Run ps -e | grep dnsmasq on the host. If the output ...
  2. forums.docker.com

    Hi, I am using docker v24 on ubuntu 22.04, and everything was working for a year until recently. The dns resolution broke down on containers that use default bridge network. The host network, and a newly created custom bridge network also work as expected. Any container starting on default bridge, will not resolve any dns.
  3. forums.docker.com

    Execute nslookup miniwin - This is the friendly name we gave the container and will be used to create a DNS lookup to Docker's embedded DNS server; ... If you receive a timeout response, then DNS requests are not working and this may be your issue. 2. Is the "Apply local firewall rules" group policy setting set to "No" on my computer?
  4. serverfault.com

    If it is a DNS resolver problem, here is the solution: First thing to check is run cat /etc/resolv.conf in the docker container.If it has an invalid DNS server, such as nameserver 127.0.x.x, then the container will not be able to resolve the domain names into ip addresses, so ping google.com will fail.. Second thing to check is run cat /etc/resolv.conf on the host machine.
  5. forums.docker.com

    I am upgrading my host linux system, but suddenly, my containers just can NOT connect to others or outside by name. Here is the command results of my debug: $ docker network inspect -f '{{range .Containers}}{{.Name}} {{end}}' t2_proxy containerA containerB $ docker exec containerA ping containerB -c2 ping: bad address 'containerB' $ docker inspect -f '{{.NetworkSettings.Networks.t2_proxy ...
  6. superuser.com

    I'm finding this problem really frustrating since I've not found a way to solve it. I'm attaching for completeness a cat /etc/resolv.conf of both the machine running docker and the container itself. On the machine with CentOS 8: [server@localhost ~]$ cat /etc/resolv.conf # Generated by NetworkManager nameserver 8.8.8.8 nameserver 8.8.4.4
  7. stackoverflow.com

    I have the same problem. I am using the pihole/pihole docker container as the sole dns server on my network. Docker containers on the same host as the pihole server could not resolve domain names. I resolved the issue based on "hmario"'s response to this forum post.. In brief, modify the pihole docker-compose.yml from:--- version: '3.7' services: unbound: image: mvance/unbound-rpi:1.13. ...
  8. devops.stackexchange.com

    dns: <DNS server IP> Turns out the docker container attempts to get DNS responses from the gateway configured in the network that compose generates, and for some reason only gets "server failed" responses. Conversely, docker run just grabs the hosts DNS config which is why that works. Why only my windows containers are affected, i do not know.
  9. Can’t find what you’re looking for?

    Help us improve DuckDuckGo searches with your feedback

  1. A clean solution is to configure docker+dnsmasq so than DNS requests from the docker container are forwarded to the dnsmasq daemon running on the host.

    For that, you need to configure dnsmasq to listen to the network interface used by docker, by adding a file /etc/NetworkManager/dnsmasq.d/docker-bridge.conf:

    $ cat /etc/NetworkManager/dnsmasq.d/docker-bridge.conf
    listen-address=172.17.0.1

    Then restart network manager to have the configuration file taken into account:

    sudo service network-manager restart

    Once this is done, you can add 172.17.0.1, i.e. the host's IP address from within docker, to the list of DNS servers. This can be done either using the command-line:

    $ sudo docker run -ti --dns 172.17.0.1 mmoy/ubuntu-netutils bash
    root@7805c7d153cc:/# ping www.example.com
    PING www.example.com (93.184.216.34) 56(84) bytes of data.
    64 bytes from 93.184.216.34: icmp_seq=1 ttl=54 time=86.6 ms

    ... or through docker's configuration file /etc/docker/daemon.json (create it if it doesn't exist):

    $ cat /etc/docker/daemon.json                      
    {
      "dns": [
        "172.17.0.1",
            "8.8.8.8",
            "8.8.4.4"
      ]
    }

    (this will fall back to Google's public DNS if dnsmasq fails)

    You need to restart docker to have the configuration file taken into account:

    sudo service docker restart

    Then you can use docker as usual:

    $ sudo docker run -ti mmoy/ubuntu-netutils bash
    root@344a983908cb:/# ping www.example.com
    PING www.example.com (93.184.216.34) 56(84) bytes of data.
    64 bytes from 93.184.216.34: icmp_seq=1 ttl=54 time=86.3 ms

    --Matthieu Moy

    Was this helpful?
Custom date rangeX