Discussed in this episode
- SOCKS5
- SOCKS5h
- DNS
- proxy
- privacy
- geo-targeting
- curl
- Python
- browser
- SocksNode
Show notes
Confused about the difference between SOCKS5 and SOCKS5h when setting up proxies? We break down why DNS resolution location matters for privacy and geo-targeting, how to set up each mode in curl, Python, and browsers, and how SocksNode supports secure SOCKS5 proxy use. Get practical answers for your proxy workflow.
Voices in this episode are AI-generated.
Full transcript
Welcome to the SocksNode podcast. Today’s question is: SOCKS5 vs SOCKS5h — why does DNS matter when you’re setting up a proxy?
If I’m using curl, Python, or a browser, what’s the real difference between socks5 and socks5h?
The main difference is where the DNS lookup happens. With SOCKS5, your device looks up the domain first, then tells the proxy to connect to the resulting IP. With SOCKS5h, your device sends the hostname to the proxy, and the proxy does the DNS lookup at its location.
So why does that matter for privacy or geo-targeting? Isn’t all my data going through the proxy anyway?
Not quite. If your device does the DNS lookup, your local DNS server—usually your ISP or office—sees what domains you’re visiting, even if the actual web traffic is proxied. That’s called a DNS leak. With SOCKS5h, the proxy does the DNS resolution, so your DNS queries look like they’re coming from the proxy, not your real network.
Does this affect what websites I see or how they respond to me?
Yes. If you’re testing or collecting public data and want to see what a user in another country would see, you need the DNS lookup to happen from that country. If you use regular SOCKS5, you might get different content or even hit the wrong server, because your local DNS resolver could return different IPs than the proxy’s resolver. SOCKS5h lines up your DNS and web traffic geography.
How do I make sure I’m using SOCKS5h and not just regular SOCKS5 in my tools?
In curl, it’s as simple as the scheme in your proxy URL. Use socks5h:// instead of socks5://. For example, curl --proxy socks5h://user:pass@proxyhost:port https://example.com will send the DNS request through the proxy. If you use socks5://, DNS resolves locally.
What about Python requests? Does it work the same way?
Almost. With Python requests and the requests[socks] extra, you set your proxies dictionary to use socks5h:// in the URL. That tells PySocks to send the hostname to the proxy. If you use socks5://, you may get local DNS resolution, depending on the version and settings.
And browsers? Is it easy to switch to remote DNS there?
It depends on the browser. In Firefox, go to the network settings and look for 'Proxy DNS when using SOCKS v5.' You need to check that box to get remote DNS with SOCKS5. In Chrome, it’s trickier. By default, Chrome uses system proxy settings and may resolve DNS locally. Some extensions like FoxyProxy let you enable DNS over SOCKS5, but always test to make sure.
How do I check if my DNS is leaking or if it’s really going through the proxy?
Use a DNS leak test site. Visit it while your proxy is active. If the DNS servers shown belong to your ISP or local network, you have a leak. If they match the proxy’s location, you’re set up correctly. It’s a good habit to test after any config change.
Are there cases where I shouldn’t use SOCKS5h or remote DNS?
If you need to access private or internal domains only resolvable on your local network, remote DNS won’t work. Also, some legacy apps don’t support SOCKS5h. And for ultra-low latency needs, local DNS is a bit faster, but most users prefer privacy and location accuracy.
Does SocksNode support SOCKS5h, and are there any special settings?
Yes, SocksNode supports SOCKS5 with username and password on all proxy types: residential, datacenter, mobile, and static IP. You can use socks5h:// in any client that supports it for remote DNS. No special settings are needed on the SocksNode side—just set up your client to use socks5h, and you get remote DNS resolution at the proxy’s location.
Can I geo-target my proxies and still get remote DNS?
Absolutely. With SocksNode residential proxies, you can target by country or US city using the username token. With SOCKS5h, both your web traffic and DNS requests will match the chosen location. That’s key for accurate market research, ad verification, or any geo-sensitive workflow.
What are the common mistakes people make with SOCKS5 and DNS?
The biggest mistake is using socks5:// instead of socks5h://, then assuming everything is private. Another is forgetting to test for DNS leaks after setup. Some people use browser extensions or tools that don’t support remote DNS, so their DNS queries still go local. Always check your client’s documentation, and run a DNS leak test.
Is there any difference in pricing or setup if I use SOCKS5h with SocksNode?
No, there’s no extra cost for using SOCKS5h. For residential proxies, prices start from fifty-three cents per gigabyte, with a minimum order of five gigabytes. There’s no monthly subscription, and your purchased traffic does not expire. For mobile proxies, it’s a flat rental per port—thirty dollars for thirty days on the Economy plan, so as low as one dollar per day. You just choose SOCKS5 as the protocol and set your client to use socks5h for remote DNS.
Any last advice for someone setting up proxies for privacy or geo-targeting?
Always use remote DNS—SOCKS5h—whenever privacy or location consistency matters. Test your setup with a DNS leak test. And if your client doesn’t support SOCKS5h, consider switching to one that does, or review the documentation to see if there’s a workaround.
Let’s recap. SOCKS5h matters because it pushes DNS lookups through your proxy, protecting privacy and making sure your requests match the proxy’s location. To use it, set your client to socks5h, check your browser or script settings, and always test for leaks. SocksNode supports SOCKS5 with remote DNS on all proxy types—visit socksnode dot com for details. The links are in the show notes.
FAQ
What is the main difference between SOCKS5 and SOCKS5h?
SOCKS5 resolves DNS locally on your machine, while SOCKS5h sends the hostname to the proxy for remote DNS resolution. This difference affects privacy and geo-targeting.
Why does remote DNS resolution matter for proxies?
Remote DNS resolution ensures that DNS queries originate from the proxy location, not your local network. This prevents DNS leaks and makes location targeting more accurate.
How do I configure curl to use remote DNS with SOCKS5?
Use the socks5h:// scheme in your proxy URL, e.g., curl --proxy socks5h://user:pass@proxyhost:port https://example.com.
Does Python requests support SOCKS5h?
Yes, when using requests with PySocks, specifying socks5h:// in the proxy URL enables remote DNS resolution. Always test your setup to confirm behavior.
How can I check if my DNS queries are leaking?
Visit a DNS leak test site with your proxy enabled. If the DNS resolver shown matches your local ISP, DNS is leaking; if it matches the proxy's location, remote DNS is working.
Do all browsers support remote DNS with SOCKS5?
Support varies. Firefox includes an explicit option to proxy DNS over SOCKS5. Chrome relies on system proxy settings and may require extensions for proper remote DNS.
What should I do if my client does not support SOCKS5h?
Consider switching to a client that does, or use additional privacy tools. Some legacy clients do not support remote DNS with SOCKS5 proxies.
Does SocksNode support SOCKS5 with remote DNS?
Yes. SocksNode supports standard SOCKS5 proxies with username/password authentication. Remote DNS resolution is available when your client supports the SOCKS5h scheme.
Explore SocksNode
- Residential proxies
- Mobile proxies
- Datacenter proxies
- Static IP proxies
- Documentation
- Compare residential vs mobile proxies
- Pricing
- Signup
More episodes on the SocksNode Proxy Insights podcast.
