| Previous | Next |
| WSA_QOS_RESERVED_PETYPE | WSA_IPSEC_NAME_POLICY_ERROR |
WSA_SECURE_HOST_NOT_FOUND
WSA_SECURE_HOST_NOT_FOUND is more specific than the traditional WSAHOST_NOT_FOUND. The word securely matters: a name can resolve through ordinary DNS yet still fail a Windows name-resolution path that requires a result accepted under secure name-resolution policy.
Do not reduce it to “DNS is down”
Windows can apply name-resolution policy and security mechanisms before a host result is accepted for an application. The useful comparison is the same hostname under the affected secure lookup path and under ordinary diagnostic resolution, while preserving the policy context.
What to collect
- The exact FQDN after suffix and IDN processing.
- Applicable Name Resolution Policy Table or IPsec/name-based policy.
- DNS response, DNSSEC-related validation data where relevant, and the resolver used.
- Whether the result changes by network profile, domain connectivity, VPN, or policy refresh.
Editing the application to connect directly to a remembered IP may bypass the intended name-based security decision and is not a valid fix. Diagnose why the secure name could not be established.
Microsoft: system and Winsock error codes · Microsoft: Name Resolution Policy Table · IETF: DNS Security introduction
Looking for a different code? Search another status or error code.