Adguard Sucks whole internet over night || cant use "protection"

FoxXxHater commented 5 months ago

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 or ask for help
[X] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

Installation

Docker

Setup

On one machine

AdGuard Home version

latest (v0.107.46)

Action

Replace the following command with the one you're calling or a description of the failing action:

nslookup -debug -type=a 'www.google.com' '192.168.20.2'

PS C:\Users\John> nslookup -debug -type=a 'www.google.com' '192.168.20.2'

Got answer: HEADER: opcode = QUERY, id = 1, rcode = NXDOMAIN header flags: response, want recursion, recursion avail. questions = 1, answers = 0, authority records = 1, additional = 0

QUESTIONS:
    2.20.168.192.in-addr.arpa, type = PTR, class = IN
AUTHORITY RECORDS:
->  2.20.168.192.in-addr.arpa
    ttl = 10 (10 secs)
    primary name server = fake-for-negative-caching.adguard.com
    responsible mail addr = hostmaster.2.20.168.192.in-addr.arpa
    serial  = 100500
    refresh = 1800 (30 mins)
    retry   = 900 (15 mins)
    expire  = 604800 (7 days)
    default TTL = 86400 (1 day)

Server: UnKnown Address: 192.168.20.2

DNS request timed out. timeout was 2 seconds. timeout (2 secs) DNS request timed out. timeout was 2 seconds. timeout (2 secs) *** Zeitüberschreitung bei Anforderung an UnKnown.

Expected result

Dont know, that it works :LuL:

Actual result

If the "protection" is on no, and i mean NO connection is possible. But the pings to 1.1.1.1 or 8.8.8.8 are posible, so its not my ISP.

Yesterday everything works fine But at 2am the connection was down, the docker log of both AdGuard servers are full with the error entries...

Additional information and/or screenshots

The docker logs are attached. _AdGuard-update-24-11-23_logs.txt

FoxXxHater commented 5 months ago

P.S. If the protection is of the connection are back...

FoxXxHater commented 5 months ago

P.P.S. the 192.168.178.1 and the 192.168.20.2 isnt listed as upstream DNS server...

ghost commented 5 months ago

Are you able to access the dashboard when protection is enabled? Did you map the ports?

Ports mappings you may need:

-p 53:53/tcp -p 53:53/udp: plain DNS.

-p 67:67/udp -p 68:68/tcp -p 68:68/udp: add if you intend to use AdGuard Home as a DHCP server.

-p 80:80/tcp -p 443:443/tcp -p 443:443/udp -p 3000:3000/tcp: add if you are going to use AdGuard Home's admin panel as well as run AdGuard Home as an HTTPS/DNS-over-HTTPS server.

-p 853:853/tcp: add if you are going to run AdGuard Home as a DNS-over-TLS server.

-p 784:784/udp -p 853:853/udp -p 8853:8853/udp: add if you are going to run AdGuard Home as a DNS-over-QUIC server. You may only leave one or two of these.

-p 5443:5443/tcp -p 5443:5443/udp: add if you are going to run AdGuard Home as a DNSCrypt server.

FoxXxHater commented 5 months ago

Are you able to access the dashboard when protection is enabled? Did you map the ports?

Ports mappings you may need: -p 53:53/tcp -p 53:53/udp: plain DNS. -p 67:67/udp -p 68:68/tcp -p 68:68/udp: add if you intend to use AdGuard Home as a DHCP server. -p 80:80/tcp -p 443:443/tcp -p 443:443/udp -p 3000:3000/tcp: add if you are going to use AdGuard Home's admin panel as well as run AdGuard Home as an HTTPS/DNS-over-HTTPS server. -p 853:853/tcp: add if you are going to run AdGuard Home as a DNS-over-TLS server. -p 784:784/udp -p 853:853/udp -p 8853:8853/udp: add if you are going to run AdGuard Home as a DNS-over-QUIC server. You may only leave one or two of these. -p 5443:5443/tcp -p 5443:5443/udp: add if you are going to run AdGuard Home as a DNSCrypt server.

As already mentioned, everything worked wonderfully until around 2 and has done so for months... all necessary ports are gamapt. And I have switched off the protection via the web interface, so yes.

Cebeerre commented 5 months ago

the 192.168.178.1 and the 192.168.20.2 isnt listed as upstream DNS server...

If they show there, then they're configured as Private Resolvers.

Your log actually shows timeouts both connecting to your upstreams and the Adguard Family Protection DNS server, so I guess you ticked the "Adguard Parental control web service". That might not be caused 100% by your ISP, but it doesn't look like a bug.

FoxXxHater commented 5 months ago

Hay there,

what you are meaning with the "Adguard Parental control web service"? The interessting is... the fail comes at 2am in the night. I go 8pm offline (Sleeping) so nothing was changed...

FoxXxHater commented 5 months ago

I found my failure...

The Unify Console ha blocked the internet connection to the up DNS servers. You can't turn on the add filtering on that network from the AdGuard server and i blocked some south eastern network connections. So I turned it off and now it works!

AdguardTeam / AdGuardHome