Sign up ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.


I want to be able to access my laptop publicly from anywhere, while my laptop could also be anywhere. Any Service, any port.

Original Post:

I want to be able to access my own computer from a public domain so I can test OAuth integrations.

Setting up a CNAME record on my domain to point to my work address and forwarding ports to my computer is easy enough.

I move around a lot, and would still like to be able to publicly access my own computer.

I've looked into Dynamic DNS solutions, such as, but they require port forwarding. They are nice if I'm behind the same router all the time, but I am not.

So, I think I need some sort of tunnel or proxy service that will allow my computer to always be publicly available.

I tried searching for things like Dynamic DNS Tunnel, and it didn't seem like any services were easy to set up, or wouldn't clear that they would solve the problem I have. Ideally, I'd like to just have a program on my computer that connects to the proxy or tunnel, and point my domain at that.

I also wonder if it's possible to have something in Ruby create a tunnel, and host that on my account (or maybe another language Site5 is capable of running, idk, I'd have to look into that)... I wouldn't need to pay for anything extra then.

share|improve this question
I don't really understand what you're asking for, you seem to be linking DNS to a lot of functionality. Can you simplify the question, and describe the computers, and networks, and what services you're trying to connect to from where? –  EightBitTony Jun 21 '13 at 22:56
I added a TL;DR: –  NullVoxPopuli Jun 22 '13 at 5:55
1 –  Alex Oct 31 '13 at 9:11
From what I've seen, there are 2 ways when you don't control the router/gateway/firewall, if you control the server and client, you can establish a P2P/VPN network and talk through that and that will break through NAT. But if you want to allow arbitrary public internet clients to communicate with your server (like just a plain old HTTP request), you need to establish a third party tunnel that is connected between the server the public internet, and connect to that instead from your client. A combination of DDNS and ngrok can help with this. –  CMCDragonkai Oct 5 at 18:48

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.