AdguardTeam / AdguardTeam/AdGuardHome

Query Log: Entries "Blocked" but really just redirected

Ouverte
#3,926 4 commentaires 1 réaction 1 personne assignée Réclamée par @ainar-g Voir sur GitHub
enhancement
Langage dominant
TypeScript
Étoiles
36.9k
Forks
2.5k
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

### Prerequisites

- [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:**
* v0.106.3
* **How did you install AdGuard Home:**
* GitHub release
* **How did you setup DNS configuration:**
* router with AdGuard upstream and AdGuard IPs as DNS in DHCP settings
* **If it's a router or IoT, please write device model:**
* USG-3p
* **CPU architecture:**
* amd64
* **Operating system and version:**
* TrueNAS Core 12.0-U7 (FreeBSD 12)

### Expected Behavior
Entries should be marked as _Redirected_ or _/etc/hosts style redirect_, or something more indicative of _not explicitly_ being **Blocked** in Query Log.

### Actual Behavior
Entries in Query Log end up **Blocked** when they're configured to be managed/redirected by an _/etc/hosts_ style entry in _Custom filtering rules_.

### Screenshots
![adguard-querylog](https://user-images.githubusercontent.com/16342210/145566149-1ee4f2ff-e026-4d47-ab1b-cdf7cee68cac.png)

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.