Originally posted by ccole So basically....if one IP is blacklisted, you want another. I understand that - but why would you need another IP for anonymous FTP? And why would you need another IP for SSL?
I've never really needed either SSL or anon FTP, but I don't see why you would need another IP for either of those.
Also...any other reasons?
ok say you hosted 2 domains on the same ip and you were going to try to give them both anon ftp well they would be sharing the same one since if a person logged in it would be logging into that ip of the anon ftp where as if you have your own dedicated ip for just your site it will be able to have anon ftp
sort of hard to understand but without it you can't have your own anon ftp or ssl cert
for specific scripting reasons... some of the larger resellers of mine... i dedicate an entire IP to them... just so they can have their own separate apache and all with custom headers and apache modules/etc... but that involves recompiling apache independantly for each of the resellers... heh... in addition, the apache runs under their own username (as the reseller) instead of nobody... so the reseller's clients can't mess with data from other resellers via PHP/etc... heh... i m trying to figure out how to do some sorta chroot() easily... heh... by this point... it starts looking a lot like a VPS... heh
The only disadvantage regarding search engines is that you may be on a shared IP that is blocked for spamming that engine, then again you might get a dedicated IP that was also blacklisted due to spamming.. but at least that can be changed easily
nah... i don't have many clients... might as well take care of the few that i do have... hehe...
as far as the search engine stuff... a friend of mine that does search engine promotion (and is very wealthy because of it)... well... he says it doesn't matter anymore... before the spider scripts used to not be HTTP/1.1 compliant, now they are... so... if that helps any...
Originally posted by Dotcomsnz netdude.. sounds like you spoil them