| Previous | Next |
| DNS_ERROR_SUBNET_ALREADY_EXISTS | DNS_ERROR_POLICY_INVALID_WEIGHT |
DNS_ERROR_POLICY_LOCKED
DNS_ERROR_POLICY_LOCKED means DNS has a configuration lock on the policy. The policy should not be edited while another policy operation is still applying or rolling back.
Wait for the current DNS policy operation to finish and check management events before retrying. If the lock persists, investigate the operation that owns it rather than repeatedly issuing competing edits to the same policy.
What to check
- Ensure that another administrator, script, or configuration-management job is not changing DNS policies concurrently.
- Refresh the policy list and wait for the earlier operation to complete before retrying.
- If the condition persists, inspect DNS Server events for the operation that left the policy locked.
Get-DnsServerQueryResolutionPolicy
Get-DnsServerQueryResolutionPolicy -ZoneName "example.com"
Get-DnsServerClientSubnet
Microsoft: Get-DnsServerQueryResolutionPolicy
Looking for a different code? Search another status or error code.