Remote access guide

Remote access without port forwarding

Port forwarding is useful when you control the router and have public inbound access. When either piece is missing, you need a different path back into the service.

Dynamic DNSUse it when inbound access already works and only the public IP changes.
Public TunnelUse it for local web services when router changes are not practical.
Static-IP RelayUse it for TCP services or CGNAT situations where no public IPv4 exists.

Why port forwarding may not be available

  • Your ISP uses CGNAT.
  • You cannot change the router.
  • The network blocks inbound ports.
  • You want less exposure at the edge.

How to choose the fallback

  1. Check inbound accessIf your router has a public WAN IP and you can forward ports, Dynamic DNS may be enough.
  2. Identify the serviceBrowser-based service? Public Tunnel is usually simpler. TCP service? Static-IP Relay is more flexible.
  3. Start narrowExpose only the service you actually need, then expand once the workflow is proven.

Need a route that does not depend on port forwarding?

DNSExit Remote Access is being designed for the exact point where Dynamic DNS alone stops being enough.

See the home-server 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.
;