none
Implementing DNSSec

    Question

  • Hi,

    We have a customer who want to force their clients to use DNSSec. The problem is that these users and computers recide in a Windows 2016 domain with trusts to several other domains. I have tested in my test environment, and my experience is that computers will not resolve other internal domains through conditional forwarding or stub zones once DNSsec is required, and trust will not work.

    Is it some way to do this without implementing DNSsec in all domains? In Linux you have something called "negative thrust anchor", but I cant't find anything like this in Windows...

    Wednesday, May 15, 2019 7:45 AM

All replies

  • Hello,

    Thank you for posting in this forum.

    Have you consulted to this article?

    DNSSEC in Windows

    Best Regards,

    Leon


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, May 16, 2019 9:54 AM
  • Hi,
    Just checking the current situation of your problem.
    Please let us know if you would like further help.

    Best regards,
    Leon

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, May 21, 2019 9:06 AM
  • Hi,

    Was your issue resolved? 

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,
    Leon

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, May 23, 2019 8:39 AM