Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to remotely connect to home machine through Windows Remote Desktop (amongst other things, but this is currently my primary focus). I can do this fine using my home WAN's static IP (thank god for cable!) with port-forwarding, but I would like to access it from a subdomain of my web-site (e.g.

In the cPanel for my hosting account, I've gone into DNS zones and altered the A-record to point to my WAN's IP, which I thought should do the job, but I still cannot connect. When I ping the subdomain, I get my web-host's IP, which I guess is to be expected as I believe the DNS of the host domain is used first, then my server handles the redirection of traffic to the IP in the A-record. Is this the correct idea? Do A-record changes suffer from the same propagation delays as DNS record changes, as I suppose that could explain it?

(by the way, this thread confirms my thoughts that setting the A-record should be enough: Hostmonster Subdomain redirected to home server IP: How to ssh into home server using subdomain)

share|improve this question
If they are cached locally or the DNS server you use is serving cached entries and the TTL has not passed, then yes you have to wait it out. You should set a really low TTL for that entry/zone if you plan on updating it frequently. – SleighBoy Feb 2 '12 at 7:38
Yeah it's working now - I guess I was just being impatient! Thanks for your advice on TTL - I'm fairly new to the whole remote access thing! – ianhales Feb 2 '12 at 14:56

You must log in to answer this question.

Browse other questions tagged .