74275bebdc
* commit '1f0fdef8d6b2ce324e7009bb3f95626d87438d61': Fix invalid element order for historical stats -- in API declaration values are from oldest to newest, not other way around. Rewrite how historical stats are stored and calculated. coredns plugin -- convert logic into switch, logging unexpected non-covered cases After filters were redownloaded and deemed to be fresh, tell coredns server to reload coredns plugin -- on server reload, metrics disappeared, therefore they must be registered on each reload instead of once coredns plugin -- give feedback how many rules were in rulefile dnsfilter -- Update tests to check for expected filter/nofilter reason as well. Remove debug logging during checks if coredns is alive Be more atomic during writing of files -- this prevents other processes from seeing empty or impartial files Start coredns on launch before we serve HTTP -- this checks if port is available Move starting of coredns server into separate function sometimes answer can be empty, therefore question could be lost -- pass both to querylog Reduce binary size of coredns by 60% by removing orchestration plugins like kubernetes, route53, trace, etcd and federation Fix registration of metrics if querylog is enabled |
||
|---|---|---|
| client | ||
| coredns_plugin | ||
| dnsfilter | ||
| packaging | ||
| tests | ||
| .gitignore | ||
| .travis.yml | ||
| app.go | ||
| config.go | ||
| control.go | ||
| helpers.go | ||
| issue_template.md | ||
| LICENSE.txt | ||
| Makefile | ||
| openapi.yaml | ||
| README.md | ||
| stats.go | ||
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.