AdguardTeam / AdguardTeam/AdGuardHome

Block list fetching does not respect to per-client upstreams and bootstrap upstreams

Aperta
#8,420 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub
needs investigation
Lingua principale
TypeScript
Stelle
36.9k
Fork
2.5k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### Prerequisites

- [x] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) 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](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)

- [x] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)

### Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

### Installation

GitHub releases or script from README

### Setup

On one machine

### AdGuard Home version

AdGuard Home, version v0.107.77

### Action

Added a client upstream `[/example.com/]127.0.0.11`(the docker dns) for `127.0.0.1`, `::1`, `172.10.0/16`(the docker network).
Added boostrap upstream `127.0.0.11`(the docker dns).
Adding a custom blocklist serving from a local server with custom domain in the same docker network as AdGuardHome. It used the global upstream and failed to resolve the domain.

### Expected result

Queries from AdGuardHome itself, unless upstream server domain, should respect to per-client settings, where there's a rule for querying the custom domain of block list url in this case.

Some preliminary thoughts:
* Respect per-client settings for queries from AdGuardHome itself, with ip `127.0.0.1`
* Fallback to global bootstrap upstream to resolve blocklist fetching.
* Provide a builtin ClientID that identifies queries from AdGuardHome itself.

### Actual result

AdGuardHome ignores per-client settings, instead it uses global upstream settings and fails.

### Additional information and/or screenshots

`nslookup` queries from inside AdGuardHome container correctly goes into expected per-client upstream.

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.