[RESOLVED] Noob question regarding domain names and hosting

[3Nex]

I recently purchased a Reseller hosting account and now i have to make my own account for the corresponding domain names that i buy. So if i buy example.com, my hoster "gets" the domain name and does whatever they need to do with it, while i create a new account, enter that domain name and create an FTP account for it. And everything works fine.

Now, let's say you and me have our Reseller accounts with the same hoster and on the same IP. You buy the domain example2.com and create the corresponding account for it, but in the meantime, i also make an account that corresponds to the domain name example2.com. If i understand correctly, all that the hoster did after buying the domain name was point it to their (our) server's IP address. So now that both you and me have our accounts for the same domain (example2.com) and with the same IP address (cause we're on the same server), how will the server know which page to load, yours or mine?

[3Nex]

245 views, no replies :eek: Maybe it aint such a noob question after all...

Or did you guys not understand what i meant?

[aj_nsc]

Good question, they probably won't let you do it. If somebody registers a hosting account with example2.com on their server, if anybody else tries to register a hosting account with the externally registered domain name example2.com, they'll probably tell you that you can't do it because that domain is already in their vhosts.conf file.

This is all a guess because, really, how often would this happen? If you really want an answer, perhaps you should ask your host's tech support.

You are correct though, there is no way, as far as I know, for a server to distinguish which hosting account to serve up, other than perhaps the first VirtualHost listing for example2.com in the servers vhosts.conf file (providing you are running Apache)

[3Nex]

This is all a guess because, really, how often would this happen? If you really want an answer, perhaps you should ask your host's tech support.


Well for years now people have known there was a "potential hole" in the TLS encryption but they thought it wouldn't be such a big deal, and then it got hacked.

It's not ever gonna be an accident, like you made it sound. If anything, people would do it on purpose. Most of the time it's not such a hard thing to find out where a site is hosted...

Well okay, I'll ask my web hosting company I guess.

[aj_nsc]

Yes, people would do it on purpose, but I highly suspect that if there's an entry in your hosts vhosts.conf file with example2.com, then they won't allow another one which plugs this hole completely.

But, because large hosts generally have hundreds of shared hosting environments, they won't have to block you from attempting to register another example2.com because, if they do happen to find a record in the vhosts.conf file on one of their servers, they'll just move you to a server where that domain doesn't exist in that servers vhosts file.