Background:

 

This guide offers a comprehensive troubleshooting guide on DNS Proxy.

 

This Article Applies to:

 

All TP-Link(Omada) routers with DNS Proxy features are available.

 

Troubleshooting Steps:

 

1. Prepare Wireshark and Port Mirroring. If you need help with this, please use the guides:

How to capture packets using Wireshark on an SMB router or switch

How to configure Port Mirror on TP-Link routers

WAN IP is 192.168.0.103.

Test PC is 192.168.10.6.

DoH is set to be Cloudflare HTTPS.

 

2. Test the LAN DNS resolution and WAN DNS.

 

There are no overlapped results in comparison which means the LAN > Gateway > ISP > DoH is not leaking to the ISP. 

 

 

3. Verify the DNS resolution sent to the desired DoH server instead of others.

In this case, only one DoH is enabled. Cloudflare is used.

Online Detection is set at a different address.

 

 

4. Test with Cloudflare official server using Firefox in Private Mode with DNS flushed.

 

 

5. On computer 192.168.10.6, the tested computer in this guide, accesses the youtube.com. The resolution is not leaking on the WAN. No plain text DNS on the WAN.

 

 

Update Log:

 

Mar 21st, 2025:

Release of this article.

 

Recommended Threads:

 

How to Configure Local DNS Server on Omada Router

How to configure DNS Proxy on the Omada Gateway

How to Disable NAT in Controller Mode and Verify its Status

 

Feedback:

 

• If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
• If there is anything unclear in this solution post, please feel free to comment below.

 

Thank you in advance for your valuable feedback!

 

------------------------------------------------------------------------------------------------

Have other off-topic issues to report? 

Welcome to > Start a New Thread < and elaborate on the issue for assistance.