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
Which one do I need?
Choose by the problem, not by the acronym.
I have a public IPDynamic DNSKeep a hostname pointed at your current public IP when the ISP changes it.› I cannot port forwardPublic TunnelPublish local web apps through an outbound-only tunnel without opening router ports.› I am behind CGNATStatic-IP RelayReach SSH, VPN, RDP, cameras, or other TCP services through a stable relay endpoint.›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.
Dynamic DNS is enough if inbound access already works.
Public Tunnel is the easier fit for browser-based services.
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 DNS | Public TunnelPublic Web Tunnel | Static-IP RelayTCP Port Relay | |
|---|---|---|---|
| Best when | Inbound access works and only the public IP changes | You cannot port forward or have no router access | You are behind CGNAT with no usable public IPv4 |
| Port forwarding | Needed | Not needed | Not needed |
| Behind CGNAT | Not enough on its own | Yes, for web services | Yes |
| Public endpoint | Your hostname pointing at your IP | Website URL such as https://ra9.tunnel.dnsexit.com or a custom domain | Server and port such as remote1.dnsexit.com:22001 |
| Good for | Any service that is already reachable | Web dashboards, Home Assistant, webhook receivers, local web apps | SSH, RDP, VPN, MikroTik, cameras, databases, other TCP services |
| Explore Dynamic DNS → | Explore Public Tunnels → | Explore Static-IP Relay → |
Common Public Tunnel use cases
Home server without port forwarding
Reach a self-hosted dashboard or web app when the router cannot accept inbound traffic.
View use case →Webhook testing
Receive callbacks from public services while developing against a local app.
View use case →Share a local web app
Send a preview link before you deploy a demo, review build, or temporary site.
View use case →Learn before you choose
What is CGNAT?
Understand why some home connections cannot receive direct inbound traffic at all.
Read guide → ComparisonPublic Tunnel vs port forwarding
Compare direct router exposure with an outbound-only tunnel path.
Read comparison → GuidePort forwarding not working?
Check the common failure points before deciding the router is the whole story.
Read guide → GuideMikroTik behind CGNAT
See when RouterOS Dynamic DNS is enough and when a relay or tunnel is needed.
Read guide → GuideWhat is a reverse tunnel?
See how a local service becomes reachable without waiting for inbound traffic first.
Read guide →Compare Remote Access options
DNSExit as an ngrok alternative
Compare Public Tunnel and Static-IP Relay for local apps, webhooks, home labs, and small teams.
Read comparison → DNS and accessDNSExit as a Cloudflare Tunnel alternative
Use Remote Access when you want Dynamic DNS, domain DNS, email, and tunnels in one account.
Read comparison → DDNS plus tunnelsDNSExit as a No-IP alternative
Start with Free Dynamic DNS, then add Public Tunnel or Static-IP Relay when DDNS alone is not enough.
Read comparison →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.
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.