DNSExit Remote Access

Stay reachable when the network underneath you gets awkward

Use Dynamic DNS when your public IP changes, Public Tunnel when you cannot port forward, and Static-IP Relay when you need a stable endpoint behind CGNAT or other blocked inbound access.

  • No router port forwarding needed for Public Tunnel or Static-IP Relay
  • Works behind CGNAT, even with no usable public IPv4
  • Dynamic DNS, domain DNS, email and tunnels in one account

How Public Tunnel and Static-IP Relay work

Both use an outbound client, so your device connects out to DNSExit and nothing waits for inbound traffic first. Only the public endpoint is different.

Your deviceHome server, NAS, camera, router or local app
outbound
DNSExitPublic endpoint for your service
You and your visitorsConnect by URL or by host and port
Changing IP only

Dynamic DNS is enough if inbound access already works.

No router access

Public Tunnel is the easier fit for browser-based services.

No public IPv4

Static-IP Relay is the stronger fit for TCP services behind CGNAT.

Compare at a glance

Pick the option that matches how your service needs to be reached.

Dynamic DNSPublic TunnelPublic Web TunnelStatic-IP RelayTCP Port Relay
Best whenInbound access works and only the public IP changesYou cannot port forward or have no router accessYou are behind CGNAT with no usable public IPv4
Port forwardingNeededNot neededNot needed
Behind CGNATNot enough on its ownYes, for web servicesYes
Public endpointYour hostname pointing at your IPWebsite URL such as https://ra9.tunnel.dnsexit.com or a custom domainServer and port such as remote1.dnsexit.com:22001
Good forAny service that is already reachableWeb dashboards, Home Assistant, webhook receivers, local web appsSSH, RDP, VPN, MikroTik, cameras, databases, other TCP services
Explore Dynamic DNS →Explore Public Tunnels →Explore Static-IP Relay →

Common Public Tunnel use cases

Learn before you choose

Compare Remote Access options

Common questions

Do I still need Dynamic DNS?

Yes, when inbound access already works and only the public IP changes. Remote Access is for the cases where a hostname alone is not enough.

Which product should I try first?

Choose Public Web Tunnel when the service should be reached by URL in a browser, such as a web dashboard, Home Assistant, webhook receiver, or local web app. Choose TCP Port Relay when the service needs host-and-port access, such as SSH, RDP, VPN, MikroTik, cameras, databases, or another TCP service.

What is the difference between Public Web Tunnel and TCP Port Relay?

Public Web Tunnel gives you a website-style endpoint such as https://ra9.tunnel.dnsexit.com or a custom domain. TCP Port Relay gives you a server-and-port endpoint such as remote1.dnsexit.com:22001. Both use an outbound client, but the public endpoint is different.

Does this help behind CGNAT?

Yes. Public Tunnel can expose local web services, while Static-IP Relay is the stronger fit when no usable public IPv4 exists.

Is signup open?

Yes. Signup is open, and DNSExit prepares the endpoint that fits each request.

Signup is open

Get started with Remote Access

Tell us what you need to reach remotely: web access without port forwarding, or a stable endpoint behind CGNAT. We use your answers to prioritize the first tunnel and relay workflows.

;