mirrors
/
AdGuardHome
mirror of https://github.com/AdguardTeam/AdGuardHome.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Mirror of adguardteam/adguardhome@github.com - DNS resolver with privacy protections
3,271 Commits 96 Branches 201 Tags 57 MiB
Go 60.3%
TypeScript 24.8%
CSS 12.4%
Shell 2%
Makefile 0.2%
Other 0.2%
Go to file
Eugene Burkov 5e71f5df6a Pull request: 2846 cover aghnet vol.3 
Merge in DNS/adguard-home from 2846-cover-aghnet-vol.3 to master

Updates #2846.

Squashed commit of the following:

commit cb22987c43c17bbc8d098e65639cc84e2284bc7b
Merge: cf995e9d f31ffcc5
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Mar 30 15:01:10 2022 +0300

    Merge branch 'master' into 2846-cover-aghnet-vol.3

commit cf995e9dce635f16e10406a61e2ab12f06407f1f
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Mar 28 18:29:50 2022 +0300

    aghnet: imp tests

commit bc225fe8800633b29216840bc7d5b82d7c2d2bfb
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Mar 28 18:03:06 2022 +0300

    aghnet: imp tests

commit a82eb6045495b94a2e81ced9a3ef5bfe65788e56
Merge: f8081249 0d562a7b
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Mar 28 17:39:13 2022 +0300

    Merge branch 'master' into 2846-cover-aghnet-vol.3

commit f80812490c49f69655d409c6f015b069affa2f19
Merge: edccaa79 3603b1fc
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Mar 28 17:29:20 2022 +0300

    Merge branch 'master' into 2846-cover-aghnet-vol.3

commit edccaa79fca061ffeea1985c293eed123b16a09c
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Mon Mar 28 13:53:40 2022 +0300

    aghnet: imp tests

commit 7c5028c92f0a6680516bda67c73e794182c9b825
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Fri Mar 25 18:01:28 2022 +0300

    aghnet: imp code & docs

commit 7897c6b13e9be340ae8a71947a8a0bab82c682eb
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Fri Mar 25 17:11:46 2022 +0300

    aghnet: imp coverage

commit 1eef110af3bf721a0275c695bf27c31815abff04
Author: Eugene Burkov <E.Burkov@AdGuard.COM>
Date:   Wed Mar 23 21:10:29 2022 +0300

    all: return byte slice
 		2022-03-30 15:11:57 +03:00
.github Pull request: filtering: restore rewrite behavior with other question types 2021-12-24 20:14:36 +03:00
bamboo-specs Pull request: all: upd go 2022-03-04 15:50:35 +03:00
build Pull request: all: update go and backend tools 2021-05-21 14:55:42 +03:00
build2 Pull request: all: update go and backend tools 2021-05-21 14:55:42 +03:00
client Pull request: client: upd i18n 2022-03-23 14:36:17 +03:00
client2 Pull request: all: add bamboo specs 2021-04-08 13:55:12 +03:00
doc * tech doc: update architecture picture 2020-03-17 18:36:10 +03:00
internal Pull request: 2846 cover aghnet vol.3 2022-03-30 15:11:57 +03:00
openapi Pull request: 3978 Query Log ECS 2022-03-03 17:52:11 +03:00
scripts Pull request: scripts: imp mips compat 2022-02-11 17:41:36 +03:00
.codecov.yml Pull request: all: reformat yaml, add yaml formatting standard 2020-11-20 18:06:07 +03:00
.dockerignore Pull request: all: add a new Makefile and scripts, remove goreleaaser 2020-12-30 18:26:25 +03:00
.gitattributes Pull request: all: upd go 2022-02-11 16:30:09 +03:00
.gitignore Pull request: 3172 fix mobileconfig 2021-06-01 21:06:55 +03:00
.twosky.json Pull request: client: add fi, uk locales 2021-11-15 14:35:46 +03:00
AGHTechDoc.md Pull request: all: fix some typos 2021-08-17 15:58:40 +03:00
CHANGELOG.md Pull request: aghnet: fix catching timeout errors 2022-03-29 16:21:22 +03:00
HACKING.md Pull request: all: add links to new guidelines 2021-07-28 14:17:11 +03:00
LICENSE.txt Initial commit 2018-08-30 17:25:33 +03:00
Makefile Pull request: add go sumdb env 2022-03-28 17:05:19 +03:00
README.md Pull request: all: upd go, tools, deps 2021-12-22 16:34:51 +03:00
changelog.config.js Pull request: all: less annoying pkg names 2021-05-21 16:15:47 +03:00
go.mod Pull request: 3142 custom private subnets 2022-03-18 13:37:27 +03:00
go.sum Pull request: 3142 custom private subnets 2022-03-18 13:37:27 +03:00
main.go Pull request: 3835 check ports properly 2021-12-16 20:54:59 +03:00
staticcheck.conf Pull request: all: imp docs, names 2021-06-18 18:13:36 +03:00

