Network-wide ads & trackers blocking DNS server

 

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 -sSL https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh

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 will the server block or not block.
  • 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 lighthttpd
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).

However, 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 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.15 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 -sSL https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s beta

Edge:

curl -sSL https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh -s 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 it can be found in dnsfilter/blocked.go.
  3. Actualize the list of known trackers. It it can be found in client/src/helpers/trackers/adguard.json.
  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 with 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.

Comments
  • Memory leak and device crash

    Memory leak and device crash

    Issue Details

    • Version of AdGuard Home server:
      • v0.107.5
    • How did you install AdGuard Home:
      • GitHub releases
    • How did you setup DNS configuration:
      • router
    • If it's a router or IoT, please write device model:
      • Ubiquiti EdgeRouter ER-12, EdgeOS
    • CPU architecture:
      • mips64_softfloat (Cavium Octeon III V0.2 FPU V0.0)
    • Operating system and version:
      • EdgeOS v2.0.9-hotfix.2

    Expected Behavior

    Run for long periods of time without crashes/memory leak.

    Actual Behavior

    Leaks memory until the router is out of memory and it crashes.

    Screenshots

    After about 26 days of uptime:

    agh1

    After the screenshot above, I restarted AGH and it shows a reasonable memory footprint:

    agh2

    You can see the memory use on the device drops from 456M to 177M after an AGH restart, but it continues to climb until it eventually exhausts the entire device memory.

    Additional Information

    Cache settings:

    cache_size: 4194304
    cache_ttl_min: 300
    cache_ttl_max: 86400
    cache_optimistic: true
    safebrowsing_cache_size: 1048576
    safesearch_cache_size: 1048576
    parental_cache_size: 1048576
    cache_time: 30
    

    Clearing the stats and logs while AGH is running does not help reclaim memory, only an AGH restart does.

  • Заблокированные сервисы НЕ РАБОТАЮТ((((Сайты так же работают.

    Заблокированные сервисы НЕ РАБОТАЮТ((((Сайты так же работают.

    Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.

    Prerequisites

    Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

    • [x] I am running the latest version
    • [x] I checked the documentation and found no answer
    • [x] I checked to make sure that this issue has not already been filed

    Issue Details

    • Version of AdGuard Home server:
    • How did you install AdGuard Home:
    • How did you setup DNS configuration:
    • If it's a router or IoT, please write device model:
    • CPU architecture:
    • Operating system and version:

    Expected Behavior

    Actual Behavior

    Screenshots

    Screenshot:

    Additional Information

    Снимок PNGгнгн Снимок PNGгнгнгн Добрый вечер Уважаемые разработчики!))Не работает блокировка сайтов не один сайт не блокируется(((Настройки сохранил!

  • Stats get corrupted after flood of queries

    Stats get corrupted after flood of queries

    Issue Details

    • Version of AdGuard Home server:

      • v0.107.4
    • How did you install AdGuard Home:

      • GitHub releases
    • How did you setup DNS configuration:

      • System
    • CPU architecture:

      • ARM64/aarch64
    • Operating system and version:

      • Debian 11

    Expected Behavior

    Stats page working normally showing all the info it shows.

    Actual Behavior

    From time to time the stats page shows zero everywhere and empty domains lists (most blocked, most queried, etc). When accessing the page at the time it happens, an error appears at the right bottom corner saying:

    Error: control/clients/find?ip0=127.0.0.1&ip1=206.42.33.166&ip2=10.0.0.3&ip3=45.164.223.2&ip4=motog&ip5=joaouerj&ip6=131.159.24.242&ip7=179.190.172.16&ip8=220.180.241.26&ip9=177.25.155.98&ip10=177.25.153.160&ip11=177.25.150.57&ip12=154.202.55.217&ip13=177.25.153.142&ip14=45.205.48.180&ip15=185.249.221.238&ip16=183.90.186.240&ip17=177.25.156.157&ip18=177.25.144.182&ip19=154.198.205.174&ip20=45.205.35.196&ip21=156.229.9.224&ip22=154.198.219.21&ip23=177.25.153.187&ip24=177.25.144.89&ip25=177.25.150.41&ip26=10.0.0.1&ip27=177.25.153.233&ip28=177.25.159.130&ip29=177.25.159.162&ip30=191.47.16.69&ip31=177.25.153.174&ip32=177.25.155.148&ip33=177.25.144.221&ip34=177.25.153.216&ip35=177.25.156.1&ip36=177.25.159.132&ip37=177.25.155.166&ip38=177.25.145.82&ip39=177.25.151.167&ip40=177.25.150.32&ip41=88.80.186.137&ip42=177.25.156.159&ip43=177.25.153.172&ip44=177.25.155.73&ip45=177.25.145.50&ip46=177.25.157.85&ip47=14.1.112.177&ip48=170.106.176.49&ip49=177.25.150.119&ip50=131.159.25.7&ip51=146.88.240.4&ip52=103.203.59.3&ip53=209.141.45.192&ip54=39.129.8.129&ip55=45.83.67.25&ip56=177.25.156.143&ip57=129.250.206.86&ip58=174.138.40.30&ip59=162.142.125.133&ip60=71.6.232.7&ip61=141.22.28.227&ip62=27.98.224.20&ip63=184.105.139.117&ip64=64.62.197.37&ip65=45.79.15.228&ip66=37.44.239.30&ip67=159.89.194.175&ip68=202.112.238.56&ip69=177.25.156.77&ip70=185.180.143.142&ip71=185.180.143.73&ip72=162.142.125.212&ip73=54.173.29.204&ip74=185.180.143.76&ip75=146.88.240.12&ip76=141.212.123.193 | Network Error
    

    AdGuard continues to work normally apparently and resolving names with other pages working also, but the stats page gets broken. My guess is after a flood of queries from a bunch of CN/HK/SG addresses, the stats info file gets corrupt somehow.

    The last batch was repeatedly composed of queries like that:

    {"T":"2022-03-04T02:39:59.960278275-03:00","QH":"microsoft.com","QT":"TXT","QC":"IN","CP":"","Answer":"APyBgAABABAAAAABCW1pY3Jvc29mdANjb20AABAAAcAMABAAAQAADR8AKyphcHBsZS1kb21haW4tdmVyaWZpY2F0aW9uPTBnTWVhWXlZeTZHTFZpR2/ADAAQAAEAAA0fAEVEZ29vZ2xlLXNpdGUtdmVyaWZpY2F0aW9uPXBqUE9hdVNQY3JmWE9aUzlqblBQYTVheG93Y0hHQ0RBbDFfODZkQ3FGcGvADAAQAAEAAA0fABsaZmcydDBnb3Y5NDI0cDJ0ZGN1bzk0Z29lOWrADAAQAAEAAA0fABsadDdzZWJlZTUxanJqN3ZtOTMyazUzMWhpcGHADAAQAAEAAA0fAEVEZ29vZ2xlLXNpdGUtdmVyaWZpY2F0aW9uPU0tLUNWZm5fWXdzVi0yRkdiQ3BfSEZhRWoyM0JtVDBjVEY0bDhoWGdwdk3ADAAQAAEAAA0fACEgcGJjcGN3ODRzZms3dzRuaG03ZHd5ZzJrM2d4MHQ0eHLADAAQAAEAAA0fAC4tZG9jdXNpZ249ZDVhMzczN2MtYzIzYy00YmQwLTkwOTUtZDJmZjYyMWYyODQwwAwAEAABAAANHwC+vXY9c3BmMSBpbmNsdWRlOl9zcGYtYS5taWNyb3NvZnQuY29tIGluY2x1ZGU6X3NwZi1iLm1pY3Jvc29mdC5jb20gaW5jbHVkZTpfc3BmLWMubWljcm9zb2Z0LmNvbSBpbmNsdWRlOl9zcGYtc3NnLWEubWljcm9zb2Z0LmNvbSBpbmNsdWRlOnNwZi1hLmhvdG1haWwuY29tIGluY2x1ZGU6X3NwZjEtbWVvLm1pY3Jvc29mdC5jb20gLWFsbMAMABAAAQAADR8AODdhZG9iZS1zaWduLXZlcmlmaWNhdGlvbj1jMWZlYTliNGNkZDRkZjBkNTc3ODUxN2YyOWUwOTM0wAwAEAABAAANHwAuLWRvY3VzaWduPTUyOTk4NDgyLTM5M2QtNDZmNy05NWQ0LTE1YWM2NTA5YmZkZMAMABAAAQAADR8AXVxhZG9iZS1pZHAtc2l0ZS12ZXJpZmljYXRpb249OGFhMzVjNTI4YWY1ZDcyYmViMTliMWJkM2VkOWI4NmQ4N2VhN2YyNGIyYmEzYzk5ZmZjZDAwYzI3ZTlkODA5Y8AMABAAAQAADR8AJSRkMzY1bWt0a2V5PTRkOGJueWN4NDBmeTM1ODFwZXR0YTRnc2bADAAQAAEAAA0fAFlYOFJQRFhqQnpCUzl0dTdQYnlzdTdxQ0FDcndYUG9EVjhadExmdGhUbkM0eTlWSkZMZDg0aXQ1c1FsRUlUZ1NMSjRLT0lBOHBCWnhteXZQdWp1VXZoT2c9PcAMABAAAQAADR8ARURnb29nbGUtc2l0ZS12ZXJpZmljYXRpb249MVRlSzhxME96aUZsNFQxdEYtUVI2NUprekhaMXJjZGdOY2NERnA3OGlUa8AMABAAAQAADR8AJSRkMzY1bWt0a2V5PTN1YzFjZjgyY3B2NzUwbHprNzB2OWJ2ZjLADAAQAAEAAA0fADw7ZmFjZWJvb2stZG9tYWluLXZlcmlmaWNhdGlvbj1md3p3aGJiendtZzVmemdvdGMyZ281MW9sYzM1NjYAACkQAAAAAAAAAA==","Result":{},"Upstream":"127.0.0.1:5300","IP":"156.229.9.224","Elapsed":1031547,"Cached":true}
    

    Additional Information

    The upstream is Unbound 1.13.1. If possible, please provide an e-mail where I can forward the more sensitive info like query and stats file for analysis if needed.

  • DOH requests hang after a network reconnection

    DOH requests hang after a network reconnection

    • Version of AdGuard Home server: 0.106.3
    • How did you install AdGuard Home: docker
    • How did you setup DNS configuration: Adguard -> router -> ISP
    • If it's a router or IoT, please write device model: OPNsense
    • CPU architecture: Intel
    • Operating system and version: Ubuntu running with Docker containers

    Expected Behavior

    adguard should always keeps processing DNS requests.

    Actual Behavior

    Since the latest updates, AdGuard stops processing DNS requests. Even in the same vlan (excluding the router) the software stops listing to DNS requests. Logs keep empty, webgui and ping still works (no network issue)

    Screenshots

    PRTG polling my DNS setup, also pihole is deployed in the same setup an never show an alarm. It seems for now only related tot adguard. image

    Additional Information

    sudo docker run -d --name adguard --hostname adguard --net=hostnetwork --ip=172.16.1.253 --cap-add=NET_ADMIN --cap-add=CAP_NET_RAW --cap-add=CAP_NET_BIND_SERVICE -e TZ=Europe/Amsterdam -v /home/rodeho/docker/adguard/workdir:/opt/adguardhome/work -v /home/rodeho/docker/adguard/confdir:/opt/adguardhome/ --restart unless-stopped adguard/adguardhome

  • Choosing filter lists for AdGuard Home

    Choosing filter lists for AdGuard Home

    Prerequisites

    Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

    • [x] I am running the latest version
    • [x] I checked the documentation and found no answer
    • [x] I checked to make sure that this issue has not already been filed

    Problem Description

    As I was testing with a stock AGH install on AMD64 Windows, I noticed that the available selection of lists on default installations is still pretty weak: image

    So I think it's time to consider trusting some more lists enough for them to be included by default as well. I'd recommend one or more of the following (in mostly random order):

    —— Non-regional ——

    —— Regional ——

    And that's even without getting into more proof-of-concept-esque list purposes like censorship evasion lists, Nintendo DS online servers, software update blockers, anti-gambling, and so on. I also chose to exclude unofficial domains versions of ABP-formatted lists.

    Proposed Solution

    Add some more lists to default AdGuard Home installations.

    Alternatives Considered

    Adding a link to FilterLists.com on the filter settings page would've also been great, although I (who've worked very extensively on its list cataloguing) will be the first to admit that it's become a daunting site for newcomers to browse through, and is almost unusable on phones.

    Additional Information

    These list additions would be done independently of you guys' plans to create an official script to convert adblocker lists to AGH lists, and these list suggestions should hopefully not interfere with those plans of yours for the immediate time being.

  • how fix error 127.0.0.1:8618

    how fix error 127.0.0.1:8618

    Error: control/stats | Couldn't get stats_top from coredns: *url.Error Get http://127.0.0.1:8618/stats: dial tcp 127.0.0.1:8618: connect: connection refused | 502

  • Vetted blocklists thread

    Vetted blocklists thread

    AdGuard Home lets the user choose from a list of vetted blocklists.

    If you have in mind any lists that can be added there, please leave a comment in this thread, we'll consider it.

    Previous task with a relevant comments thread: https://github.com/AdguardTeam/AdGuardHome/issues/1325

    Requirements

    • Maintained
    • Clear purpose
    • We prefer (mostly) original lists to compilations (like Energized or oisd.nl). Maybe we should add a special section for compilations (?)
  • AdGuard Home cannot work for 5 minutes after boot, DNS timeouts (Raspberry Pi)

    AdGuard Home cannot work for 5 minutes after boot, DNS timeouts (Raspberry Pi)

    When setting the Upstream DNS servers from the default TLS to Cloudflare's DoH (https://cloudflare-dns.com/dns-query), rebooting the Pi causes AdGuard Home to behave unexpectedly once booted.

    No clients can use DNS, the DNS requests all timeout. Trying to visit the admin page causes the settings page to freeze and not load for a very long time, with errors about timeouts for version checks to github. If I can get it to eventually load, I need to clear the DoH entry so it reverts back to the default TLS entries.

    Once it uses TLS again, all clients can use DNS fine and the AdGuard Home admin interface works normally again.

    So DNS-over-HTTPS does not work for me once I restart the Pi.

  • When internet drops, Adguard stops serving all DNS requests, including rewrites.

    When internet drops, Adguard stops serving all DNS requests, including rewrites.

    • Version of AdGuard Home server:
    • How did you install AdGuard Home: Docker
    • How did you setup DNS configuration: dns over tls and https for upstream, half a dozen local rewrites
    • If it's a router or IoT, please write device model: Raspi 4
    • Operating system and version: Raspbian 64bit

    Expected Behavior

    Like a real DNs server, queries should be delivered from local zones and cached lookups, even when upstream servers are down.

    Actual Behavior

    All DNS queries fail and clients panic

    Screenshots

    Screenshot:

    Additional Information

  • Bootstrapping DOH and DOT uses system resolver on Windows

    Bootstrapping DOH and DOT uses system resolver on Windows

    Steps to reproduce

    1. Install as service
    2. Run ipconfig /flushdns
    3. Run AdGuardHome.exe -s start
    4. Run nslookup www.google.com

    Expected behavior

    Return something.

    Actual behavior

    If I get the timeout, always timeout. When the timeout, [Test upstreams] will get the error. But If I set any DNS (direct set IP) at the first upstream DNS, it will work.

    Config: AdGuardHome.zip

    Your environment

    | Description | Value | | - | - | | Version of AdGuard Home server: | v0.95-hotfix | How did you setup DNS configuration: | System | If it's a router or IoT, please write device model: | PC | Operating system and version: | Windows 10 x64/Windows 8.1 x64

  • AdGuard Home sending out excessive PTR requests in its CIDR range

    AdGuard Home sending out excessive PTR requests in its CIDR range

    Background I have two Raspberry Pi 4B units running the latest version of Raspberry Pi OS. Each unit has AdGuard Home installed on it and nothing more. AdGuard Home is latest version (0.106.2) and is configured identically for each unit.

    The presence of two units allows one unit to provide DNS service while the other is offline (e.g., to install software patches). The units are part of 10.0.10.0/24 and have respective IP addresses of 10.0.10.6 and 10.0.10.7. DHCP functionality is disabled for both units. (DHCP is managed by my firewall.)

    Problem Both units send excess PTR requests for other clients in the 10.0.10.0/24 range. The response is always SERVFAIL. For example, AdGuard Home at 10.0.10.6 may send out a PTR request of 1.10.0.10.in-addr.arpa for which the response is SERVFAIL. The unit may also query their own host names, e.g., AdGuard Home at 10.0.10.7 may send out a PTR request of 7.10.0.10.in-addr.arpa. How do I stop this behavior? Is this behavior from AdGuard Home, or could it be from the underlying Raspberry Pi OS?

    Attempted Solution There is a box to “Enable reverse resolving of clients’ IP addresses” under Settings --> DNS Settings. I have checked and then unchecked this box to ensure this feature is off. However, an unchecked box does not stop this behavior.

    Comments I did not have this problem before the recent upgrade to the version 106.x series. However, since the 106.x series has been released, I have also patched the Raspberry Pi OS a couple of times. Unfortunately, the PTR requests are so excessive that they populate the first few slots of the “Top Queried Domains”. The AdGuard Home units also occupy the first and second slots of the “Top clients”.

    2021-05-16_21-41-25

  • Request for Parental Control - Possiblity to set time slot to allow / block some kids devices to Internet or Services.

    Request for Parental Control - Possiblity to set time slot to allow / block some kids devices to Internet or Services.

    Prerequisites

    • [X] I have checked the Wiki and Discussions and found no answer

    • [X] I have searched other issues and found no duplicates

    • [X] I want to request a feature or enhancement and not ask a question

    Description

    Hi, and happy new year, here is a request I would like to have :

    What problem are you trying to solve?

    Block internet access during the night and some time slots for the kids devices.

    Proposed solution

    Block / Allow DNS requests via Parental Control for some devices based on time slots authorization.

    Alternatives considered

    No idea.

    Additional information

    Many thanks for the consideration of my request.

    Have a nice day.

  • Bump json5, babel-loader, css-loader, html-webpack-plugin, mini-css-extract-plugin, postcss-loader, react-hot-loader, webpack and webpack-cli in /client

    Bump json5, babel-loader, css-loader, html-webpack-plugin, mini-css-extract-plugin, postcss-loader, react-hot-loader, webpack and webpack-cli in /client

    Bumps json5 to 2.2.3 and updates ancestor dependencies json5, babel-loader, css-loader, html-webpack-plugin, mini-css-extract-plugin, postcss-loader, react-hot-loader, webpack and webpack-cli. These dependencies need to be updated together.

    Updates json5 from 2.2.0 to 2.2.3

    Release notes

    Sourced from json5's releases.

    v2.2.3

    v2.2.2

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)
    Changelog

    Sourced from json5's changelog.

    v2.2.3 [code, diff]

    v2.2.2 [code, diff]

    • Fix: Properties with the name __proto__ are added to objects and arrays. (#199) This also fixes a prototype pollution vulnerability reported by Jonathan Gregson! (#295).

    v2.2.1 [code, diff]

    • Fix: Removed dependence on minimist to patch CVE-2021-44906. (#266)
    Commits
    • c3a7524 2.2.3
    • 94fd06d docs: update CHANGELOG for v2.2.3
    • 3b8cebf docs(security): use GitHub security advisories
    • f0fd9e1 docs: publish a security policy
    • 6a91a05 docs(template): bug -> bug report
    • 14f8cb1 2.2.2
    • 10cc7ca docs: update CHANGELOG for v2.2.2
    • 7774c10 fix: add proto to objects and arrays
    • edde30a Readme: slight tweak to intro
    • 97286f8 Improve example in readme
    • Additional commits viewable in compare view

    Updates babel-loader from 8.1.0 to 8.3.0

    Release notes

    Sourced from babel-loader's releases.

    v8.3.0

    New features

    Full Changelog: https://github.com/babel/babel-loader/compare/v8.2.5...v8.3.0

    v8.2.5

    What's Changed

    New Contributors

    Full Changelog: https://github.com/babel/babel-loader/compare/v8.2.4...v8.2.5

    v8.2.4

    What's Changed

    Thanks @​loveDstyle, @​stianjensen and @​pathmapper for your first PRs!

    8.2.3

    This release fixes compatibility with Node.js 17

    Thanks @​Reptarsrage!

    8.2.1

    8.2.0

    • Replace mkdirp with make-dir 47958ca3857e489e450b27c6f3266375015cba82 (@​JLHwung)
    • Use async config loading when available d8cff97ff387ded0fc9b5cbc489228c96c5ab14a (@​the-spyke)
    Commits
    Maintainer changes

    This version was pushed to npm by nicolo-ribaudo, a new releaser for babel-loader since your current version.


    Updates css-loader from 3.5.3 to 6.7.3

    Release notes

    Sourced from css-loader's releases.

    v6.7.3

    6.7.3 (2022-12-14)

    Bug Fixes

    v6.7.2

    6.7.2 (2022-11-13)

    Bug Fixes

    • css modules generation with inline syntax (#1480) (2f4c273)

    v6.7.1

    6.7.1 (2022-03-08)

    Bug Fixes

    v6.7.0

    6.7.0 (2022-03-04)

    Features

    v6.6.0

    6.6.0 (2022-02-02)

    Features

    • added the hashStrategy option (ca4abce)

    v6.5.1

    6.5.1 (2021-11-03)

    Bug Fixes

    • regression with unicode characters in locals (b7a8441)
    • runtime path generation (#1393) (feafea8)

    v6.5.0

    ... (truncated)

    Changelog

    Sourced from css-loader's changelog.

    6.7.3 (2022-12-14)

    Bug Fixes

    6.7.2 (2022-11-13)

    Bug Fixes

    • css modules generation with inline syntax (#1480) (2f4c273)

    6.7.1 (2022-03-08)

    Bug Fixes

    6.7.0 (2022-03-04)

    Features

    6.6.0 (2022-02-02)

    Features

    • added the hashStrategy option (ca4abce)

    6.5.1 (2021-11-03)

    Bug Fixes

    • regression with unicode characters in locals (b7a8441)
    • runtime path generation (#1393) (feafea8)

    6.5.0 (2021-10-26)

    Features

    • support absolute URL in url() when experiments.buildHttp enabled (#1389) (8946be4)

    ... (truncated)

    Commits

    Updates html-webpack-plugin from 4.3.0 to 5.5.0

    Changelog

    Sourced from html-webpack-plugin's changelog.

    5.5.0 (2021-10-25)

    Features

    • Support type=module via scriptLoading option (1e42625), closes #1663

    5.4.0 (2021-10-15)

    Features

    5.3.2 (2021-06-22)

    Bug Fixes

    • update lodash and pretty error (9c7fba0

    5.3.1 (2021-03-09)

    Bug Fixes

    • remove loader-utils from plugin core (82d0ee8)

    5.3.0 (2021-03-07)

    Features

    • allow to modify the interpolation options in webpack config (d654f5b)
    • drop loader-utils dependency (41d7a50)

    5.2.0 (2021-02-19)

    Features

    5.1.0 (2021-02-12)

    Features

    • omit html tag attribute with null/undefined/false value (aa6e78d), closes #1598

    5.0.0 (2021-02-03)

    ... (truncated)

    Commits
    • 873d75b chore(release): 5.5.0
    • ddeb774 chore: update examples
    • 1e42625 feat: Support type=module via scriptLoading option
    • 7d3645b Bump pretty-error to 4.0.0 to fix transitive vuln for ansi-regex CVE-2021-3807
    • 79be779 [chore] changes actions to run on pull_requests
    • b7e5859 [chore] fixes CI to avoid race conditions
    • 48131d3 chore(release): 5.4.0
    • 16a841a [chore] rebuild examples
    • 3bb7c17 Update index.js
    • e38ac97 Update index.js
    • Additional commits viewable in compare view

    Updates mini-css-extract-plugin from 0.9.0 to 2.7.2

    Release notes

    Sourced from mini-css-extract-plugin's releases.

    v2.7.2

    2.7.2 (2022-12-06)

    Bug Fixes

    v2.7.1

    2.7.1 (2022-11-29)

    Bug Fixes

    v2.7.0

    2.7.0 (2022-11-16)

    Features

    • add function support for locals (loader) (#985) (65519d0)

    v2.6.1

    2.6.1 (2022-06-15)

    Bug Fixes

    • do not attempt hot reloading when emit is false (#953) (b426f04)

    v2.6.0

    2.6.0 (2022-03-03)

    Features

    • added baseUri option support (from entry options) (#915) (6004d95)

    v2.5.3

    2.5.3 (2022-01-25)

    Bug Fixes

    v2.5.2

    2.5.2 (2022-01-17)

    ... (truncated)

    Changelog

    Sourced from mini-css-extract-plugin's changelog.

    2.7.2 (2022-12-06)

    Bug Fixes

    2.7.1 (2022-11-29)

    Bug Fixes

    2.7.0 (2022-11-16)

    Features

    • add function support for locals (loader) (#985) (65519d0)

    2.6.1 (2022-06-15)

    Bug Fixes

    • do not attempt hot reloading when emit is false (#953) (b426f04)

    2.6.0 (2022-03-03)

    Features

    • added baseUri option support (from entry options) (#915) (6004d95)

    2.5.3 (2022-01-25)

    Bug Fixes

    2.5.2 (2022-01-17)

    Bug Fixes

    2.5.1 (2022-01-17)

    ... (truncated)

    Commits

    Updates postcss-loader from 3.0.0 to 7.0.2

    Release notes

    Sourced from postcss-loader's releases.

    v7.0.2

    7.0.2 (2022-11-29)

    Bug Fixes

    • support ESM version of postcss.config.js and postcss.config.mjs (#614) (955085f)

    v7.0.1

    7.0.1 (2022-07-11)

    Bug Fixes

    • unexpected failing on CSS syntax error (#593) (888d72e)

    v7.0.0

    7.0.0 (2022-05-18)

    ⚠ BREAKING CHANGES

    • minimum supported Node.js version is 14.15.0

    v6.2.1

    6.2.1 (2021-11-26)

    Bug Fixes

    v6.2.0

    6.2.0 (2021-10-13)

    Features

    v6.1.1

    6.1.1 (2021-07-01)

    Bug Fixes

    • do not swallow exception from postcss (2eec42b)

    v6.1.0

    6.1.0 (2021-06-10)

    ... (truncated)

    Changelog

    Sourced from postcss-loader's changelog.

    7.0.2 (2022-11-29)

    Bug Fixes

    • support ESM version of postcss.config.js and postcss.config.mjs (#614) (955085f)

    7.0.1 (2022-07-11)

    Bug Fixes

    • unexpected failing on CSS syntax error (#593) (888d72e)

    7.0.0 (2022-05-18)

    ⚠ BREAKING CHANGES

    • minimum supported Node.js version is 14.15.0

    6.2.1 (2021-11-26)

    Bug Fixes

    6.2.0 (2021-10-13)

    Features

    6.1.1 (2021-07-01)

    Bug Fixes

    • do not swallow exception from postcss (2eec42b)

    6.1.0 (2021-06-10)

    Features

    • allow String value for the "implementation" option (0d342b1)

    6.0.0 (2021-06-10)

    ... (truncated)

    Commits
    Maintainer changes

    This version was pushed to npm by evilebottnawi, a new releaser for postcss-loader since your current version.


    Updates react-hot-loader from 4.12.21 to 4.13.1

    Release notes

    Sourced from react-hot-loader's releases.

    🔥-rc for 17-rc

    Bug Fixes

    • tailUpdate might be blocked by a PureComponent (#1448) (e44103a)
    • provide "hot fallback" when module.hot is not truthy (#1451) (ec3447f)

    Features

    Changelog

    Sourced from react-hot-loader's changelog.

    Changelog

    All notable changes to this project will be documented in this file. See standard-version for commit guidelines.

    4.13.0 (2020-09-22)

    Bug Fixes

    Features

    Commits

    Updates webpack from 4.43.0 to 5.75.0

    Release notes

    Sourced from webpack's releases.

    v5.75.0

    Bugfixes

    • experiments.* normalize to false when opt-out
    • avoid NaN%
    • show the correct error when using a conflicting chunk name in code
    • HMR code tests existance of window before trying to access it
    • fix eval-nosources-* actually exclude sources
    • fix race condition where no module is returned from processing module
    • fix position of standalong semicolon in runtime code

    Features

    • add support for @import to extenal CSS when using experimental CSS in node
    • add i64 support to the deprecated WASM implementation

    Developer Experience

    • expose EnableWasmLoadingPlugin
    • add more typings
    • generate getters instead of readonly properties in typings to allow overriding them

    v5.74.0

    Features

    • add resolve.extensionAlias option which allows to alias extensions
      • This is useful when you are forced to add the .js extension to imports when the file really has a .ts extension (typescript + "type": "module")
    • add support for ES2022 features like static blocks
    • add Tree Shaking support for ProvidePlugin

    Bugfixes

    • fix persistent cache when some build dependencies are on a different windows drive
    • make order of evaluation of side-effect-free modules deterministic between concatenated and non-concatenated modules
    • remove left-over from debugging in TLA/async modules runtime code
    • remove unneeded extra 1s timestamp offset during watching when files are actually untouched
      • This sometimes caused an additional second build which are not really needed
    • fix shareScope option for ModuleFederationPlugin
    • set "use-credentials" also for same origin scripts

    Performance

    • Improve memory usage and performance of aggregating needed files/directories for watching
      • This affects rebuild performance

    Extensibility

    • export HarmonyImportDependency for plugins

    v5.73.0

    ... (truncated)

    Commits

    Updates webpack-cli from 3.3.11 to 5.0.1

    Release notes

    Sourced from webpack-cli's releases.

    v5.0.1

    5.0.1 (2022-12-05)

    Bug Fixes

    • make define-process-env-node-env alias node-env (#3514) (346a518)

    v5.0.0

    5.0.0 (2022-11-17)

    Bug Fixes

    • improve description of the --disable-interpret option (#3364) (bdb7e20)
    • remove the redundant utils export (#3343) (a9ce5d0)
    • respect NODE_PATH env variable (#3411) (83d1f58)
    • show all CLI specific flags in the minimum help output (#3354) (35843e8)

    Features

    • failOnWarnings option (#3317) (c48c848)
    • update commander to v9 (#3460) (6621c02)
    • added the --define-process-env-node-env option
    • update interpret to v3 and rechoir to v0.8
    • add an option for preventing interpret (#3329) (c737383)

    BREAKING CHANGES

    • the minimum supported webpack version is v5.0.0 (#3342) (b1af0dc), closes #3342
    • webpack-cli no longer supports webpack v4, the minimum supported version is webpack v5.0.0
    • webpack-cli no longer supports webpack-dev-server v3, the minimum supported version is webpack-dev-server v4.0.0
    • remove the migrate command (#3291) (56b43e4), closes #3291
    • remove the --prefetch option in favor the PrefetchPlugin plugin
    • remove the --node-env option in favor --define-process-env-node-env
    • remove the --hot option in favor of directly using the HotModuleReplacement plugin (only for build command, for serve it will work)
    • the behavior logic of the --entry option has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please use webpack --entry-reset --entry './src/my-entry.js'

    v4.10.0

    4.10.0 (2022-06-13)

    Bug Fixes

    Features

    v4.9.2

    4.9.2 (2022-01-24)

    ... (truncated)

    Changelog

    Sourced from webpack-cli's changelog.

    5.0.1 (2022-12-05)

    Bug Fixes

    • make define-process-env-node-env alias node-env (#3514) (346a518)

    5.0.0 (2022-11-17)

    Bug Fixes

    • improve description of the --disable-interpret option (#3364) (bdb7e20)
    • remove the redundant utils export (#3343) (a9ce5d0)
    • respect NODE_PATH env variable (#3411) (83d1f58)
    • show all CLI specific flags in the minimum help output (#3354) (35843e8)

    Features

    • failOnWarnings option (#3317) (c48c848)
    • update commander to v9 (#3460) (6621c02)
    • added the --define-process-env-node-env option
    • update interpret to v3 and rechoir to v0.8
    • add an option for preventing interpret (#3329) (c737383)

    BREAKING CHANGES

    • the minimum supported webpack version is v5.0.0 (#3342) (b1af0dc), closes #3342
    • webpack-cli no longer supports webpack v4, the minimum supported version is webpack v5.0.0
    • webpack-cli no longer supports webpack-dev-server v3, the minimum supported version is webpack-dev-server v4.0.0
    • remove the migrate command (#3291) (56b43e4), closes #3291
    • remove the --prefetch option in favor the PrefetchPlugin plugin
    • remove the --node-env option in favor --define-process-env-node-env
    • remove the --hot option in favor of directly using the HotModuleReplacement plugin (only for build command, for serve it will work)
    • the behavior logic of the --entry option has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please use webpack --entry-reset --entry './src/my-entry.js'

    4.10.0 (2022-06-13)

    Bug Fixes

    Features

    4.9.2 (2022-01-24)

    Bug Fixes

    • respect negatedDescription for flags from schema (#3102) (463b731)

    ... (truncated)

    Commits
    • 4a0f893 chore(release): publish new version
    • 9de982c chore: fix cspell
    • 32d26c8 chore(deps-dev): bump cspell from 6.15.1 to 6.16.0 (#3517)
    • 2788bf9 chore(deps-dev): bump eslint from 8.28.0 to 8.29.0 (#3516)
    • ac88ee4 chore(deps-dev): bump lint-staged from 13.0.4 to 13.1.0 (#3515)
    • 346a518 fix: make define-process-env-node-env alias node-env (#3514)
    • 3ec7b16 chore(deps): bump yeoman-environment from 3.12.1 to 3.13.0 (#3508)
    • c8adfa6 chore(deps-dev): bump @​types/node from 18.11.9 to 18.11.10 (#3513)
    • 0ad8cc2 chore(deps-dev): bump cspell from 6.15.0 to 6.15.1 (#3512)
    • d30f261 chore(deps-dev): bump ts-loader from 9.4.1 to 9.4.2 (#3511)
    • Additional commits viewable in compare view
    Maintainer changes

    This version was pushed to npm by evilebottnawi, a new releaser for webpack-cli since your current version.


    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate ...

    Description has been truncated

  • 100% cpu usage on all cores - rpi 3b+

    100% cpu usage on all cores - rpi 3b+

    Prerequisites

    • [X] I have checked the Wiki and Discussions and found no answer

    • [X] I have searched other issues and found no duplicates

    • [X] I want to report a bug and not ask a question

    Operating system type

    Linux, Other (please mention the version in the description)

    CPU architecture

    64-bit ARM

    Installation

    GitHub releases or script from README

    Setup

    On one machine

    AdGuard Home version

    latest beta

    Description

    I tried stress testing adguard home through a couple adblock tests like https://d3ward.github.io/toolz/adblock.html, and within a second or two adguard home reaches 100% cpu usage on all cores on this 3b+, only a couple dozen queries are being made, (with nothing but docker which has containers stopped running at the time).

    Tabby_0pTEY3hTps

    Not sure if this is normal for the 3b+, i also have roughly 2.3 million filters in total, have caching enabled, and only a couple small regex filters. However I never noticed high resource consumption in the past.

  •  Show total number of filters on blocklist page, and on custom filtering rules page

    Show total number of filters on blocklist page, and on custom filtering rules page

    Prerequisites

    • [X] I have checked the Wiki and Discussions and found no answer

    • [X] I have searched other issues and found no duplicates

    • [X] I want to request a feature or enhancement and not ask a question

    Description

    would be a useful metric to have

  • If a blocklist update, updates filter count to zero don't update blocklist

    If a blocklist update, updates filter count to zero don't update blocklist

    Prerequisites

    • [X] I have checked the Wiki and Discussions and found no answer

    • [X] I have searched other issues and found no duplicates

    • [X] I want to request a feature or enhancement and not ask a question

    Description

    What problem are you trying to solve?

    There's been a couple incidents where the website for blocklists have gone down and adguard home as a result updated the blocklists to 0 filters, since it couldn't find any

    Proposed solution

    Keeping the old blocklist, and skipping that time periods update, if the new filter count is 0.

  • www.24ur.com

    www.24ur.com

    Issue URL (Ads)

    https://www.24ur.com/

    Comment

    I have AdGuard home instaled on rasberry pi. I fixed static ip for rasberry pi on my router.

    AdGuard used to work fine responding with 0.0.0.0 to ads. But after some time (days) it stopped working. I was trying to figure out if this was something I did but I rerolled my system settings and even reinstalled my AdGuard on Rasberry pi but to no use it stopped blocking all ads either uTube or others.

    I tried edge and chrome and same thing happens. I find it interesting that after installing AdGuard on my PC which uses AdGuard Basic Filter if I am not mistaken ads are now blocked.

    This however is not what truly want I would like to block ads for my whole LAN and since it worked before there must be something wrong. If you need any further info I will provide. Also I would like to know if I can add this basic filter to my AdGuard Home that would probably block ads on all devices on my LAN but again it should work without this like it has before.

    Thank you and best regards,

    Maj

    Screenshots

    Screenshot 1

    Screenshot 1

    Screenshot 2

    Screenshot 2

    System configuration

    Information | value --- | --- Platform: | AdGuard Home Browser: | Chrome Filters: | Other:
    AdGuard DNS Other extensions used: | I have no extensions except Google Docs Offline, no antivirus software just windows firewall, no adblockers.

Hetzner-dns-updater - A simple tool to update a DNS record via Hetzner DNS API. Used for simple HA together with Nomad

hetzner-dns-updater A small utility tool to update a single record via Hetzner D

Feb 12, 2022
🚀Gev is a lightweight, fast non-blocking TCP network library based on Reactor mode. Support custom protocols to quickly and easily build high-performance servers.
🚀Gev is a lightweight, fast non-blocking TCP network library based on Reactor mode. Support custom protocols to quickly and easily build high-performance servers.

gev 中文 | English gev is a lightweight, fast non-blocking TCP network library based on Reactor mode. Support custom protocols to quickly and easily bui

Jan 6, 2023
Access Google Ads API via GRPC

google-ads-pb You can use the golang library to interact with the Google Ads API across grpc. This library is not the official Google Ads API library.

Dec 9, 2022
GoLang ads.txt scraper

Collects and parses ads.txt GoLang program scrapes sites for ads.txt and stores its significant details to PostgreSQL database. Give it a file with CS

Feb 11, 2022
🚀 gnet is a high-performance, lightweight, non-blocking, event-driven networking framework written in pure Go./ gnet 是一个高性能、轻量级、非阻塞的事件驱动 Go 网络框架。
🚀 gnet is a high-performance, lightweight, non-blocking, event-driven networking framework written in pure Go./ gnet 是一个高性能、轻量级、非阻塞的事件驱动 Go 网络框架。

English | ???? 中文 ?? Introduction gnet is an event-driven networking framework that is fast and lightweight. It makes direct epoll and kqueue syscalls

Jan 2, 2023
Netpoll is a high-performance non-blocking I/O networking framework, which focused on RPC scenarios, developed by ByteDance.
Netpoll is a high-performance non-blocking I/O networking framework, which focused on RPC scenarios, developed by ByteDance.

Netpoll is a high-performance non-blocking I/O networking framework, which focused on RPC scenarios, developed by ByteDance. RPC is usually heavy on processing logic and therefore cannot handle I/O serially. But Go's standard library net designed blocking I/O API, so that the RPC framework can only follow the One Conn One Goroutine design.

Jan 2, 2023
High-performance, non-blocking, event-driven, easy-to-use networking framework written in Go, support tls/http1.x/websocket.

High-performance, non-blocking, event-driven, easy-to-use networking framework written in Go, support tls/http1.x/websocket.

Jan 8, 2023
meek is a blocking-resistant pluggable transport for Tor.

meek is a blocking-resistant pluggable transport for Tor. It encodes a data stream as a sequence of HTTPS requests and responses. Requests are reflect

Nov 9, 2021
Middleware for Blocking IP ranges by inserting CIDR Blocks and searching IPs through those blocks

firewall Middleware for Blocking IP ranges by inserting CIDR Blocks and searching IPs through those blocks. Features Easy to use Efficient and Fast Co

Oct 9, 2022
A small tool used to correspond to the IP address according to the name, id, and network alias of the docker container, which can be run as a DNS server

A small tool used to correspond to the IP address according to the name, id, and network alias of the docker container, which can be run as a DNS server

Apr 4, 2022
DNS Ping: to check packet loss and latency issues with DNS servers

DNSping DNS Ping checks packet loss and latency issues with DNS servers Installation If you have golang, easiest install is go get -u fortio.org/dnspi

Nov 18, 2022
Verify IP addresses of respectful crawlers like Googlebot by reverse dns and forward dns lookups
Verify IP addresses of respectful crawlers like Googlebot by reverse dns and forward dns lookups

goodbots - trust but verify goodbots verifies the IP addresses of respectful crawlers like Googlebot by performing reverse dns and forward dns lookups

Aug 16, 2022
The Dual-Stack Dynamic DNS client, the world's first dynamic DNS client built for IPv6.

dsddns DsDDNS is the Dual-Stack Dynamic DNS client. A dynamic DNS client keeps your DNS records in sync with the IP addresses associated with your hom

Sep 27, 2022
netcup DNS module for caddy: dns.providers.netcup

netcup DNS module for Caddy This package contains a DNS provider module for Caddy. It can be used to manage DNS records with the netcup DNS API using

Nov 9, 2022
A fork on miekg/dns (since I've already forked zmap/dns)

Alternative (more granular) approach to a DNS library Less is more. Complete and usable DNS library. All Resource Records are supported, including the

Jan 19, 2022
A simple DNS forwarder that forwards DNS queries to various upstreams

A simple DNS forwarder that forwards DNS queries to various upstreams. If an upstream returns NXDomain, the next upstream is tried.

Jul 8, 2022
Designed to support DNS brute-forcing with a minimal number of network connections

Fast Use of DNS Resolvers Designed to support DNS brute-forcing with a minimal number of network connections. Installation go get -v -u github.com/caf

Dec 8, 2022
Capdns is a network capture utility designed specifically for DNS traffic. This utility is based on tcpdump.
Capdns is a network capture utility designed specifically for DNS traffic. This utility is based on tcpdump.

Capdns is a network capture utility designed specifically for DNS traffic. This utility is based on tcpdump. Some of its features include: Unde

Feb 26, 2022
Package socket provides a low-level network connection type which integrates with Go's runtime network poller to provide asynchronous I/O and deadline support. MIT Licensed.

socket Package socket provides a low-level network connection type which integrates with Go's runtime network poller to provide asynchronous I/O and d

Dec 14, 2022