sujiba/pihole-unbound-hyperlocal
1
0
Fork 0
mirror of https://github.com/sujiba/pihole-unbound-hyperlocal.git synced 2025-07-10 21:55:13 +02:00
Code Issues Releases Activity
docker pull sujiba/pihole-unbound-hyperlocal
28 commits 1 branch 9 tags 149 KiB
Find a file
sujiba 15b5eacbc8
added version var
2022-03-09 10:58:30 +01:00
.github/workflows added version var 2022-03-09 10:58:30 +01:00
docker-build commit 2022-03-07 23:53:06 +01:00
etc-dnsmasq.d first commit 2021-09-27 18:06:12 +02:00
.gitignore removed etc-dnsmasq.d 2022-01-12 12:52:12 +01:00
docker-compose.yaml changed variables 2022-01-12 12:30:03 +01:00
example.env removed double quotes 2022-01-24 16:00:28 +01:00
README.md changed documentation for resolv.conf 2021-12-22 23:56:56 +01:00
resolv.conf first commit 2021-09-27 18:06:12 +02:00

README.md

Pihole + Unbound + Hyperlocal

IMPORTANT: When using this Docker image, please report any bugs or suggestions to us directly.

Overview

Introduction

Pi-hole:

  • Pi-hole is a DNS sinkhole that protects your devices from unwanted content, without installing any client-side software.

Unbound:

  • Unbound is a validating, recursive, caching DNS resolver. It is designed to be fast and lean and incorporates modern features based on open standards.

Hyperlocal:

  • To spare the initial DNS query to the DNS-Root-Servers by Unbound, we provide Unbound with an appropriate configuration. With each Pi-hole update, the DNS-Root-Zone (root.hints) is also updated.

Prerequisites

First startup

Copy example.env to .env and change the parameters

cp example.env .env
vi .env

Start the container

docker-compose up -d

Testing

docker exec -it pihole-unbound bash
dig github.com @127.0.0.1 +short
dig sigfail.verteiltesysteme.net @127.0.0.1 | grep status 
dig sigok.verteiltesysteme.net @127.0.0.1 | grep status
  • First dig should show an IP address
  • Second dig should show status: SERVFAIL
  • Last dig should show status: NOERROR

Additional configuration

Edit setupVars.conf

vi ./etc-pihole/setupVars.conf

and add

# Caching is done by unbound
CACHE_SIZE=0

resolv.conf

If you are using a self-created docker network or having problems with the pihole deployment inside the container, uncomment the following line in the docker-compose.yaml

#- ./resolv.conf:/etc/resolv.conf

Restart the container

docker-compose up -d --force-recreate

Blocklists

Acknowledgement