Please follow the below template, it will help us to help you!
Expected Behaviour:
When using Pi-hole with Cloudflare as a DNS forwarder in my Windows domain, it should show that DNSSEC is functioning and validating requests from my Windows 10 and Server 2012r2 clients.
Actual Behaviour:
Tests on Cloudflare Browser Check and http://dnssec.vs.uni-due.de/ show that DNSSEC is not working and fails validation on Windows clients when the client's DNS is pointed to my Windows Server 2012r2 DC. The DC is running DNS and the Pi-hole is set to be the forwarder. If I point a workstation directly to the Pi-hole for DNS, DNSSEC functions as expected and passes the validation tests.
Hello, yes, exactly right. I'm assuming its something within Windows DNS thats the issue. I made sure "Enable DNSSEC validation for remote responses" was checked in the properties of Windows DNS, and I even found a similar post on here from a user who had the same problem and was able to resolve it be reenabling that option in Windows DNS, but I'm not having any luck with either of these.
Since Pi-Hole appears to be working and that is what we support on this forum, we may not be able to help you with the Windows DNS issue. Perhaps a user on this forum has some experience.
You might also want to check some of the Windows DNS forums as well.