Thanks
I've always had issues with web hosts which is why I had chosen to self-host lately but my PC simply isn't meant to be a web server. Plus it puts the other computers on my LAN at risk for attack as well.
I just got through with a 6 hour struggle in DNS Management hell.
I have a machine on my network that I like to connect to through ssh to upload/download source code.
My domain name no longer points to the ip address of my router so I can't get to the ssh server through my domain name.
I contacted my host provider wondering if it would be possible to alter the DNS records so all ssh traffic ended up going to my router rather than to their web servers. The answer was "I'm not sure." then 20 minutes later "No you can't." then I was hung up on.
I had an idea after that to create a new A record for a subdomain of my site which, with my infinite wit, named ssh, points to my routers ip address.
So siliconemilk.com and
www.siliconemilk.com points to my host ip address.
ssh.siliconemilk.com points to my home ip address.
Now I can access my ssh server as usual through a slight modification in address. I can type ssh://ssh.siliconemilk.com and get at the machine I want to get at
------------------------------------------------------------------
I'm disappointed because a good friend told me this host was great and I should move my site to their servers. I've had a 5 minute downtime in less than 24 hours (guaranteed 99.9% uptime) and dealt with rude, incompetent tech support.
I'm not naming them because they don't deserve any additional google brownie points from me. But I'm sure you can guess what it is when I say the first part of the name is host and the second part is the kind of creature Godzilla is. (You need to watch more Godzilla films if you're guessing gator...)