dns-server-setup
unbound-docker
Our great sponsors
dns-server-setup | unbound-docker | |
---|---|---|
5 | 13 | |
54 | 426 | |
- | - | |
2.7 | 0.0 | |
over 1 year ago | 8 days ago | |
Shell | Shell | |
GNU General Public License v3.0 only | 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.
dns-server-setup
- Waktu Pendaftaran PSE sampai 27 Juli, Kominfo: Kalau Tidak Respons, Akses Diputus Sementara
-
There is a way to create a dns that use oisd?
Yes, looks like the code you're looking for lives in https://github.com/AhaDNS/dns-server-setup/blob/master/files/scripts/bash/unbound_update.sh
-
Adguard not working properly
Haha I know what you mean :) On the bright side it is open-source: https://github.com/AhaDNS/dns-server-setup
unbound-docker
-
No internet access for containers co-hosted with pihole
services: pihole: dependson: [unbound] container_name: pihole image: pihole/pihole:latest hostname: pihole networks: dns_net: ipv4_address: 10.2.0.100 ports: - "${HOST_IP}:53:53/tcp" - "${HOST_IP}:53: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 healthcheck: disable: true restart: unless-stopped
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.
-
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
-
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
What are some alternatives?
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
Technitium DNS Server - Technitium DNS Server
Pi-hole - A black hole for Internet advertisements
ansible-adguard - Ansible playbook to setup AdGuard Home with Unbound, including DoH, DoT & Let's Encrypt, based on Docker
dnscrypt-server-docker - A Docker image for a non-censoring, non-logging, DNSSEC-capable, DNSCrypt-enabled DNS resolver
sdns - A high-performance, recursive DNS resolver server with DNSSEC support, focused on preserving privacy.
unbound-config - fragmented configuration files for unbound recursive dns resolver
docker-pi-hole - Pi-hole in a docker container
unbound-docker-rpi - Run Unbound with latest version of OpenSSL on Raspberry Pi with Docker.
docker-radarr
doh-cf-workers - DNS-over-HTTPS proxy on Cloudflare Workers
docker-jackett