AdguardTeam / AdguardTeam/AdGuardHome
Extend url scheme to allow setting pre-resolved IPs for DoT and DoH
- Vorherrschende Sprache
- TypeScript
- Sterne
- 36.9k
- Forks
- 2.5k
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### 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 request a feature or enhancement and not ask a question
### Description
[dnsproxy](https://github.com/AdguardTeam/dnsproxy) actually provides `upstream.Options.ServerIPAddrs` for manually defining the IPs used for DNS lookups of any upstream. For DoT and DoH upstreams, this can't be alternated by simply changing domain to IPs for non-tls upstreams, like `tcp://example.dns.server` to `tcp://1.2.3.4`, because of the hostname required in certificate validation. Unfortunately for now there's no way to utilize `ServerIPAddrs` field to build an TLS upstream with both domain and IP specified.
I suggest to add some magic params to the url for (single or multiple) server IP setting. e.g. `tls://1dot1dot1dot1.cloudflare-dns.com/?adguardhome_upstream_ip=1.1.1.1&adguardhome_upstream_ip=[2606:4700:4700::1001]` .
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.