38b3fe6718
* commit '9682dc6bc19ea940cf71911f6281450c7027eb16': travis -- npm installation of dependencies belongs in install section makefile -- use npm --prefix syntax instead of doing cd into subdir travis -- don't use slow master or tip builds, just specify 1.x for latest go version travis -- move dependency installation to install section, simplify go test invocation to test all subdirs in one go dnsfilter -- small code cleanup coredns plugin metrics -- deduplicate code dnsfilter metrics -- parental cache hits were counted as safebrowsing cache hits
Self-hosted AdGuard DNS
AdGuard DNS is an ad-filtering DNS server with built-in phishing protection and optional family-friendly protection.
This repository describes how to set up and run your self-hosted instance of AdGuard DNS -- it comes with a web dashboard that can be accessed from browser to control the DNS server and change its settings, it also allows you to add your filters in both AdGuard and hosts format.
If this seems too complicated, you can always use AdGuard DNS servers that provide same functionality — https://adguard.com/en/adguard-dns/overview.html
Installation
Go to https://github.com/AdguardTeam/AdguardDNS/releases and download the binaries for your platform:
Mac
Download file AdguardDNS_*_darwin_amd64.tar.gz, then unpack it and follow how to run instructions below.
Linux
Download file AdguardDNS_*_linux_amd64.tar.gz, then unpack it and follow how to run instructions below.
How to build your own
Prerequisites
You will need:
You can either install it from these websites or use brew.sh if you're on Mac:
brew install go node yarn
Building
Open Terminal and execute these commands:
git clone https://github.com/AdguardTeam/AdguardDNS
cd AdguardDNS
make
How to run
DNS works on port 53, which requires superuser privileges. Therefore, you need to run it with sudo:
sudo ./AdguardDNS
Now open the browser and point it to http://localhost:3000/ to control AdGuard DNS server.
Running without superuser
You can run it without superuser privileges, but you need to instruct it to use other port rather than 53. You can do that by opening AdguardDNS.yaml and adding this line:
coredns:
port: 53535
If the file does not exist, create it and put these two lines down.
Contributing
You are welcome to fork this repository, make your changes and submit a pull request — https://github.com/AdguardTeam/AdguardDNS/pulls
Reporting issues
If you come across any problem, or have a suggestion, head to this page and click on the New issue button.