How to Use Private AdGuard DNS-over-TLS or DNS Over HTTPS on GL-E750 Without AdGuard Home?

Hello GL-Inet Community,

I’m on a GL-E750 Mudi with a paid AdGuard DNS subscription and want to point all DNS traffic to my private AdGuard DNS-over-TLS or DNS-over-HTTPS endpoints—without running the resource-heavy AdGuard Home plugin. By default, under Network → DNS → Encrypted DNS, I only see:

  • Cloudflare
  • NextDNS

…and no place to enter my custom DoT URL (tls://<my-device-id>.d.adguard-dns.com:853). Here’s everything I’ve tried so far:

1. Native Encrypted DNS (DoT & DNSCrypt-Proxy)

  • DNS over TLS dropdown only lists Cloudflare/NextDNS.
  • DNSCrypt-Proxy dropdown only shows AdGuard’s public endpoints (no “Custom” field).

2. Editing /etc/config/https-dns-proxy

  • Added a config https-dns-proxy 'adguard_private' block with option name 'AdGuard-Private', my private DoH URL and bootstrap IPs.
  • Restarted the service, but LuCI still didn’t list my resolver—only showed a generic entry.

3. Installing Alternative LuCI Plugins

  • luci-app-https-dns-proxy: Installs OK, but UI only lets me choose predefined resolvers; custom entries don’t stick.
  • luci-app-dnsproxy: Not available in official Mudi repos.

4. SmartDNS (Recommended Lightweight Binary)

  • Installed via opkg install smartdns luci-app-smartdns.
  • Configured DoH upstream to my private AdGuard endpoint on port 6053.
  • Faced “NOT RUNNING” status and Permission denied on Save & Apply.
  • Fixed file permissions and edited UCI directly, but still no DNS resolution through the router.

5. Stubby (DNS-over-TLS via Service Stubby)

  • Enabled DoT in Network → DNS → Encrypted DNS by selecting Cloudflare to spin up Stubby.
  • Installed stubby package and edited /etc/stubby/stubby.yml to point at <my-device-id>.d.adguard-dns.com with the correct address_data.
  • Set uci set stubby.@stubby[0].manual='1' to force the custom config.
  • Updated Network → DHCP and DNS to forward to 127.0.0.1#853.
  • Stubby runs fine; DNS queries via dig @127.0.0.1 -p 853 example.com succeed—but I still can’t inject this into LuCI’s dropdown or guarantee all clients use it automatically.

Summary of Pain Points

  • No native “Custom” field for private DoT/DoH in Mudi v4.3.x
  • Predefined resolver lists in both HTTPS-DNS-Proxy and DNSCrypt-Proxy UIs
  • Alternative plugins either unavailable or unreliable
  • SmartDNS lightweight approach blocked by permission/UI issues
  • Stubby works under the hood but isn’t exposed cleanly in the UI

What I’m Looking For

  1. A clean LuCI-based method to enter custom AdGuard DNS-over-TLS URLs.
  2. Or a minimal-footprint plugin (lighter than AdGuard Home) that supports private DoT endpoints and integrates properly into the Services → DNS menu.
  3. Any CLI/UCI snippet or hack to extend the current dropdown with my private DoT link.

If you’ve successfully done this on a GL-E750 Mudi, please share your configuration steps or package recommendations. Thanks in advance....

I spent my whole day trying to figure it out together with AI but so far, nothing... Thanks for any further interaction...

Why not put DNS address in your Adguard home upstream?


Then your Adguard home make empty filters, put more filters in your account Adguard DNS server.
That's good light Adguard home

Thanks for the collaboration @slesar , but:

Thats what I’m using but, AdGuard home is extremely heavy for a system like Mudi GLE750.

The boot time of this router is 3 minutes, and still after 3 minutes it’s needed to wait one more minute to access the control panel.

With AdGuard Home active, sometimes after pressing the button to turn on, I just can really use my router after 5 minutes.

Not only this but, if I want to use any extra plugin is impossible, because with AdGuard Home running all the 128mb memory are consumed.

So, as the name of the topic says, I need a way to use my https, tls or quic AdGuard private dns WITHOUT using the application AdGuard home.

Anyway, thanks for answering.