2 Questions,

1. Should I block pinging on my server. It had been really common in the past, but now it appears that most places no longer block pings. Any recommendations?

2. IP's. Is this feasable:

IP#1 - Name Server #1, Main Hosting Site, Shared Sites
IP#2 - Name Server #2

If I did this, and purchased an SSL certificate for my hosting site, could I then use that same ssl as a 'shared ssl' certificate? or would it be better to perhaps moved the shared sites to another ip (perhaps #2, or one of their own) ? I've never done the shared ssl - I assume if I shared it, people could then get to it by using 'https://hostname/~sharedsite/... or https://ip/~sharedsite/... Correct? Any issues with this set up?

Thanks

Dont block ping, alot of lesser informed individuals still use pinging to determine whether or not something is up (which isnt what it was meant for.) So you're better off leaving it enabled.

We have server wide SSL certs on all of our virtual webhosting boxen, they're IIS boxes so all you do is apply the SSL certificate to the 'default website' and then make the path of the default website the top level root of where your users' sites are stored.

So the url for the secure pages looks like this.

secure.whatever.com/sitename/filename.ext

-Drew

Thanks... Need to look up the echo port so I can unblock the ping.

As for the sharedssl. I suspect I would install a ssl certifictate for mysite.com (which uses the same IP as my clients sites) and then if they wanted to use the ssl they would use https://mysite.com/theirsite/

correct?