AdguardTeam / AdguardTeam/AdGuardHome

Query Log: Entries "Blocked" but really just redirected

Abierto
#3,926 4 comentarios 1 reacción 1 asignado Reclamado por @ainar-g Ver en GitHub
enhancement
Lenguaje dominante
TypeScript
Estrellas
36.9k
Forks
2.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### 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)

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.