Brother engineer team next DNS as soon as possible help me

"The issue was previously fixed. I verified that it was resolved, and the system was no longer bypassing Private DNS when using NextDNS's non-filtering DNS as a custom DNS in the Chrome browser. However, this issue has resurfaced. It was only fixed for one day, and the same issue reappeared the next day."Subject: salmankamal622@gmail.com - Issue with Public NextDNS Bypassing Custom Filtering

Dear NextDNS Team,

I’m using your custom filtering settings, and they generally work great. However, I’ve noticed a specific issue. When I use your non-customized public DNS—the one without filtering—as a custom DNS in Chrome, it ends up bypassing my private DNS filtering entirely. In other words, if I put that public NextDNS address into Chrome’s custom DNS settings, it no longer respects the filtering I’ve set up through your private DNS. Other DNS services don’t bypass like this; it’s just the public NextDNS (without customization) that does.

I wanted to bring this to your attention in case you might consider adding an option to prevent this kind of bypass so that the private DNS filtering remains enforced.

Thank you for your attention.

Best regards,

Salman Kamal

salmankamal622@gmail.com