Remote access guide

How to access a home server without port forwarding

If your router cannot accept inbound traffic, a hostname alone will not make the service reachable. You need a path that starts outbound from inside the home network.

Dynamic DNSUse it when the network already accepts inbound traffic and only the IP changes.
Public TunnelUse it for browser-based home-server apps when port forwarding is unavailable.
Static-IP RelayUse it when the service is TCP-based or you need a stable endpoint behind CGNAT.

Why a home server may be unreachable

  • The ISP uses CGNAT.
  • The router belongs to someone else.
  • Inbound ports are blocked.
  • You prefer not to expose a new router port.

How to choose

  1. Check inbound accessIf the router can forward traffic, Dynamic DNS may already be enough.
  2. Identify the appIf it opens in a browser, Public Tunnel is usually the simpler next step.
  3. Stay narrowExpose only the one service you need instead of opening the whole network.

Need the web-first path?

See how DNSExit Public Tunnel is being built for home-server access when plain Dynamic DNS stops being enough.

See the use case Get started
Explore by goal

Keep moving with the guide that matches the problem.

Keep remote access working Start with Dynamic DNS when your public IP changes. Fix email delivery Separate outbound sending issues from inbound mail problems. Automate DNS and SSL Use API-driven DNS updates and validation workflows. Compare service options Choose the right email setup before you commit.
;