NextDNS has compatibility issues with Microsoft Defender's Network Protection
As the title suggests, enabling "Network Protection" in Microsoft/Windows Defender results in some kind of conflict between it and NextDNS. Despite the dashboard saying traffic is being blocked (Such as, say, Twitter.com), when I navigate to said site it isn't blocked whatsoever, which indicates NextDNS can't filter traffic. The issue is resolved when Network Protection is disabled.
The issue can be replicated by using a tool like ConfigureDefender to enable Network Protection