Jump to content
Posted 13 November 2012 - 18:19
Posted 13 November 2012 - 18:47
Posted 13 November 2012 - 19:04
I think your over stating your intermediate understanding a bit.
An IP really has nothing to do with a domain name?
You mention a website, is this hosted on a VPS? Is it a shared host, dedicated host?
I find it unlikely your website holds the dns registry? You mean you point your domains nameservers to a webhosts dns? Or is your server actually the authoritative nameserver for your domain?
if I register domainX.com, this is done at registrar, be it godaddy, namecheap or any of the other hundreds out there. Or even your webhosting company could do it for you.
to resolve something.domainx.com - domainx.com needs nameservers, they might be housed by the registrar or your webhost. Or sure you could run your own that you point domainx.com too.
now something.domainx.com is just a "A" record that points to an IP, be it 188.8.131.52, etc.
If you want to point remote.domainx.com to your public IP of your SBS server - sure that would be done at where your domainx.com nameservers are managed. Now the question is, does this public IP ofyour sbs server change? How is the sbs server connected to the internet?
To hopefully answer your question - no you don't need another domain if you already have one. You can point "A" records to whaterver IP you want - they could be all over the planet does not matter. Where you run into issues if if that IP changes often, then you need a way to make sure remote.domainx.com is updated to point to 184.108.40.206, or 220.127.116.11 if it changes, etc.
So for starters - how is sbs server connected to the internet? Does this public IP change? And what is your domain name. And I can look up the nameservers for it and the registrar. Feel free to PM me the domain name if you don't want to make it public.
Posted 13 November 2012 - 19:18
Posted 13 November 2012 - 19:28