| Previous | Next |
| DNS_ERROR_DP_NOT_ENLISTED | DNS_ERROR_DP_NOT_AVAILABLE |
DNS_ERROR_DP_ALREADY_ENLISTED
The server is already enlisted in this DNS replication partition
Partition enlistment controls which application directory partitions a DNS server participates in for directory-backed DNS data. MS-DNSP tracks enlistment in the Application Directory Partition Table and exposes an explicit enlistment operation. Repeating an enlist request for a server that already participates does not create an additional replica role or another copy of the zone.
Verify the existing enlistment and then investigate the actual symptom that prompted the retry. If an AD-integrated zone is missing, check zone placement, load state, and replication rather than reenlisting the server. If the goal is to stop hosting the partition, use the supported unenlist operation after confirming no required zones rely on that replication scope.
What to inspect
- Enumerate the partition and confirm the target server is already a participant.
- Check whether the expected zone is stored in this partition and has replicated to the server.
- Treat missing zone data as replication or load diagnosis, not as evidence that enlistment must be repeated.
References
- MS-DNSP: zone and application directory partition management structures
- MS-DNSP: DNS Server initialization and zone loading
- MS-DNSP: DNS Server management operations
Looking for a different code? Search another status or error code.