README.md

 

AdGuard Home

Privacy protection center for you and your devices

Free and open source, powerful network-wide ads & trackers blocking DNS server.

AdGuard.com | Wiki | Reddit | Twitter | Telegram

Code Coverage Go Report Card Docker Pulls Docker Stars
Latest release adguard-home


AdGuard Home is a network-wide software for blocking ads & tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client-side software for that.

It operates as a DNS server that re-routes tracking domains to a "black hole", thus preventing your devices from connecting to those servers. It's based on software we use for our public AdGuard DNS servers -- both share a lot of common code.

Getting Started

Automated install (Linux and Mac)

Run the following command in your terminal:

curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -v

The script also accepts some options:

  • -c <channel> to use specified channel.
  • -r to reinstall AdGuard Home;
  • -u to uninstall AdGuard Home;
  • -v for verbose output;

Note that options -r and -u are mutually exclusive.

Alternative methods

Manual installation

Please read the Getting Started article on our Wiki to learn how to install AdGuard Home manually, and how to configure your devices to use it.

Docker

You can use our official Docker image.

Snap Store

If you're running Linux, there's a secure and easy way to install AdGuard Home - you can get it from the Snap Store.

Guides

API

If you want to integrate with AdGuard Home, you can use our REST API. Alternatively, you can use this python client, which is used to build the AdGuard Home Hass.io Add-on.

Comparing AdGuard Home to other solutions

How is this different from public AdGuard DNS servers?

Running your own AdGuard Home server allows you to do much more than using a public DNS server. It's a completely different level. See for yourself:

  • Choose what exactly the server blocks and permits.
  • Monitor your network activity.
  • Add your own custom filtering rules.
  • Most importantly, this is your own server, and you are the only one who's in control.

How does AdGuard Home compare to Pi-Hole

At this point, AdGuard Home has a lot in common with Pi-Hole. Both block ads and trackers using "DNS sinkholing" method, and both allow customizing what's blocked.

We're not going to stop here. DNS sinkholing is not a bad starting point, but this is just the beginning.

AdGuard Home provides a lot of features out-of-the-box with no need to install and configure additional software. We want it to be simple to the point when even casual users can set it up with minimal effort.

Disclaimer: some of the listed features can be added to Pi-Hole by installing additional software or by manually using SSH terminal and reconfiguring one of the utilities Pi-Hole consists of. However, in our opinion, this cannot be legitimately counted as a Pi-Hole's feature.

Feature AdGuard Home Pi-Hole
Blocking ads and trackers ✅ ✅
Customizing blocklists ✅ ✅
Built-in DHCP server ✅ ✅
HTTPS for the Admin interface ✅ Kind of, but you'll need to manually configure lighttpd
Encrypted DNS upstream servers (DNS-over-HTTPS, DNS-over-TLS, DNSCrypt) ✅ ❌ (requires additional software)
Cross-platform ✅ ❌ (not natively, only via Docker)
Running as a DNS-over-HTTPS or DNS-over-TLS server ✅ ❌ (requires additional software)
Blocking phishing and malware domains ✅ ❌ (requires non-default blocklists)
Parental control (blocking adult domains) ✅ ❌
Force Safe search on search engines ✅ ❌
Per-client (device) configuration ✅ ✅
Access settings (choose who can use AGH DNS) ✅ ❌
Running without root privileges ✅ ❌

How does AdGuard Home compare to traditional ad blockers

It depends.

"DNS sinkholing" is capable of blocking a big percentage of ads, but it lacks flexibility and power of traditional ad blockers. You can get a good impression about the difference between these methods by reading this article. It compares AdGuard for Android (a traditional ad blocker) to hosts-level ad blockers (which are almost identical to DNS-based blockers in their capabilities). This level of protection is enough for some users.

