AdguardTeam / AdguardTeam/AdGuardHome

Local DNS zones and cached responses aren't served after the network lost

Ouverte
#4,825 71 commentaires 8 réactions 1 personne assignée Réclamée par @EugeneOne1 Voir sur GitHub
bug needs investigation
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 have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/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

### Operating system type

Linux, Other (please mention the version in the description)

### CPU architecture

64-bit ARM

### Installation

Docker

### Setup

On one machine

### AdGuard Home version

v0.107.9

### Description

This is a continuation of the thread started in #2657. The problem's first occurance was in v0.104.3 and has already been fixed a couple of times but still reported. We can't reproduce the issue on our machines. If you've faced it, please consider providing the following information:

* the setup details (the OS, CPU architecture, installation type);
* the environment details (other DNS servers, DHCP server);
* the "General settings", "Cache" and "Encryption" configuration parts (any other details on AdGuard Home's configuration are appreciated);
* the [verbose log](https://github.com/AdguardTeam/AdGuardHome/wiki/FAQ#verboselog) with the network loss moment captured.

The last two pieces of information (optionally anonymized) could be sent to devteam@adguard.com with **this issue's number** in the subject.

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.