Using the Proxy

Applications can use SOCKS5, an HTTP proxy for HTTP destinations, or HTTPS through HTTP CONNECT. Each method uses a Proxy Credential username and password and the matching endpoint displayed by MyOwnProxy. See Connection Details for method selection and examples.

Pool access is the normal and recommended method:

Application -> Gateway -> Pool -> Current Node -> Internet

The Pool's Current Node provides the public Internet exit IP for new connections. Pool access lets MyOwnProxy choose among eligible, available Nodes without requiring the application to target one directly.

Direct Node access is a secondary option for an application that must use a specific Node and its exit IP. It bypasses Pool selection and depends on that Node remaining available.

Both methods use the customer-controlled Gateway and Node data plane. Application proxy traffic does not pass through the MyOwnProxy control plane. See How MyOwnProxy Works and Data Plane Privacy.

Residential DNS resolution

When MyOwnProxy performs DNS resolution for a proxied hostname, that resolution follows the same residential Node as the proxy connection. DNS and proxy TCP traffic therefore use the same residential path, avoiding DNS and egress geography mismatches.

MyOwnProxy uses public DNS resolvers reached through that residential Node; the current IPv4 implementation uses Cloudflare resolvers. It does not use the Gateway hosting provider's resolver path. You do not need to configure DNS separately or make DNS-specific changes to the Node or Raspberry Pi, and MyOwnProxy does not expose a public DNS service.

If resolution is unavailable through the residential Node path, the request fails instead of falling back to the Gateway or hosting provider's resolver. This behavior applies when the application sends a hostname to the proxy for remote resolution. If the application resolves the hostname locally and sends only an IP address, MyOwnProxy does not perform or control that DNS lookup.

See Connection Details for protocol-specific behavior.

Connection guides

• Connection Details explains the endpoint and credential values required by an application.
• Connecting through a Pool covers the recommended Pool workflow.
• Connecting through a Specific Node covers optional fixed-Node access.
• Verifying Connection provides a short operational test and result checklist.
• Performance and Connection Optimization covers observed benchmark latency, connection reuse, and practical client settings.

For Proxy and Pool configuration, see Understanding Proxies and Pools. For credential scope and lifecycle, see Understanding Proxy Credentials.