Personal DNS container replacing provider / public DNS servers with included Ad- and Tracker blocking
Find a file
Knut Ahlers ed3c4cc1fa
Replace Coredns magic with bind response-policy
Signed-off-by: Knut Ahlers <knut@ahlers.me>
2019-08-25 16:40:40 +02:00
.gitignore Replace Coredns magic with bind response-policy 2019-08-25 16:40:40 +02:00
blacklist.local Replace Coredns magic with bind response-policy 2019-08-25 16:40:40 +02:00
blacklist.tpl Replace Coredns magic with bind response-policy 2019-08-25 16:40:40 +02:00
build.sh Replace Coredns magic with bind response-policy 2019-08-25 16:40:40 +02:00
build_blacklist.sh Replace Coredns magic with bind response-policy 2019-08-25 16:40:40 +02:00
docker-entrypoint.sh Replace Coredns magic with bind response-policy 2019-08-25 16:40:40 +02:00
Dockerfile Replace Coredns magic with bind response-policy 2019-08-25 16:40:40 +02:00
LICENSE Create LICENSE 2018-05-09 23:12:20 +02:00
Makefile Replace Coredns magic with bind response-policy 2019-08-25 16:40:40 +02:00
named.conf Replace Coredns magic with bind response-policy 2019-08-25 16:40:40 +02:00
README.md Add README 2018-05-09 23:20:21 +02:00
whitelist.local Add local whitelist to unblock entries 2019-08-23 15:13:17 +02:00

Luzifer / personal-dns

personal-dns is a combination of two DNS servers in one container: CoreDNS and Bind9.

The purpose is to be fully independent from provider and third-party DNS servers and have a neat list of additional features:

  • No DNS query is sent to your providers DNS servers
  • You decide which domains are available to you, no third party company
  • Container does not log requesting IPs: You're not traced
  • On every build a current list of IANA and OpenNIC registered TLDs is loaded together with their authorative nameservers
  • The container includes a blacklist blocking quite a lot of crap

As soon as you build and roll this DNS container and set your system to use it you should notice a lot of ad- and tracking requests to be gone even for example on your Android device where adblockers does not work that well. Also all connected devices can access any domain registered within the OpenNIC TLDs.

Usage

Build and run the container

This is quite easy:

$ docker build -t personal-dns .
$ docker run --rm -ti -p 53:53 -p 53:53/udp personal-dns
$ dig +short @<ip of your container> health.server.test
0.0.0.0

Connect your computer to the container

  • On Mac OS go into the System Preferences, Network, edit your LAN / WiFi connection, enter the IP your container is reachable into DNS settings
  • On Android I'm using the DNS Changer App