I'm looking to switch hosts and was wondering what advantage there'd be to a dedicated IP vs virtual?

The machine you're on is still shared, so it's not a resource issue. So I'm scratching my head. :)

Thanks!

anonymous ftp and ssl certificates require a dedicated ip. also, when you register your domain, having a dedicated ip might be easier for you to upload and view your pages while dns propagates.

Well a static ip address does this:

Allows you to test your website before it goes public.

Alot of e-commerece type application require at static ip and so does an SSL key.

Cheers,
Seagate

Teck,

How is it that ssl certificates rely on your IP address? According to Equifax and Thawte's web sites, the SSL doesn't rely on IP. It relies on domain name. As long as your IP resolves back to the domain listed in the cert, everything's good.

Ron

Actaully there is no benefit anymore to a dedicated IP. You can still give each user SSL access and access to view their site before the NIC record is updated without a dedicated IP.

Originally posted by compsci
Teck,

How is it that ssl certificates rely on your IP address? According to Equifax and Thawte's web sites, the SSL doesn't rely on IP. It relies on domain name. As long as your IP resolves back to the domain listed in the cert, everything's good.

From http://marc.theaimsgroup.com/?l=apache-modssl&m=98576871506980&w=2 :

--
In a nutshell: You can't do Name-Based Virtual Hosting with SSL.

Check out the following from earlier this week:

http://www.modssl.org/docs/2.8/ssl_faq.html#ToC47

Q: Why is it not possible to use Name-Based Virtual Hosting to identify
different SSL virtual hosts?

A: Name-Based Virtual Hosting is a very popular method of identifying
different virtual = hosts. It allows you to use the same IP address and
the same port number for many different sites. When people move on to
SSL, it seems natural to assume that the same method can be used to have
lots of different SSL virtual hosts on the same server.

It comes as rather a shock to learn that it is impossible.

The reason is that the SSL protocol is a separate layer which
encapsulates the HTTP protocol. So the problem is that the SSL session
is a separate transaction that takes place before the HTTP session even
starts. Therefore all the server receives is an SSL request on IP
address X and port Y (usually 443). Since the SSL request does not
contain any Host: field, the server has no way to decide which SSL
virtual host to use. Usually, it will just use the first one it finds
that matches the port and IP address.

Ah, you'd think I would have read that when looking at the mod_ssl site, eh?

I do have a server with only one IP that has several virtual hosts on it, one of which has an SSL cert...so it doesn't stop working completely. But I guess you're limited to one.
I stand corrected. :)

Ron

thanks rehan. i didnt feel like finding out the info. :)

The only real advantage for most people has already been mentioned, being able to access and test your new site before the domain transfer has been effected. Other than that, if you have to ask, you donlt need one.

There are previous discussions on this subject, though the benefits have already been summarized in this one.

Originally posted by Duster
The only real advantage for most people has already been mentioned, being able to access and test your new site before the domain transfer has been effected. Other than that, if you have to ask, you donlt need one.

You don't need a separate IP address to do that. Just add a line in your HOSTS file to resolve the hostname to the appropriate IP address, and that will also work.

You folks might be interested in this reply I had to a similar question on Sitepoint
http://sitepointforums.com/showthread.php?s=&postid=140253#post140253

For those that don't feel like reading it suggests that if you happen to be on a server and someone on that server spams search engines etc then the IP they are on and consequently you are on could be black listed.

There are a lot of fallacies and beliefs stated as facts about IP addresses, search engines, etc. That's just another one. Notice that the entire statement of that response is an assumption and guesswork.

Originally posted by Duster
There are a lot of fallacies and beliefs stated as facts about IP addresses, search engines, etc. That's just another one. Notice that the entire statement of that response is an assumption and guesswork.
Could you take the time to quote what the assumption and guesswork part of Mr Bowmans message was. I think I will consider his thoughts as he has been running a website devoted to "search engine optimization and web promotion" for some time.

To refresh this is what he said

quote by J.K. Bowman editor http://spider-food.net/

It's true that the engines will register your domain. However, when possible it is always preferred to have your own unique IP address.

Now, usually this presents no problem. It's common at many hosting companies to put as many as 200 web sites on one IP address - as IP addresses are not free. However, what do you do when you are site 34 and site 176 on the same IP address spams the engines or keeps resubmitting the same pages over and over and over again?

The answer is that you just sit there with your fingers crossed. That's because some engines (I believe AltaVista dn Inktomi are at least two) do register IP addresses, and this kind of spamming has the potential to impact all the other web sites sharing that same IP address.

Anyway, again it's usually not a problem. But if your web site is truly important to ya go ahead and spring for the extra $5 bucks a month to get your own IP address. You can even host multiple sites under your own IP address. But at least doing it that way you know you are in complete control.

Hope that helps.

P.S. Duster do your hosting plans not offer dedicated IP?

[Edited by gthorley on 04-07-2001 at 12:05 AM]

Originally posted by gthorley
[QUOTE]Could you take the time to quote what the assumption and guesswork part of Mr Bowmans message was.
That's because some engines (I believe AltaVista dn Inktomi are at least two) do register IP addresses, and this kind of spamming has the potential to impact all the other web sites sharing that same IP address.

Anyway, again it's usually not a problem.

You might read other comments on that same subject. There is nothing that can happen to you with a shared IP that can't happen with a dedicated one, or being with the wrong host.