Gdzie masz zainstalowane DNS HTTPS Proxy? Na routerze, na komputerze?

Jak masz zrobione DNS HTTPS Proxy? słucha bezpośrednio na porcie 53 czy masz pośrednika w postaci dnsmasq?

Jeżeli dobrze zrozumiałem jak to zrobiłes to masz wymuszone https-dns-proxy na porcie 53, więc ono robi na serwer dns forwardując zapytania dalej. Więc adblock nie będzie działał, bo on zapina się np. do dnsmasq. Musiał byś wywalić te opcje z sekcji config żeby dnsmasq normalnie słuchało na 53 i robiło forward na 5053/5054 na których słucha https-dns-proxy

Czyli oba na raz odpowiednio skonfigurowane.

Nie, to wywalić:

  option force_dns '1'
  list force_dns_port '53'
  list force_dns_port '853'

Ten post co stasowałeś - tam to było. Pokaż jeszcze raz wyniki poleceń

uci show dnsmasq
uci show https_dns_proxy

ls /etc/config

?

root@OpenWrt:~# uci show https-dns-proxy

https-dns-proxy.config=main
https-dns-proxy.config.force_dns_port='53' '853'
https-dns-proxy.config.force_dns='0'
https-dns-proxy.config.update_dnsmasq_config='-'
https-dns-proxy.@https-dns-proxy[0]=https-dns-proxy
https-dns-proxy.@https-dns-proxy[0].listen_addr='127.0.0.1'
https-dns-proxy.@https-dns-proxy[0].listen_port='5054'
https-dns-proxy.@https-dns-proxy[0].user='nobody'
https-dns-proxy.@https-dns-proxy[0].group='nogroup'
https-dns-proxy.@https-dns-proxy[0].bootstrap_dns='208.67.222.123,208.67.220.123'
https-dns-proxy.@https-dns-proxy[0].resolver_url='https://doh.familyshield.opendns.com/dns-query'
https-dns-proxy.@https-dns-proxy[1]=https-dns-proxy
https-dns-proxy.@https-dns-proxy[1].listen_addr='127.0.0.1'
https-dns-proxy.@https-dns-proxy[1].listen_port='5053'
https-dns-proxy.@https-dns-proxy[1].user='nobody'
https-dns-proxy.@https-dns-proxy[1].group='nogroup'
https-dns-proxy.@https-dns-proxy[1].bootstrap_dns='1.1.1.2,1.0.0.2,2606:4700:4700::1112,2606:4700:4700::1002'
https-dns-proxy.@https-dns-proxy[1].resolver_url='https://security.cloudflare-dns.com/dns-query'

root@OpenWrt:~# uci show dhcp

dhcp.@dnsmasq[0]=dnsmasq
dhcp.@dnsmasq[0].domainneeded='1'
dhcp.@dnsmasq[0].boguspriv='1'
dhcp.@dnsmasq[0].filterwin2k='0'
dhcp.@dnsmasq[0].localise_queries='1'
dhcp.@dnsmasq[0].rebind_protection='1'
dhcp.@dnsmasq[0].rebind_localhost='1'
dhcp.@dnsmasq[0].local='/lan/'
dhcp.@dnsmasq[0].domain='lan'
dhcp.@dnsmasq[0].expandhosts='1'
dhcp.@dnsmasq[0].nonegcache='0'
dhcp.@dnsmasq[0].authoritative='1'
dhcp.@dnsmasq[0].readethers='1'
dhcp.@dnsmasq[0].leasefile='/tmp/dhcp.leases'
dhcp.@dnsmasq[0].resolvfile='/tmp/resolv.conf.d/resolv.conf.auto'
dhcp.@dnsmasq[0].nonwildcard='1'
dhcp.@dnsmasq[0].localservice='1'
dhcp.@dnsmasq[0].ednspacket_max='1232'
dhcp.@dnsmasq[0].confdir='/tmp/dnsmasq.d'
dhcp.lan=dhcp
dhcp.lan.interface='lan'
dhcp.lan.leasetime='12h'
dhcp.lan.dhcpv4='server'
dhcp.lan.dhcpv6='server'
dhcp.lan.ra='server'
dhcp.lan.ra_flags='managed-config' 'other-config'
dhcp.lan.start='2'
dhcp.lan.limit='30'
dhcp.lan.force='1'
dhcp.wan=dhcp
dhcp.wan.interface='wan'
dhcp.wan.ignore='1'
dhcp.odhcpd=odhcpd
dhcp.odhcpd.maindhcp='0'
dhcp.odhcpd.leasefile='/tmp/hosts/odhcpd'
dhcp.odhcpd.leasetrigger='/usr/sbin/odhcpd-update'
dhcp.odhcpd.loglevel='4'
dhcp.monitoring=dhcp
dhcp.monitoring.interface='monitoring'
dhcp.monitoring.leasetime='12h'
dhcp.monitoring.start='2'
dhcp.monitoring.limit='25'
dhcp.monitoring.force='1'
dhcp.monitoring.ra_flags='none'

mam /etc/dnsmasq.conf

# Change the following lines if you want dnsmasq to serve SRV
# records.
# You may add multiple srv-host lines.
# The fields are <name>,<target>,<port>,<priority>,<weight>

# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 289
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389

# Two SRV records for LDAP, each with different priorities
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2

# A SRV record indicating that there is no LDAP server for the domain
# example.com
#srv-host=_ldap._tcp.example.com

# The following line shows how to make dnsmasq serve an arbitrary PTR
# record. This is useful for DNS-SD.
# The fields are <name>,<target>
#ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"

# Change the following lines to enable dnsmasq to serve TXT records.
# These are used for things like SPF and zeroconf.
# The fields are <name>,<text>,<text>...

#Example SPF.
#txt-record=example.com,"v=spf1 a -all"

#Example zeroconf
#txt-record=_http._tcp.example.com,name=value,paper=A4

# Provide an alias for a "local" DNS name. Note that this _only_ works
# for targets which are names from DHCP or /etc/hosts. Give host
# "bert" another name, bertrand
# The fields are <cname>,<target>
#cname=bertand,bert

No to teraz wywal te linie z https-dns-proxy, dodaj ew do konfiga dnsmasq linie z server i zobacz czy wszystko nadal działa.

hmmm... aż się zaciekawiłem i sprawdziłem u siebie i niby jedno i drugie śmiga razem:)
dziwne, że masz tyle problemów bo u mnie to chodzi "po wyjęciu z opakowania"