config main 'config'
option dnsmasq_config_update '*'
option force_dns '0'
option notrack_dns '0'
list force_dns_port '53'
list force_dns_port '853'
option procd_trigger_wan6 '0'
option verbosity '1'
option force_ipv6_resolvers '1'
config https-dns-proxy
option resolver_url 'https://doh.cleanbrowsing.org/doh/security-filter/'
option listen_addr '127.0.0.1'
option listen_port '5053'
option user 'nobody'
option group 'nogroup'
option bootstrap_dns '185.228.168.9,185.228.169.9'
config https-dns-proxy
option bootstrap_dns '1.1.1.1,1.0.0.1,2606:4700:4700::1111,2606:4700:4700::1001'
option resolver_url 'https://security.cloudflare-dns.com/dns-query'
option listen_addr '127.0.0.1'
option listen_port '5054'
option user 'nobody'
option group 'nogroup'
config https-dns-proxy
option bootstrap_dns '8.8.8.8,8.8.4.4,2001:4860:4860::8888,2001:4860:4860::8844'
option resolver_url 'https://dns.google/dns-query'
option listen_addr '127.0.0.1'
option listen_port '5055'
option user 'nobody'
option group 'nogroup'
(Blocks all adult content):IPv4: 185.228.168.168 and 185.228.169.168IPv6: 2a0d:2a00:1:: and 2a0d:2a00:2::Adult Filter
(Blocks adult content, safe search):IPv4: 185.228.168.10 and 185.228.169.11IPv6: 2a0d:2a00:1::10 and 2a0d:2a00:2::11Security Filter
(Blocks phishing, malware, scams):IPv4: 185.228.168.9 and 185.228.169.9IPv6: 2a0d:2a00:1::9 and 2a0d:2a00:2::9
I suspect, you should use âoption force_dns â1ââ. Otherwise, clients can bypass usage of dnsmasq+proxy, which might look like ânot resolvingâ.
Works for me. However, I have a slightly different environment as yours. Before going any further: Can you âping 185.228.168.9â ? Are you using any filtering software, i.e. adblocker or similar ? If not, pls provide ânft list rulesetâ
not sure if that is the problem but there is no bootstrap
You have set option force_ipv6_resolvers '1' but there is no IPv6 bootstrap DNS server set.
(Better not stray from the default settings if you are unsure what it means)
I just tested and it works fine for me but I am on the latest dns-https-proxy that could also play a role
`root@Defcon:~# ping 185.228.168.9
PING 185.228.168.9 (185.228.168.9): 56 data bytes
64 bytes from 185.228.168.9: seq=0 ttl=52 time=24.728 ms
64 bytes from 185.228.168.9: seq=1 ttl=52 time=24.590 ms
64 bytes from 185.228.168.9: seq=2 ttl=52 time=24.543 ms
64 bytes from 185.228.168.9: seq=3 ttl=52 time=24.634 ms
64 bytes from 185.228.168.9: seq=4 ttl=52 time=24.587 ms
64 bytes from 185.228.168.9: seq=5 ttl=52 time=24.609 ms
64 bytes from 185.228.168.9: seq=6 ttl=52 time=24.567 ms
64 bytes from 185.228.168.9: seq=7 ttl=52 time=24.551 ms
64 bytes from 185.228.168.9: seq=8 ttl=52 time=24.641 ms
64 bytes from 185.228.168.9: seq=9 ttl=52 time=24.560 ms
64 bytes from 185.228.168.9: seq=10 ttl=52 time=24.475 ms
64 bytes from 185.228.168.9: seq=11 ttl=52 time=24.597 ms
64 bytes from 185.228.168.9: seq=12 ttl=52 time=24.641 ms
64 bytes from 185.228.168.9: seq=13 ttl=52 time=24.609 ms
64 bytes from 185.228.168.9: seq=14 ttl=52 time=24.597 ms
64 bytes from 185.228.168.9: seq=15 ttl=52 time=24.528 ms
64 bytes from 185.228.168.9: seq=16 ttl=52 time=24.572 ms
64 bytes from 185.228.168.9: seq=17 ttl=52 time=24.538 ms
64 bytes from 185.228.168.9: seq=18 ttl=52 time=24.566 ms
64 bytes from 185.228.168.9: seq=19 ttl=52 time=24.582 ms
64 bytes from 185.228.168.9: seq=20 ttl=52 time=24.536 ms
64 bytes from 185.228.168.9: seq=21 ttl=52 time=24.609 ms
64 bytes from 185.228.168.9: seq=22 ttl=52 time=24.576 ms
64 bytes from 185.228.168.9: seq=23 ttl=52 time=24.590 ms`
Replace the bootstrap_dns value of the instance that is configured for doh.cleanbrowsing.org with - '2a0d:2a00:1::9,2a0d:2a00:2::9,185.228.168.9,185.228.169.9'
There is another thread with you, having issues with DDNS, Curl, embedtls and TLS 1.2/3 . May be, you are hit here, again. I am using OpenSSL, actually, for testing another issue. I can build my actual image, using mbedtls for https-dns-proxy, and test again. Needs couple of hours, though. Just to confirm: What says âhttps-dns-proxy -Vâ ?
