TP-Link Archer BE230 V1 - DoH/DoT Not Working Properly with NextDNS
TP-Link Archer BE230 V1 - DoH/DoT Not Working Properly with NextDNS
TP-Link Archer BE230 V1 - DoH/DoT Not Working Properly with NextDNS
Device: Archer BE230 V1
Firmware Version: 1.1.3 Build 20241211 rel.47943(5553)
I'm experiencing issues with DoH/DoT on my Archer BE230 V1 when using NextDNS. The router either fails to connect entirely, or on rare occasions when it does, it does not send the client list properly.
Issues Observed:
- Intermittent Connection: The router only connects to NextDNS once in a while (if at all).
- Unidentified Devices: Even when connected, NextDNS does not recognize individual clients, despite enabling "Authorize Third-Party Services Client Identification" in the settings.
- No Error Feedback: The DoH/DoT settings page does not indicate whether the connection is failing, making troubleshooting difficult.
Steps Taken:
- Enabled DoH/DoT with NextDNS
- Verified NextDNS setup via CLI on other devices (works fine) but not on this router so the dns itself is functional
- Enabled "Authorize Third-Party Services Client Identification" (no change)
- Checked logs for DoH/DoT failures (no clear errors shown)
Is anyone else experiencing similar issues? Any workarounds or potential fixes? Would appreciate any input from the TP-Link team as well.
Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Yesrab wrote
yes but having nextdns on every device is pain in the rear also it defeates the purpose of having DOH in the router itself not being able to send client names is fine since it only effects statics in nextdns but not getting a stable dns connection is bad in be230 even with DOH/DOT ultra secure mode you can leak dns easily.
@Yesrab yes, the name is important. If you have blocks you need to be able to relate to which device saw it.
It's even more of a puzzle since I used the iOS profile method to setup a few iPhones and iPads and I've had trouble with my iPhone hanging to the point I had to remove the profile.
This shouldn't have anything to do with the router but it should work so ... the straight unencrypted DNS set in the router work OK.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 867
Replies: 11
Voters 0
No one has voted for it yet.