I lately moved my web site to a hosting that is shared solution at asmallorange.com, however i needed to set my domain to make use of their provided nameservers to ensure that the website to correctly resolve. I had been going to keep charge of the domain's DNS however i may find not a way to create my top level domain resolve towards the shared location that was within the format of
And So I know I am missing something here, my real question is this:
What within their nameservers/DNS entry causes it to be feasible for server.sharedhost.com/~username to function as a top level domain? (ie. http://topleveldomain.com)
Nothing. DNS simply maps topleveldomain.com to server.sharedhost.com. It is the webserver which compares the
Host: topleveldomain.com header and knows that's equal to server.sharedhost.com/~username.
Nothing. They're getting your domain title resolve towards the same IP that server.asmallorange.com resolves to, however they're making their web server conscious of the domain title topleveldomain.com, and telling the webserver that it's the just like server.asmallorange.com/~username.
Virtual hosts aren't a DNS trick, they are an HTTP trick - the hostname asked for is distributed through the browser inside a Host: area of each and every request.
apache includes a "mod_user" which you'll enable inside your apache conf file. By using this and virtual hosts is when that's accomplished.
Virtual Hosts in Apache are how this is accomplished.
However simply because you place the DNS as much as go "mydomain.com resolves to at least one.2.3.4", that is their Ip, does not imply that you are quitting charge of your domain title.