NextDNS Breaking Cookie/Login on Internal Web App — Need Help

Before installing Next DNS, my internal web application at https://mis.liveblog365.com/mra/public/ worked fine. After enabling Next DNS, the site loads but the login process fails — it displays a cookie consent/verification page that it never showed before, and I cannot proceed past it.

What I've tried:

(Add your troubleshooting steps here if any)

Symptoms:

Site opens ✅

Login triggers a cookie/verification wall ❌

Was working fine before Next DNS ✅

Screenshots: (attached)

Questions:

Is Next DNS blocking a cookie-related domain (e.g., session validation or auth service) that the login flow depends on?

How do I identify which domain is being blocked from the Next DNS query log?

Should I whitelist the entire domain, or is there a safer way to allow only the required auth endpoints?

My Setup:

Next DNS profile: (add your profile config — blocklists enabled, security settings, etc.)

Browser: (add)

Device: (add)

I've already allow listed my main domain and subdomain via Next DNS logs, but the cookie/login wall still appears at https://mis.liveblog365.com/mra/public/.

Is Next DNS blocking a third-party domain that the login flow depends on? How do I identify all domains involved in a login sequence — not just the main site? Should I use browser Dev tools (Network tab) alongside Next DNS logs to catch everything?

Screenshots attached.