unbound-docker
unbound-docker-rpi
Our great sponsors
unbound-docker | unbound-docker-rpi | |
---|---|---|
13 | 6 | |
509 | 133 | |
- | - | |
6.3 | 5.4 | |
7 days ago | about 1 month ago | |
Shell | Shell | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unbound-docker
-
No internet access for containers co-hosted with pihole
version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ networks: dns_net: driver: bridge ipam: config: - subnet: 10.2.0.0/24 services: pihole: depends_on: [unbound] container_name: pihole image: pihole/pihole:latest hostname: pihole networks: dns_net: ipv4_address: 10.2.0.100 ports: - "5335:53/tcp" - "5335:53/udp" - "7000:80/tcp" environment: TZ: ${TZ} WEBPASSWORD: ${PWD} FTLCONF_LOCAL_IPV4: ${HOST_IP} # Set to server's LAN IP, used by web block modes. PIHOLE_DNS_: 10.2.0.200 # Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon DNSMASQ_LISTENING: all # "Listen on all interfaces, permit all origins" # Volumes store your data between container upgrades volumes: - /var/lib/docker/volumes/pihole/etc-pihole:/etc/pihole - /var/lib/docker/volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d healthcheck: disable: true restart: unless-stopped unbound: # https://github.com/MatthewVance/unbound-docker container_name: unbound image: mvance/unbound:latest hostname: unbound networks: dns_net: ipv4_address: 10.2.0.200 ports: - "${HOST_IP}:53:53/udp" - "${HOST_IP}:53:53/tcp" healthcheck: disable: true restart: unless-stopped
-
I've created a simple 2 container Pihole + Unbound Docker Setup for you to use
I'm not an unbound expert, but as far as I understand MatthewVance's image, unbound is already configured properly: https://github.com/MatthewVance/unbound-docker/blob/master/1.17.1/data/unbound.sh. I didn't want to go into detail how pi-hole or unbound works, since I think there is enough documentation on that.
-
Problems with unbound
I am successfully running pihole on a different machine, but am planning to migrate to a new docker host. I figured this would be a good time to configure pihole with unbound. I am attempting to run unbound in a docker container running on Opensuse leap and I am using this docker image.
- Need help w/ unbound
-
Pihole with Recursive DNS
You can also use Unbound for recursive DNS in a docker container: https://github.com/MatthewVance/unbound-docker
- Pihole & Unbound Docker?
- Starting Unbound in a Docker Container
-
When using Unbound can’t connect to any site?
https://github.com/MatthewVance/unbound-docker/blob/master/1.14.0/data/unbound.sh
- Nothing but issues with unbound and dont know what to do.
-
Radarr installation fails on fresh Ubuntu install
# https://github.com/MatthewVance/unbound-docker unbound: container_name: unbound environment: PGID: $PGID PUID: $PUID TZ: $TZ image: mvance/unbound networks: smarthome: ipv4_address: 172.18.0.6 restart: always
unbound-docker-rpi
- Pihole, unbound and WireGuard.
-
My Raspberry Pi 4 Dashboard
- Unbound
-
Pi-Hole with Unbound reporting Cloudflare DNS when checking for DNS leaks
In Pi-Hole, all the queries are sent to and answered by the Unbound docker container, as confirmed by the Pi-Hole logs. I am not seeing any query in Pi-Hole going outside my network for resolution, so I am stumped as to what the cause of this is. The best guess that I could come up with is that somehow Unbound got configured in forwarding mode instead of a recursive resolver. I am not an expert on networking or Unbound, so I am looking for anyone who has an idea as to how to solve this. If it helps, I used https://github.com/MatthewVance/unbound-docker-rpi as the docker image to set up unbound.
-
Starting Unbound in a Docker Container
If your using a pi, you need to use the pi image. Also I remember that I created these files before deploying the container: config files for unbound * a-records.conf ```
- How to install Unbound and Pi-hole in Docker using docker-compose
-
Best Docker image to use to install Pi-hole (along with PiVPN and Unbound)?
mvance/unbound-rpi is a image that is updated regularly and used by many. The code he uses to create the image is here.
What are some alternatives?
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
dnscrypt-server-docker - A Docker image for a non-censoring, non-logging, DNSSEC-capable, DNSCrypt-enabled DNS resolver
gravity-sync - 💫 The easy way to synchronize the DNS configuration of two Pi-hole 5.x instances.
unbound-config - fragmented configuration files for unbound recursive dns resolver
Pi-hole - A black hole for Internet advertisements
docker-pi-hole - Pi-hole in a docker container
cloudblock - Cloudblock deploys secure ad-blocking and VPN for all devices. Text and video guides included! 6 supported cloud providers, plus Ubuntu and Raspberry Pi. Cloudblock deploys Wireguard VPN, Pi-Hole DNS Ad-blocking, and DNS over HTTPS in a cloud provider - or locally - using Terraform and Ansible.
docker-radarr
dns-server-setup - Ansible playbook to easily deploy new, fully configured, DNS servers.
wirehole - WireHole is a combination of WireGuard, Pi-hole, and Unbound in a docker-compose project with the intent of enabling users to quickly and easily create a personally managed full or split-tunnel WireGuard VPN with ad blocking capabilities thanks to Pi-hole, and DNS caching, additional privacy options, and upstream providers via Unbound.