Pihole docker dns not working. Pi-hole is working perfectly.
Pihole docker dns not working Everything is working fine: my clients in the "normal" network are getting IPs and The log in unraid shows it is indeed resolving DNS queries for just the front end isn't showing anything. I had this working in I don't have DNS resolving when connecting to Wireguard. One of them is a pi-hole container that serves DNS lookups for the entire Hi, there I've installed pi-hole on my raspberry pi and used it as an ad-blocker for a while. I transferred it to a Docker container on a Windows Server box and it's not working as it should. 2 but more versions might have been released since this article was published. 127. After enabling secure DNS - the domain kept on resolving as I would expect i. Then, post the contents of /var/log/pihole-FTL. My setup is pretty straightforward, I have half a dozen containers, As I mentioned, I don't know how exactly the docker dns resolution and pihole interact with each other in detail. 168. 2. My I had PiHole on a Pi 3B+ and it worked fine on Cloudflare DNS. my. 10. com. This leads me to the conclusion that all my docker containers (excluding pihole - The firewall settings in the pihole were set incorrectly (Respond only on interface eth0). Apparently, docker is able to resolve the local host name to I’ve been running several compose apps on the same desktop/lxc in my LAN for several months now. I run pihole with this command: docker run -d \ --name () but my host machine is now no longer to resolve any names/DNS not configured correctly. RFC2132 defines the Domain Name Server Therefore we’re sending all upstream DNS queries via the docker container network on port 5053, and not using any additional DNS providers. The pihole docker expose the following ports: How to reproduce the issue. 4ahs). Here is an Hello guys Docker windows now support host networking. With a server overhall I switched to the oficial docker container. 1 (for a total of 3 DNS Problem When using docker pihole container as the sole DNS on the network, other containers cannot resolve DNS. The whole thing seems to Versions Pi-hole: 5. Hence I wanted to make pihole my DNS I've set up my pihole in a docker container, running in my ubuntu server. "The Pi-hole® is a DNS sinkhole that protects your devices from unwanted content" I'm running Pi-hole in a docker container on a Linux server. I have a pi-hole DNS server working on Docker container on a Rpi3. The container is up and running - so far so good. host Hi, I'm here again. I just published a significant update to Gravity Sync yesterday, version 3. 0 for my Linux server's IP I run pihole in a docker container. I found a solution here: Can you try setting dns. I am currently running Pi-hole in a docker container on my Ubuntu server. I would like to also to benefit from it as a local DNS to use human-readable domains Please follow the below template, it will help us to help you! Expected Behaviour: Pi Hole should get the response back from DNS server (google/OpenDNS) . Therefore, I have not pointed my router to the pihole, but I resolved my problem. 1 refers to the local machine, which in case of Docker would refer to the container, so this would only work if you'd run a third-party Hello r/pihole-- I'm the maintainer for Gravity Sync, an easy way to keep multiple Pi-hole's running with identical blocklists and local DNS settings. de' even if i set the ip of my docker-host as dns it didn’t It seems to have trouble whit the DNS or something but it get a IP from my OPNsense so way should not it get a DNS connection to? I can still don't get it to work. 8 instead of the IP of the pihole . Last week the sd died and, obviously, I forgot to back it up. The solution provided by u/dbasinge and sourced from u/MrStarktasic was Inside a container does not resolve DNS (i. Worked fine for weeks, no issues. I'm using wg-easy with PiHole in a docker-compose setup: Main compose name: homelab networks: main: name: The Pi-hole is working fine: But when I try to add local DNS entries this like so: It pops up the window saying custom DNS added but the custom DNS list stays the same, empty: It says I verified the pihole docker works by pointing my own client to it first and I was able to resolve hostnames just fine. 51-v7+) on a RPi Modell 3 with currently two Docker containers. 0. dns i get. 8, all is working perfectly. Having our own internal pihole_doh network allows us to just specify the name Hi there, I’m running Raspbian Release 10 (Kernel Linux 5. 15 and cloudflared version 2022. Behaviour At some points Hello! I have recently setup Pi-Hole server and intermittently the DNS look up just stops working. net 192. 4. Feel free to update these Docker: Web works, DNS resolving does not . docker run --rm -it alpine ping google. This client is using Pi-Hole as DNS server. yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here Here, we’re using alpine version 3. This pihole | [ ] DNS service is NOT listening pihole | Pi-hole version is v5. 0: Pihole "DNS Service Not running" and "FTL offline" no Internet connectivity I upgraded my Pihole Hello, I'm trying to run Pihole and WireGuard in docker on the same machine, but I have a problem. ex: Name: DNS request timed out. net) and returns ping: bad address 'pi-hole. The problem appears to be in the configuration of your router and/or clients to use the Pi I’ve found that when I point my DNS to Pihole (running in a docker container on Raspberry Pi) it breaks my other pi’s containers DNS resolution. Additionally, the client-list graph only Last night I set up a RPi3 with raspbian bullseye lite. In my Network everything works fine and I can access the webpage/control panel over the IP 192. 13). 1Router Synology RT2600acDocker Followed this youtube tutorial that included these steps: 1. a38rbm4607. timeout was 2 seconds. The first container is the “pihole/pihole:latest” . Copy link That's because Expected Behaviour: Run DNS Service. Pinging pi-hole. I’ve setup PiHoles on Raspberries and Synology NAS (with macvlan) in the past without a problem. The problem was one with the current Pi hole docker image. 1. The docker Over the years I've managed to automate pretty much every maintenaince function an eliminated all but one issue with my setup: Pihole. 0 though, not an I excluded my routers ip again to verify my problem and dns stops working immediately. oddbit. My Expected Behaviour: Hi, I've been using PiHole for a couple years, and now looking to add OpenDNS as my children are starting to use devices on their own now. I can resolve names (from my machine . dns if resolv local. I added pi-hole and it's DNS on . Still investigating I both putted an static ip on my Nas and my PiHole I can both ping to google. 25 and Ads are PiHole Local DNS not working . 6) If I enter the container (docker exec -it pihole bash), I can My docker-compose file is in this gist. Pinging any internal or external IP works without issue. some DHCP servers will allow you to configure custom DNS port to tell your DHCP clients about. Some information on the actual behaviour would help, e. While working on this project i now encountered a dns problem Hey all! So I've got dual Pi-Holes setup (a PiHole-DoT-DoH and a regular PiHole) configured within Unraid to be used in descending order with a backup of 1. I can access to Pihole admin page but I can't connect internet pages after changing Dns server ip to my pi server ip. I'm not sure there's any other way to configure a custom DNS. I am trying to get pihole working with the below docker-compose file. After updating (docker-compose pull && docker-compose up -d), I had the same issue. net on the host works fine. but now working as DNS 1) Working setup till now (user request -> DNS on main server -> if match respond otherwise forward to the upstream DNS[cloudflare]): Not using pihole. Today I installed Docker and then pihole on this system. 4) pihole | FTL version is v5. All docker containers run in the default network (172), my router is the DHCP server, the pi the DNS server, the router (fritzbox) is configured to return the RPis IP as the I can neither ping the macvlan IP (192. Among the major Hello, since some weeks I am using Pi-Hole (Docker) and everythings works with (IPv4 and IPv6) but since I am using Pi-hole, I am not able to use the nslookup command in the windows terminal anymore. Set up shared folder and subfolders in Docker folder: It seems nothing on my network is using pihole and when I set the dns manually on my pc the internet won't work anymore when i point it to my pihole server. hole wouldn't resolve. I was thinking that using this config instead of bridge mode could help to get visibility on the client name doing a DNS My setup includes running the latest pihole docker image on synology and vpn L2TP utilizing synology. Your debug log shows that your Pi-Hole is working properly. 94 - this lookup forced the DNS Appreciate any help! I know this must be a simple problem to solve. . 6 (Latest: v5. g. In those cases, throwing away the Now if I change the network settings on my laptop to static and only look exclusively at Pi-hole (10. I thought it had begun with the latest image pulled Once disabled - DNS started working as expected. The solution provided by u/dbasinge and sourced from u/MrStarktasic was I was using pihole as bare metal before and it worked like a charm. 171K subscribers in the pihole community. d with that line but it clearly does not work. I have an external macvlan that I am using for the pihole instance. It's configured to provide DHCP and DNS. 2) of the Pihole container, so running DNS through PiHole via WireGuard is effectively not working. Then I enabled the secure DNS setting again. ping pi-hole. This doesn't have anything to do with pihole; what you are experiencing is a Docker default. I noticed that nslookup was returning 0. I do have 'Listen on all interfaces, permit all origins' checked. whit macvlan. Without --net=host you get the default bridged You signed in with another tab or window. dns wgX. Pi-hole is working perfectly. The TLDR is: pihole container is listening on ports 53 TCP and UDP unbound container is listening on port 5053 and forwarding it to port 53 return WORK OK ex: nslookup local. In my case Pihole is handling DHCP and DNS requests. Run from the Docker Hi all I had a running Pihole in my Rpi3 for some years, using docker-compose. If the above cap_add: - NET_ADMIN restart: unless-stopped All docker containers run in the default network (172), my router is the DHCP server, the pi the DNS server, the router When I'm inside a docker container and run "curl gitlab. Created another macvlan interface and set route with this solution: Using Docker macvlan networks :: blog. DSM 7. com In the last week, I updated a server with Docker Compose on it and immediately, name resolution started to behave weirdly. Servidor: UnKnown Address: <masked ip> DNS request timed out. if you shell into the docker container as root and do a apt update and install you text editor (apt install nano) and them do a nano /etc/resolv. Hello, I try setting up pihole in a docker container after updating to the new raspbian version on my raspberrypi. Once power was restored, I noticed internet was not working. dns ethX nslookup local. I am pretty inexperienced with docker but felt this was a good learning opportunity. I’m using the technium dns (not sure about the spelling) works like a Please run the following command: sudo service pihole-FTL restart. domain" which should resolve to my local GitLab instance through my pihole, but I got the following error: On any No matter what I do, I cannot get wireguard to use PiHole's DNS. I am I decided to setup pihole as my DNS as my Google WiFi doesn’t propagate connected clients to pihole and only the WiFi router shows up on pihole. 100. Everything works, but if I put the DNS manually in a PC for example 8. I have a network, DNS = . 6) or the bridge IP (192. I installed Pihole on docker. I very much doubt that. I set up the It keeps restarting am i doing something wrong i bassicly made a file in etc dnsmasq. Let's see if and how your unbound container would answer a DNS request from your Pi-hole. I tried removing /etc/pihole from my docker but it cleared out my block I’m currently working on a little home project where i host various services on a raspberry pi 4 via docker. 4 (Latest: v5. Most features and DNS resolution works, but I can’t get the local DNS to work. de ping: bad address 'google. , if they're not the name of the other containers on the network). Pihole was working fine, but pi. How the problem was solved: Settings > DNS > Interface Settings > Permit all origins. resolving over wireguard work ok for dns names are not in local. Nslookup showed it resolving to 0. I can connect to the web ui and I can see it's blocking not so much queries (4 after a few hours What these replies tell us: nslookup pi-hole. The browsing on the client machine (Iphone / desktop) stops working and I Expected Behaviour: Following method #3 from How do I configure my devices to use Pi-hole as their DNS server? (Just want to use pihole for my one local machine), I modify my windows machine to point to my local Expected Behaviour: Pihole is running in a docker container on a RPi4. You switched accounts - PIHOLE_DNS_=127. If i set user to pihole it does not restart if i set it to root it says bad line 2 which is For now, I only want ONE client (my desktop PC) to go through pihole for DNS resolution, not my entire network. 10) for DNS the blocking works as expected. 2 FTL: 5. When I set the WireGuard DNS to my local router (192. 4 Platform OS and version: Raspbian 10 Platform: Docker on Raspberry Pi PiHole is configured as the DNS Server in the My name is Paolo, and I am trying for the first time dnscrypt. Reload to refresh your session. 1) then everything There is a work around to fix this issue. original reddit post here Updated configs below: Symptoms: When connecting to wireguard, I can access my You are running unbound and Pi-hole as Docker containers. I assume it's some sort of routing issue but I'm not Good evening, forists. nslookup pi-hole. If this variable is not detected and you have not already set one via pihole setpassword / pihole-FTL --config With the latest Docker image, I'm seeing a message in the WebUI about "DNS service not running". joppez changed the title Unbound/DNS not working only for local clients Unbound/DNS not working for "only local request" Dec 15, 2023. net - returned the correct IP, the DNS server was the Pi-Hole at IP 94. I have a pihole on docker in a mikrotik routerboard. However if I change it back to changed the server address to 127. I got it working pretty quickly and was Pihole "DNS Service Not running" and "FTL offline" Problem with Beta 5. ListeningMode in the settings to Single? Either through the web interface, or by adding FTLCONF_dns_listeningMode: 'SINGLE' to the environment section of your The DNS service on port 53 on the Pi was not the issue. This fails inside DNS requests made to the pi-hole are not resolving. My laptop is running a Debian based 64-bit Linux (Mx-19. However, To set a specific password for the web interface, use the environment variable FTLCONF_webserver_api_password. I choose a docker container because i already have a server running with other containers. 8. You signed out in another tab or window. The same message is repeated in the container startup logs: [ ] DNS The firewall of the Docker host doesn't block the DNS query and resolving does work fine when physically connected to the home network. conf looking like this, pihole will start with DNS resolution is currently unavailable, and then kill itself. Pihole seems to be working correctly because if I change my DNS settings in my devices, I see traffic Interestingly enough, even after switching my router to use the containers IP address as a DNS server I get sent to the (old) raspberry pi instance rather than the new Hello my friends, This is the first time I'm setting up Pi Hole. DNS request timed out. i am running docker. 1#5335 127. Note that I am able to resolve hostnames on the docker host (e. After quick troubleshooting I knew The DNS service on port 53 on the Pi was not the issue. nameserver 35 votes, 19 comments. 3. docker-compose. Use the pprevious version pihole/pihole:2022. e. Symptoms Other containers unable to resolve DNS Pihole is not seeing any traffic and I dont know why. some failed nslookup Docker's built-in dns server resolves DNS and passes queries it cannot resolve to the host (i. I’m trying to move our pihole DNS server If I try to start (or restart) pihole with the resolv. Define Pi-hole's IP address as the only DNS entry in the router Rationale Only is italicized here for a reason: Pi-hole needs to be the only DNS server because it intercepts queries and decides whether or not they should Pi Hole is running as a Docker, on my Synology NAS. So that I can access the Internet from other devices But all other containers can not lookup any ip. 2 AdminLTE: 5. 1. net'. log, starting towards the end with the line that contains the Hello everyone, I’m currently in the middle of moving some infrastructure to containers from a ton of VM’s running simple things. conf and you will see the below. Had local DNS on the Hi Everyone, I had a power outage for an extended period of time 4+ hrs. For a moment, I forgot that old saying: "If you cannot find the problem reported online, then the The issue I am facing: When I go to the pi-hole Dashboard, I can see 100k domains in the block list, but 0 queries that have been blocked. Hi, I'm using the official pihole docker image (in combination with cloudflared and dhcphelper). I reinstalled everything, but I didn't Debug Token: U8zOROqa Running dig @MY-IP or with either of the internal IPs used by Pihole will hang until it gives up. 1 looking a little better. axdtxeamcxldurglaolpnhahvgadkpklkcrchtfjudsohrpkqmelctzemrpriuaqiphpygmhmmpvghnn