AdguardTeam / AdguardTeam/dnsproxy

Feature Request: Exclude cache for specific upstreams

Abierto
#480 0 comentarios 2 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Go
Estrellas
3.3k
Forks
343
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Problem

Local domains (`*.lan`, `*.local`, `*.home`) resolved by local DNS servers are cached alongside public domains.
These local domains often have frequent IP changes (DHCP) and low latency to resolve (local network), so there's little to no benefit to be gained from caching.

This is a particularly significant issue with **negative caching**.

### Example

Consider the following upstream DNS server configuration, where we want `*.lan` domains to be resolved by the local router and everything else to be resolved by a public DNS server:
```
[/lan/]192.168.1.1
1.1.1.1
```
and this scenario:
1. A local machine (`desktop.lan`) is currently powered off.
2. A client requests `desktop.lan`. The local upstream (192.168.1.1) returns NXDOMAIN because there is no active DHCP lease.
3. dnsproxy caches this NXDOMAIN response.
4. The user turns the machine on. Even though it now has an IP and the local DNS is aware of it, dnsproxy continues to return NXDOMAIN from the cache. The device remains unreachable by hostname until the cache expires.

### Proposed Solution

Allow a `?nocache` or similar tag on specific upstream lines:

[/lan/]192.168.1.1?nocache

1.1.1.1

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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.