![]() ![]() Now set the PI hole custom DNS to 127.53 and hit Save on the DNS settings page of Pihole. # logfile: "/var/log/unbound/unbound. sudo apt install unbound Updated every 6 months (Jan & July) wget -O root.hints https. The advantages of unbound as a local recursive resolver (in my opinion) are: No upstream DNS resolver has your DNS history. # If no logfile is specified, syslog is used config/root.hints:/var/unbound/etc/root.hints I'm new Docker and Unbound so this has been a bit of a dive in at the deep end! My docker-compose.yml and nf are below. Pi-Hole + Unbound on Docker Use Docker to run Pi-Hole with an upstream Unbound resolver. However after that I still get the same error, no matter what ports I try. I theorized this could be to do with the pihole container not being able to communicate with the Unbound container through localhost, so updated my docker-compose to try and correct this using the netowkr bridge. Before switching to OpenWrt, my Pi was resolving queries without any issues and everything worked as intended. The installation was relatively smooth and the router is working. connection timed out no servers could be reached Recently I installed OpenWrt on my Archer C50 v4 using tftp. However, when running docker exec pihole dig -p 5333 or -p 5354 I get a response of > DiG 9.10.3-P4-Debian > -p 5354 Pihole has nice interface to view amount and type of dns queries. I've been following Pihole's documentation to get this running found here and have got both containers starting, and pihole working. Unbound is a fast and secure DNS server, primarily developed by NLnet Labs. The idea is that Pihole will first block any requests before using Unbound as its DNS server. I'm trying to run 2 Docker containers on Raspberry pi 3, one for Unbound and one for Pihole. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |