|
On-Rails:
I fully understand the limits of a web server (and the number of ips you can assign to one).
Technically you do not even need a unique ip for a domain.
IE
abc.com can resolve to 1.2.3.4
xyz.com can resolve to 1.2.3.4
lmnop.abc.com can resolve to 1.2.3.4
all three websites hosted on those unique three domains (subdomains) would be hosted on the same server.
as far as putting a subdomain on a unique ip, the only reason i would do that is if the subdomain was not going to be hosted on the same server as the domain.
IE
abc.com resolves to 1.2.3.4
lmnop.abc.com resolves to 1.2.3.5
and 1.2.3.4 and 1.2.3.5 were seperate machines.
if 1.2.3.4 and 1.2.3.5 were assigned to the same machine there is no reason to assign them seperate ips.
if you are talking about just a free site, i wouldn't worry about how many you put on a single domain or ip as long as the domains make sense.
i wouldnt have a subdomain called
twinks.NoGayContent.com
although the search engines would probably like it (having the words twink and gay in your domain name), it does not make logical sense.
either way
freesite1.domain.com
freesite2.domain.com
.
.
freesiteN.domain.com
or
domain.com/freesite1/
domain.com/freesite2/
.
.
.
domain.com/freesiteN/
should be perfectly accecptable to link list operators and search engines alike. it is more just personal preference.
i would recommend domain.com/freesite1/ for the sake of network simplicity.
|