AdguardTeam / AdguardTeam/AdGuardHome
Bug: DoH/DoT/DoQ/HTTPS only listen on IPv4, no IPv6 support
- 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 have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) 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 or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)
- [x] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)
### Platform (OS and CPU architecture)
Darwin (aka macOS), AMD64 (aka x86_64)
### Installation
GitHub releases or script from README
### Setup
On one machine
### AdGuard Home version
v0.107.73
### Action
# 1. Test DoH via IPv6
https://[2400:3200::1]/dns-query
# 2. Test DoT via IPv6
tls://[2400:3200::1]
# 3. Test DoQ via IPv6 (using dog command)
quic://[2400:3200::1]
### Expected result
All encrypted DNS services (DoH/DoT/DoQ) and the HTTPS admin panel should work normally via both IPv4 and IPv6.
The server should listen on :: (all IPv6 addresses) for ports 443, 853, 853
### Actual result
1. All the above tests fail when using IPv6 address (connection timeout/refused).
2. All tests work perfectly when using IPv4 address on the same ports.
3. Plain DNS (UDP/TCP 53) works fine on both IPv4 and IPv6.
4. Checking port listening with `ss -tuln` shows ports 443/853/853 are only bound to IPv4 (0.0.0.0), not IPv6 (::)
### Additional information and/or screenshots
### Environment
- Network: Dual-stack (IPv4 + IPv6), public IPv6 is available.
- Firewall: Ports 443, 853, 853 are allowed for both IPv4 and IPv6.
- Certificate: Valid domain SSL certificate configured correctly.
### Config snippet (config.yaml)
```yaml
dns:
bind_hosts:
- 0.0.0.0
- ::
- 127.0.0.1
- ::1
port: 53
tls:
enabled: true
server_name: [2400:3200::1]
force_https: true
port_https: 443
port_dns_over_tls: 853
port_dns_over_quic: 853
certificate_chain: "/path/to/fullchain.pem"
private_key: "/path/to/privkey.pem"
serve_http3: true
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.