[Bug] DNS not working #238
Comments
cnsquare
changed the title
|
You may try removing the default |
Still doesn't work. |
|
Looks like a Docker setup issue. Can you ping On what system are you running Docker ? |
|
Ping works, but nslookup fails. I am running Debian 12 (bookworm) |
|
Do you have any firewall running (on the machine or the network) that might affect DNS traffic ? |
|
It's related to running this image on Debian. I launched an Ubuntu server and spawned up this image, and the DNS is functioning properly. When I went back to the Debian server and ran a standard Alpine image, the DNS problem persisted |
|
DNS works on image jlesage/firefox:v1.17.1 but not on any newer tags. |
|
I have the same issue, running Ubuntu 22.04.4 LTS as the host VM. (TL/DR setting dns: 1.1.1.1 in the firefox container docker compose yaml file works) I run 4 instances of pihole on 4 machines locally as DNS servers. One of them, my main one, is in another docker container on the same host. jlesage/firefox:v1.17.1 didn't help. Pihole on my main DNS server is set to use the ports: (following pi-hole/docker-pi-hole#1166) which resolved a few issues I had with other docker containers, but not firefox (which might have worked previously, I don't recall) Here is an example sudo docker exec -ti firefox sh /tmp # nslookup google.com ;; connection timed out; no servers could be reached /tmp # nslookup google.com 1.1.1.1 Non-authoritative answer: Non-authoritative answer: It does work if I use the IP address of my pihole! /tmp # nslookup google.com 192.168.61.5 Non-authoritative answer: Non-authoritative answer: If I set the dns in the firefox yaml docker compose file to 1.1.1.1 (or anything else, including 192.168.61.5), that works. |
|
Something similar happening for me. I can get the container running, i can browse for about 60 seconds, then i get nothing. I can no longer ping google or access any websites after about 60 seconds, but for 60 seconds it appears to work just fine. I have disabled pihole, and i have no other firewall or blocking that should be occurring. my docker-compose The DNS setting and setting anything in /etc/resolv.conf does not seem to make a difference. Now i can ping 1.1.1.1 but i cannot resolve any sites after the first minute or so of running. EDIT: My issues are likely unrelated, when I do not have containers running, my DNS and connectivity everywhere is fine.. When docker IS running after a minute or so it stops working. Unrelated to this project, just noticed it here. |
Current Behavior
DNS not working. I can't access any website with their domain name, but I can with their IP address.
I can ping 142.251.46.206 but can't ping google.com
docker exec -ti firefox sh
/tmp # cat /etc/resolv.conf
Generated by Docker Engine.
This file can be edited; Docker Engine will not make further changes once it has been modified.
nameserver 172.30.40.83
nameserver 172.30.0.1
Based on host file: '/etc/resolv.conf' (legacy)
Overrides: []
/tmp # ping google.com
ping: bad address 'google.com'
/tmp # ping 142.251.46.206
PING 142.251.46.206 (142.251.46.206): 56 data bytes
64 bytes from 142.251.46.206: seq=0 ttl=118 time=64.486 ms
64 bytes from 142.251.46.206: seq=1 ttl=118 time=64.713 ms
64 bytes from 142.251.46.206: seq=2 ttl=118 time=64.450 ms
64 bytes from 142.251.46.206: seq=3 ttl=118 time=64.818 ms
--- 142.251.46.206 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 64.450/64.616/64.818 ms
/tmp #
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Container creation
Docker Image Version: 24.05.1
Container log
The text was updated successfully, but these errors were encountered: