Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I'm getting DNS_PROBE_FINISHED_BAD_CONFIG after start resolvable container #26

Open
ephillipe opened this issue Jul 13, 2016 · 1 comment

Comments

@ephillipe
Copy link

After get DNS_PROBE_FINISHED_BAD_CONFIG. I need stop resolvable to my DNS work again.

Run resolvable container:

docker run -d \
    --name resolvable \
    --hostname resolvable \
    -v /var/run/docker.sock:/tmp/docker.sock \
    -v /run/systemd:/tmp/systemd \
    -v /run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket \
    mgood/resolvable

Create a container test:

erick.cirrus@pat01550 ~/testedocker $ docker rm -f teste; docker run -it --name teste ubuntu bash
teste
root@ba0ee56c01bf:/#

Ping to new container.

pat01550 testedocker # ping teste.docker
PING teste.docker (172.17.0.3) 56(84) bytes of data.
64 bytes from 49f7ec106ff3 (172.17.0.3): icmp_seq=1 ttl=64 time=0.083 ms
64 bytes from 49f7ec106ff3 (172.17.0.3): icmp_seq=2 ttl=64 time=0.046 ms
64 bytes from 49f7ec106ff3 (172.17.0.3): icmp_seq=3 ttl=64 time=0.036 ms
64 bytes from 49f7ec106ff3 (172.17.0.3): icmp_seq=4 ttl=64 time=0.068 ms
64 bytes from 49f7ec106ff3 (172.17.0.3): icmp_seq=5 ttl=64 time=0.056 ms
^C
--- teste.docker ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3997ms
rtt min/avg/max/mdev = 0.036/0.057/0.083/0.019 ms
@ambreenmoeen
Copy link

Most of the time people face dns_probe_finished_bad_config error that stops them from using web pages, problems with connecting to outside services. This is a DNS related issue and its function is to solve or translate names so when your system is unable to fix or translate the address, you are probably facing this issue. No need to be worried about because here we have the solution for your answer. Solution:
1). Tap Windows key and click R. Now in the run dialog write cmd and press ok.
2). The time you see black command pops up write the following command and press enter ipconfig /flushdns.
3). It will flush dns cache which becomes the reason when there is a change in the DNS and the system is looking up its local cache to take you to the web pages and hold windows key and tap R again.
4). Now write ncpa.cpl and press ok. Now you are taken to the network connections where you are supposed to update DNS settings.
5). Choose properties after identifying your network adapter.
6). Tap the option of Internet Protocol Version 4 (TCP/IPv4) and choose Properties again.
7). Now check on the following dns server addresses and enter the following command for Preferred DNS Server and Alternate DNS Server Preferred DNS SERVER: 8.8.8.8 and Alternate DNS SERVER 8.8.4.4 8). At the end press ok and close all the other windows. In case you want to do it step by step with the help of images you can follow this website https://appuals.com/best-fix-steps-fix-dns_probe_finished_bad_config/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants