Folks, could use some pointers. I seem to remember from experience some years ago that if you were hosting multiple domains for web hosting in a shared environment that they needed to have individual IP numbers assigned specifically to the domain, all sharing the interface, so things like AOL browser, etc. would all work properly. Am I out of date on this, or is it still common practice to assign a single ip number to a single web hosted domain i.e. hme0/1.2.3.1/www.test1.com hme0/1.2.3.2/www.test2.com ...and so on and so forth? Specifics would be helpful i.e. certain browsers, applications, etc. Thanks. Regards, -- Martin Hannigan hannigan@fugawi.net
On Thu, Jul 11, 2002 at 04:22:53PM -0400, hannigan@fugawi.net said:
Folks, could use some pointers.
I seem to remember from experience some years ago that if you were hosting multiple domains for web hosting in a shared environment that they needed to have individual IP numbers assigned specifically to the domain, all sharing the interface, so things like AOL browser, etc. would all work properly.
I haven't heard of any problems with virtual hosting and client-side browsers. The only caveat I'm aware of is that SSL-enabled virtual hosts (i.e. https://foo.bar.bz) must have a unique IP per host, due to the nature of SSL and certificates.
Am I out of date on this, or is it still common practice to assign a single ip number to a single web hosted domain i.e.
hme0/1.2.3.1/www.test1.com hme0/1.2.3.2/www.test2.com
...and so on and so forth?
Only for SSL vhosts. Otherwise, there are no problems (well, very few anyway) that I am aware of in using a single IP to host as many vhosts as physical resources will allow. I'm quite certain somebody will correct me if I've missed something. :) -- -= Scott Francis || darkuncle (at) darkuncle (dot) net =- GPG key CB33CCA7 has been revoked; I am now 5537F527 illum oportet crescere me autem minui
http://httpd.apache.org/docs-2.0/vhosts/name-based.html Summary: Name based if you can to save on addressing and if you don't need SSL. IP Based for SSL and if customer insists for some strange reason. It got really popular when ARIN said no more IP's for web addressing, then they backed off of that idea. I've set it up on IIS and Apache before. Pretty simple on both. Gerald On Thu, 11 Jul 2002, Martin Hannigan wrote:
Folks, could use some pointers.
I seem to remember from experience some years ago that if you were hosting multiple domains for web hosting in a shared environment that they needed to have individual IP numbers assigned specifically to the domain, all sharing the interface, so things like AOL browser, etc. would all work properly.
Am I out of date on this, or is it still common practice to assign a single ip number to a single web hosted domain i.e.
hme0/1.2.3.1/www.test1.com hme0/1.2.3.2/www.test2.com
...and so on and so forth?
Specifics would be helpful i.e. certain browsers, applications, etc.
Thanks.
Regards,
-- Martin Hannigan hannigan@fugawi.net
participants (4)
-
Gerald -
Mark Kent -
Martin Hannigan -
Scott Francis