AdguardTeam / AdguardTeam/AdGuardHome

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

Open
#5,501 1 comment 2 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
36.9k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

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

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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.