@matoB I don't understand why people keep posting on this thread. They haven't fixed the issue in over five years, and this problem was known to them even before COVID. Due to their poor support, I ended up getting rid of all my TP-Link hardware, which I found to be mediocre at best. Despite the impressive stats, it never fully delivers. For example, my router struggled to handle more than 50 devices, and anything above that would cause random disconnects. This issue started after the latest firmware update, which I reported, but their response was indifferent.
 

I switched to ASUS routers, and now I have up to 80 devices connected with no issues. It handles everything I need, including DNS for the guest network.
 

TP-Link products are cheap for a reason. Unfortunately, I learned this the hard way, just like many of you.

@Lothos you're probably right, thanks for your post. I'm going to switch to ASUS too.

Currently, the BE63 is a power user device and this feature is needed for power users.

 

I don't really know why this is taking so long to implement as it has been requested years before I got a BE63. Either let us specify different DNS settings for the Guest and IoT network so we can specify non-local DNS addresses for guest networks, or allow DNS, DoH DoT,, etc.over local networks.

 

As it sits, the guest network does not work and the guest feature cannot be used for any networks that use a local DNS server.

 

This is definitely a bug. Power users are essential to get word of mouth and goodwill for your product, and right now, this BUG is definitely not wanting me to recommend this product to anyone.