| Previous | Next |
| DNS_ERROR_DP_ALREADY_EXISTS | DNS_ERROR_DP_ALREADY_ENLISTED |
DNS_ERROR_DP_NOT_ENLISTED
This DNS server is not enlisted in the partition replication scope
An AD-integrated DNS zone can be stored in an application directory partition, and a DNS server loads directory-backed zones only from partitions in which it is enlisted. MS-DNSP initialization explicitly restricts directory zone loading to enlisted application directory partitions. The partition may exist in the forest while this server is not a replica for it.
Identify the partition that stores the zone and enumerate this server's enlistment state. If the server is supposed to host zones from that scope, enlist it using the supported DNS directory-partition operation and allow directory replication to converge. If the scope was intentionally limited, direct the management request to an enlisted DNS server instead of broadening replication without design review.
What to inspect
- Resolve the zone storage partition and the target server enlistment status.
- Check whether the partition replication scope intentionally excludes this DC.
- Enlist the server only when it should host that DNS data, then verify the zone loads after replication.
References
- MS-DNSP: DNS Server initialization and zone loading
- MS-DNSP: zone and application directory partition management structures
- MS-DNSP: DNS Server management operations
Looking for a different code? Search another status or error code.