| Previous | Next |
| DNS_ERROR_INVALID_SCOPE_OPERATION | DNS_ERROR_SCOPE_ALREADY_EXISTS |
DNS_ERROR_SCOPE_LOCKED
DNS_ERROR_SCOPE_LOCKED means the policy scope cannot be changed because DNS is processing another configuration operation that holds a lock on it.
Let the operation holding the scope lock finish and inspect DNS management events if it does not. Repeated edits against the locked object can obscure whether the original configuration change is still running or has stalled.
What to check
- Avoid simultaneous policy and scope changes from different administration sessions or automation jobs.
- Refresh the current configuration and wait for the previous operation to finish before retrying.
- Check the DNS Server event log if the lock persists, because a failed configuration transaction may be the real issue.
Get-DnsServerQueryResolutionPolicy
Get-DnsServerQueryResolutionPolicy -ZoneName "example.com"
Get-DnsServerClientSubnet
Microsoft: Get-DnsServerQueryResolutionPolicy
Looking for a different code? Search another status or error code.