@wesley800
hosts
1.1.1.1 cloudflare-dns.com

will AdGuardHome ignore this hosts setting?

Prerequisites

• I have checked the Wiki and Discussions and found no answer
• I have searched other issues and found no duplicates
• I want to request a feature or enhancement and not ask a question

Description

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

Allow specifying resolver's IP address
AdguardTeam/dnsproxy#50
already done

Is this what you want?

hosts: 1.1.1.1 cloudflare-dns.com

I prefer a way to specify IP only for ADGH, so didn't tried this. Currently I'm using a dnsmasq for bootstrap, putting address=/1dot1dot1dot1.cloudflare-dns.com/1.1.1.1 in its setting. But adding extra dependencies is not so satisfactory.

AdguardTeam/dnsproxy#50

Sorry I didn't find a way to specify the IP in ADGH. Might this issue only related to the ADGH core (or dnsproxy, to be more specific), and my PR is about how to utilize it in ADGH for users? I'm not very sure though. Looking forward to repo members.