Additionally, using a DNS-based blocker can help to block ads, tracking and analytics requests on other types of devices, such as SmartTVs, smart speakers or other kinds of IoT devices (on which you can't install traditional ad blockers).

Known limitations

Here are some examples of what cannot be blocked by a DNS-level blocker:

  • YouTube, Twitch ads
  • Facebook, Twitter, Instagram sponsored posts

Essentially, any advertising that shares a domain with content cannot be blocked by a DNS-level blocker.

Is there a chance to handle this in the future? DNS will never be enough to do this. Our only option is to use a content blocking proxy like what we do in the standalone AdGuard applications. We're going to bring this feature support to AdGuard Home in the future. Unfortunately, even in this case, there still will be cases when this won't be enough or would require quite a complicated configuration.

How to build from source

Prerequisites

Run make init to prepare the development environment.

You will need this to build AdGuard Home:

  • go v1.17 or later.
  • node.js v10.16.2 or later.
  • npm v6.14 or later (temporary requirement, TODO: remove when redesign is finished).
  • yarn v1.22.5 or later.

Building

Open Terminal and execute these commands:

git clone https://github.com/AdguardTeam/AdGuardHome
cd AdGuardHome
make

Please note, that the non-standard -j flag is currently not supported, so building with make -j 4 or setting your MAKEFLAGS to include, for example, -j 4 is likely to break the build. If you do have your MAKEFLAGS set to that, and you don't want to change it, you can override it by running make -j 1.

Check the Makefile to learn about other commands.

Building for a different platform. You can build AdGuard for any OS/ARCH just like any other Go project. In order to do this, specify GOOS and GOARCH env variables before running make.

For example:

env GOOS='linux' GOARCH='arm64' make

Or:

make GOOS='linux' GOARCH='arm64'

Preparing release

You'll need this to prepare a release build:

Commands:

make build-release CHANNEL='...' VERSION='...'

Docker image

  • Run make build-docker to build the Docker image locally (the one that we publish to DockerHub).

Please note, that we're using Docker Buildx to build our official image.

You may need to prepare before using these builds:

  • (Linux-only) Install Qemu: docker run --rm --privileged multiarch/qemu-user-static --reset -p yes --credential yes
  • Prepare builder: docker buildx create --name buildx-builder --driver docker-container --use

Resources that we update periodically

  • scripts/translations
  • scripts/whotracksme

Contributing

You are welcome to fork this repository, make your changes and submit a pull request — https://github.com/AdguardTeam/AdGuardHome/pulls

Please note that we don't expect people to contribute to both UI and golang parts of the program simultaneously. Ideally, the golang part is implemented first, i.e. configuration, API, and the functionality itself. The UI part can be implemented later in a different pull request by a different person.

Test unstable versions

There are two update channels that you can use:

  • beta - beta version of AdGuard Home. More or less stable versions.
  • edge - the newest version of AdGuard Home. New updates are pushed to this channel daily and it is the closest to the master branch you can get.

There are three options how you can install an unstable version:

  1. Snap Store -- look for "beta" and "edge" channels there.
  2. Docker Hub -- look for "beta" and "edge" tags there.
  3. Standalone builds. Use the automated installation script or look for the available builds below.

Beta:

curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -c beta

Edge:

curl -s -S -L https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s -- -c edge

Report issues

If you run into any problem or have a suggestion, head to this page and click on the New issue button.

Help with translations

If you want to help with AdGuard Home translations, please learn more about translating AdGuard products here: https://kb.adguard.com/en/general/adguard-translations

Here is a link to AdGuard Home project: https://crowdin.com/project/adguard-applications/en#/adguard-home

Other

Here's what you can also do to contribute:

  1. Look for issues marked as "help wanted".
  2. Actualize the list of Blocked services. It can be found in filtering/blocked.go.
  3. Actualize the list of known trackers. It it can be found in [this repo] companiesdb.
  4. Actualize the list of vetted blocklists. It it can be found in client/src/helpers/filters/filters.json.

Projects that use AdGuard Home

Acknowledgments

This software wouldn't have been possible without:

You might have seen that CoreDNS was mentioned here before — we've stopped using it in AdGuard Home. While we still use it on our servers for AdGuard DNS service, it seemed like an overkill for Home as it impeded Home features that we plan to implement.

For a full list of all node.js packages in use, please take a look at client/package.json file.

Privacy

Our main idea is that you are the one, who should be in control of your data. So it is only natural, that AdGuard Home does not collect any usage statistics, and does not use any web services unless you configure it to do so. Full policy with every bit that could in theory be sent by AdGuard Home is available here.