RODC doesnt have its own Name server(NS) record in forward lookup zone

MM 1 Reputation point

We are running two Windows 2016 RODCs in our environment and i've noticed that the RODCs dont have its own Name server(NS) record in forward lookup zone.
The RODCs have SOA and NS records of the writable domain controllers but not its own.
Please advise if it is the right behaviour for RODCs and if not Please advise a solution for this.

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,414 questions
Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
1,028 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. MM 1 Reputation point

    Hi Mate,
    The ADD option is greyed out on RODC's DNS.
    Did you mean to add it on the Writable DC?

    0 comments No comments

  2. Dave Patrick 426.3K Reputation points MVP

    Looking further it seems RODCs are not name servers by default.

    --please don't forget to upvote and Accept as answer if the reply is helpful--