User Tools

Site Tools


DNS over HTTPS with Dnsmasq and https-dns-proxy



  • Encrypt your DNS traffic improving security and privacy.
    • Prevent DNS leak and DNS hijacking.
  • Bypass regional restrictions using public DNS providers.
    • Escape DNS-based content filters and internet censorship.


Enable split DNS mode to encrypt LAN client DNS traffic assuming that local system traffic does not involve private data.

Use https-dns-proxy to encrypt DNS traffic. Configure Dnsmasq to forward DNS queries to https-dns-proxy. Enforce DNS encryption for LAN clients to avoid DNS leak.

# Install packages
opkg update
opkg install dnsmasq https_dns_proxy
# Enable DNS encryption
uci -q delete dhcp.@dnsmasq[0].server
DOHPROXY_ADDR="$(uci get https_dns_proxy.@https_dns_proxy[0].listen_addr)"
DOHPROXY_PORT="$(uci get https_dns_proxy.@https_dns_proxy[0].listen_port)"
uci add_list dhcp.@dnsmasq[0].server="${DOHPROXY_SERV}"
# Enforce DNS encryption for LAN clients
uci set dhcp.@dnsmasq[0].noresolv="1"
uci commit dhcp
/etc/init.d/dnsmasq restart
# Start the https_dns_proxy plugin
/etc/init.d/https_dns_proxy enable
/etc/init.d/https_dns_proxy start


Verify that domain name resolution works.

nslookup localhost

Check your DNS provider. Make sure there is no DNS leak.

Test DNSSEC validation.


Collect and analyze the following information.

# Restart the services
/etc/init.d/log restart; /etc/init.d/dnsmasq restart; /etc/init.d/https_dns_proxy restart
# Log and status
logread -e dnsmasq; netstat -l -n -p | grep -e dnsmasq
logread -e https_dns_proxy; netstat -l -n -p | grep -e https_dns
# Runtime configuration
pgrep -f -a dnsmasq; pgrep -f -a https_dns_proxy
# Persistent configuration
uci show dhcp; uci show https_dns_proxy


Web interface

Install the necessary packages if you want to manage the settings via web interface.

# Install packages
opkg update
opkg install luci-app-https_dns_proxy
  • Navigate to LuCI → Network → DHCP and DNS to configure Dnsmasq.
  • Navigate to LuCI → Services → HTTPS DNS Proxy to configure https-dns-proxy.

DoH provider

https-dns-proxy is configured with Google DNS by default. You can change it to another DoH provider. Make sure selected provider supports DNSSEC validation if required. Specify several servers to improve fault tolerance.

# Configure DoH provider
while uci -q delete https_dns_proxy.@https_dns_proxy[0]; do :; done
uci set https_dns_proxy.dns="https_dns_proxy"
uci set https_dns_proxy.dns.listen_addr=""
uci set https_dns_proxy.dns.listen_port="5053"
uci set https_dns_proxy.dns.user="nobody"
uci set"nogroup"
uci set https_dns_proxy.dns.url_prefix=""
uci commit https_dns_proxy
/etc/init.d/https_dns_proxy restart

Local system

Local system does not use Dnsmasq as a primary resolver when DNS encryption is enabled. Enforce Dnsmasq as a primary resolver to provide DNS encryption for local system. Bypass DNS encryption for NTP provider to avoid deadlock state when system time is not synchronized. Beware of race condition with Adblock service.

# Enforce DNS encryption for local system
uci set dhcp.@dnsmasq[0].localuse="1"
# Fetch DNS provider
. /lib/functions/
network_find_wan NET_IF
network_find_wan6 NET_IF6
network_get_dnsserver NET_DNS "${NET_IF}"
network_get_dnsserver NET_DNS6 "${NET_IF6}"
# Bypass DNS encryption for NTP provider
uci get system.ntp.server \
| sed -e "s/\s/\n/g" \
| sed -e "s/^[0-9]*\.//" \
| sort -u \
| while read -r NTP_DOMAIN
uci add_list dhcp.@dnsmasq[0].server="/${NTP_DOMAIN}/${NET_DNS%% *}"
uci add_list dhcp.@dnsmasq[0].server="/${NTP_DOMAIN}/${NET_DNS6%% *}"
uci commit dhcp
/etc/init.d/dnsmasq restart
This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
docs/guide-user/services/dns/doh_dnsmasq_https-dns-proxy.txt · Last modified: 2019/10/11 22:42 by stansmith