For the IPv6 instance please add option force_ipv6_resolvers ‘1’.
If that works as well as I hope it does, let me know if you’re willing to amend the README. 
@stangri Is there any way to force https-dns-proxy to return only DNS A records for IPv4 resolvers / instances and only DNS AAAA records for IPv6 resolvers / instances ?
No dice. What is this option expected to do? It is not documented.
Looks like I also needed option force_ipv6 ‘1’…
That's not a valid config option name (it's only an internal variable name in the script), but maybe restarting https-dns-proxy again fixed it from the previous attempt.
Which one? force_ipv6 is documented here: https://docs.openwrt.melmac.ca/https-dns-proxy/
force_ipv6_resolvers is the correct one, at least in the instance definitions. force_ipv6 is wrong in the documentation as best I can tell.
Post the config again please.
You were right: it is working now without force_ipv6. I must have made a mistake the first time around. I now see IPv6 bootstrap IP on the command line and netstat shows a IPv6 connection established. All good now.
2 Likes
Hi and thanks for this easy to implement doh solution!
I force a reconnect with ifup waninterface at around 3:00 am, since my isp would do that for me anyway. Recently i found out that i dont have working dns for about an hour after that in my network. dns calls just time out. I have to do service https-dns-proxy restart and then it starts working again. Is that expected behaviour? I would expect the service to take note of the wan interface reconnecting.
It would hung up randomly for me too a few times a week without restarting any interfaces or doing anything on the router at all. I migrated to stubby a week ago and not a single issue so far.
Yep, it's just make and forget type of software.