| Previous | Next |
| DNS_ERROR_POLICY_INVALID_WEIGHT | DNS_ERROR_POLICY_MISSING_CRITERIA |
DNS_ERROR_POLICY_INVALID_NAME
DNS_ERROR_POLICY_INVALID_NAME indicates that the requested policy name does not meet DNS policy naming requirements.
What to verify for DNS_ERROR_POLICY_INVALID_NAME
- Use a unique, descriptive policy name that identifies the policy purpose and level.
- Do not use a name that collides with an existing policy at the same server or zone level.
- Keep a consistent naming convention across multiple DNS servers to make policy reviews auditable.
Get-DnsServerQueryResolutionPolicy
Get-DnsServerQueryResolutionPolicy -ZoneName "example.com"
Get-DnsServerClientSubnetMicrosoft: Add-DnsServerQueryResolutionPolicy
Microsoft: Get-DnsServerQueryResolutionPolicy
Microsoft: DNS Policies overview
Where the result is returned
This result is Win32 system error 9982 (0x000026FE) from winerror.h. AllStat describes it as “The DNS policy name is invalid.”. The code is useful only together with the API that failed, because multiple Windows components can reuse system-error values while imposing different retry and cleanup rules.
Diagnostic sequence
- Call GetLastError immediately after the failing API and save this result, the function name, all relevant flags, and the target path, handle, service, device, account, or policy object.
- Capture the component log that owns the dns / policy / name operation and retain the original numeric value before a framework converts it to an HRESULT or exception.
- compare preconditions with the API documentation and reproduce with a minimal request before changing system-wide configuration.
Retry this result only after the resource or state named in “The DNS policy name is invalid.” has changed. For invalid parameters, unsupported formats, missing objects, policy restrictions, and access failures, correct the input or configuration instead of immediately repeating the same call.
Looking for a different code? Search another status or error code.