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.

I have a public IP

Dynamic DNS

Keep a hostname pointed at your current public IP when the ISP changes it.

Explore Dynamic DNS
I cannot port forward

Public Tunnel

Publish local web apps through an outbound-only tunnel without opening router ports.

Explore Public Tunnels
I am behind CGNAT

Static-IP Relay

Reach SSH, VPN, RDP, cameras, or other TCP services through a stable relay endpoint.

Explore Static-IP Relay

Choose by the problem, not by the acronym.

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.

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

Public Tunnel vs port forwarding

Compare direct router exposure with an outbound-only tunnel path.

Read comparison

Port forwarding not working?

Check the common failure points before deciding the router is the whole story.

Read guide

What is a reverse tunnel?

See how a local service becomes reachable without waiting for inbound traffic first.

Read guide

Compare Remote Access options

Developer tunnels

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 access

DNSExit 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 tunnels

DNSExit 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 Tunnel for browser-based services. Choose Static-IP Relay when the service is TCP-based or you need a stable endpoint behind CGNAT.

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 so we can prioritize the first tunnel and relay workflows.

;