| Previous | Next |
| DNS_ERROR_POLICY_MISSING_CRITERIA | DNS_ERROR_POLICY_PROCESSING_ORDER_INVALID |
DNS_ERROR_INVALID_CLIENT_SUBNET_NAME
DNS_ERROR_INVALID_CLIENT_SUBNET_NAME means the named client subnet is not valid for DNS Policy configuration. This is a naming/configuration issue before any query matching takes place.
Compare the proposed name with existing client-subnet objects and the exact name used by policy criteria. Correct the configuration identifier first; IP-prefix validity is a separate check performed after the object can be named.
What to check
- Use a stable logical name for the group of IPv4 and/or IPv6 prefixes.
- Check the exact spelling in both the client-subnet definition and the policy criterion.
- Inspect the target server to make sure a similarly named subnet was not created under a different name.
Get-DnsServerClientSubnet
Microsoft: Add-DnsServerClientSubnet
Looking for a different code? Search another status or error code.