Only through the proxy
Likely causes
- - Proxy resolves DNS remotely and fails
- - Local resolver blocks lookups
Verified remedy
Test remote DNS with curl --socks5-hostname; try a different endpoint country.
Proxy troubleshooting
Ranked causes, ordered diagnostics, and a verified remedy for err_name_not_resolved with proxy - ending with a final connection check.
Quick answer
Fix: ERR_NAME_NOT_RESOLVED through a proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Ranked causes, ordered diagnostics, and a verified remedy for err_name_not_resolved with proxy - ending with a final connection check.
Fix: ERR_NAME_NOT_RESOLVED through a proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Likely causes
Verified remedy
Test remote DNS with curl --socks5-hostname; try a different endpoint country.
Likely causes
Verified remedy
Compare dig output direct vs through the endpoint; remove stale hosts entries.
The action completes and the exit IP matches the endpoint.
If curl also fails, the endpoint is unhealthy: swap to a spare.
Facts last reviewed 2026-09-01.
DNS failures through a proxy are resolver-path failures; remote DNS via SOCKS5 keeps lookups on the endpoint identity.
Work the diagnosis tree top to bottom, confirm endpoint values, test with curl, then run the final connection check.
Buy self-serve now, or talk with us about a larger agency inventory.