AdguardTeam / AdguardTeam/AdGuardHome

Extend url scheme to allow setting pre-resolved IPs for DoT and DoH

Aperta
#5,217 3 commenti 1 reazione 0 assegnatari Vedi su GitHub
feature request
Lingua principale
TypeScript
Stelle
36.9k
Fork
2.5k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### 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]` .

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.