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

MM 1 Reputation point
2022-10-18T02:33:31.657+00:00

Hi
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.
Regards,
M

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. MM 1 Reputation point
    2022-10-18T22:22:58.12+00:00

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

    0 comments No comments

  2. Anonymous
    2022-10-18T22:39:06.317+00:00

    Looking further it seems RODCs are not name servers by default.
    https://social.technet.microsoft.com/wiki/contents/articles/4031.how-read-only-domain-controllers-and-dns-works.aspx

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


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.