Our great sponsors
-
stubby
Stubby is the name given to a mode of using getdns which enables it to act as a local DNS Privacy stub resolver (using DNS-over-TLS).
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
I'm looking up DNS over TLS/HTTPS where this github page says they're recursive -- by any change, do they work the same as unbound or are they better/more suitable for some use cases?
U used Stubby for a while, that worked but I've since switched to Unbound.
version: "3" services: cloudflared: container_name: cloudflared image: visibilityspots/cloudflared:latest restart: unless-stopped networks: pihole_net: ipv4_address: 10.0.0.2 environment: UPSTREAM1: 'https://1.1.1.1/dns-query' UPSTREAM1: 'https://1.0.0.1/dns-query' googleflared: container_name: googleflared image: visibilityspots/cloudflared:latest restart: unless-stopped networks: pihole_net: ipv4_address: 10.0.0.4 environment: UPSTREAM1: 'https://8.8.8.8/dns-query' UPSTREAM2: 'https://8.8.4.4/dns-query' pi-hole: depends_on: [cloudflared, googleflared] container_name: pihole image: pihole/pihole:latest restart: unless-stopped ports: - "53:53/tcp" - "53:53/udp" - "67:67/udp" - "8090:80/tcp" environment: ServerIP: '10.0.0.3' DNS1: '10.0.0.2#5054' DNS2: '10.0.0.4#5054' IPv6: 'true' TZ: 'America/Los_Angeles' DNSMASQ_LISTENING: 'all' WEBPASSWORD: '' VIRTUAL_HOST: 'pi-hole.local' MAXDBDAYS: 7 networks: pihole_net: ipv4_address: 10.0.0.3 dns: - 127.0.0.1 volumes: - './etc-pihole/:/etc/pihole/' - './etc-dnsmasq.d/:/etc/dnsmasq.d/' - './var-log/:/var/log/' # Recommended but not required (DHCP needs NET_ADMIN) # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities cap_add: - NET_ADMIN restart: unless-stopped deploy: resources: limits: memory: 512M reservations: memory: 128M networks: pihole_net: driver: bridge ipam: config: - subnet: 10.0.0.0/29