AdguardTeam / AdguardTeam/AdGuardHome

DNS-over-HTTPS/3 is reported as DNS-over-HTTPS/2 in query stats log

Đang mở
#5,501 1 bình luận 2 reaction 0 người được giao Xem trên GitHub
enhancement
Ngôn ngữ chính
TypeScript
Star
36.9k
Fork
2.5k
Chỉ số merge pull request
Không có pull request nào được merge trong 30 ngày

Mô tả

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

GitHub releases or script from README

### Setup

Other (please mention in the description)

### AdGuard Home version

108

### Description

I am running the latest AGH Edge version on RPi OS (Bullseye 64bit, Linux Kernel 6.1) and notice that DNS-over-HTTPS/3 is reported as DNS-over-HTTPS/2 in query stats logs. For example, domains resolved via "h3://94.140.14.14/dns-query" are reported as domains resolved via "https://94.140.14.14/dns-query". I know both are HTTPS, but I think the stats log should specify whether DNS-over-HTTPS/3 or DNS-over-HTTPS/2 was used. I did verify that DNS-over-HTTPS/3 was resolving via UDP port 443, which means DNS-over-HTTPS/3 works, but is simply reported as DNS-over-HTTPS/2.

Hướng dẫn đóng góp

Mở hướng dẫn đóng góp

Đánh giá

Issue này chưa được đánh giá.

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.