Multiple Websites On Same Server
If so, how can I hide this so if example1.com and example2 are on the same server, no one should know this fact ?
Thanks for any help.
20 Replies
You could try masking this to an extent by using something like cloudflare as a "CDN"/DNS. It's free. When checking the IP address of your site a user would then get cloudflare's IP instead of your server IP.
173.194.75.99
It turns out that 99% of people don't know enough to do this, and the remaining 1% don't really give a damn. It's the way things are. If a customer wants to prevent this sort of thing from being possible, moving their site to their own Linode would probably be the most reliable approach. (You gotta pay for post office boxes, right?)
Well, all the client is looking for is not to have his website associated with one of his own other website (in eyes of public). Both sites resides currently on same linode.
Can I safely keep both of em on same box since as per hoopycat, its something very technical ?
Most people can't spell IP let alone tell you what it really means.
> Well, it's very easy for somebody to confirm if they suspect to begin with. If somebody notices that when they do "ping sitea.com" and "ping siteb.com" they get the same IP address, the gig is up.
very right. But thats when user particularly guess about siteb knowing sitea. Well all we are looking for is that anybody knowing about just the sitea, can't find out, which other websites are hosted along side. Consider it as, if cutekittens.com and pentagon.com are hosted on same server, a frequent user of cutekittens can't find what other list of websites are being hosted with it.
Hopefully, I made it more clear.
@sami1255:
> Well, it's very easy for somebody to confirm if they suspect to begin with. If somebody notices that when they do "ping sitea.com" and "ping siteb.com" they get the same IP address, the gig is up.very right. But thats when user particularly guess about siteb knowing sitea. Well all we are looking for is that anybody knowing about just the sitea, can't find out, which other websites are hosted along side. Consider it as, if cutekittens.com and pentagon.com are hosted on same server, a frequent user of cutekittens can't find what other list of websites are being hosted with it.
Hopefully, I made it more clear.
Whois.domaintools can do what you describe to some extend, e.g.
> Whois.domaintools can do what you describe to some extend, e.g.
Thats exactly what me or my client are fearing. How can I avoid this considering I don't want to get another linode. 20-25$ isn't a big deal but I already have 4 linodes and me being new in linux administration, its already too much of a work to add a new linode.
Will really appreciate some guidance.
@davidhbrown:
In the "Extras" tab of your dashboard, you can buy additional IP addresses for $1/month. Might do the trick.
Except this would not be a reasonable use of IP addresses and the request would be declined. We are running out of addresses you know
@Cromulent:
@davidhbrown:We are running out of addresses you know
:) .
Fair enough. Actually, I thought we already had run out of addresses. Hopefully my ISP will finally enable IPv6 in 2013 and I will finally be able to enable and test it on my Linode soon.
@sami1255:
Thats exactly what me or my client are fearing.
You could also look into using a CDN (Content Delivery Network) like cloudflare.com to obfuscate your website IP addresses.
And there are dozens (if not hundreds) of sites that will tell you which other websites are on your IP - so it's neither an obscure bit of research or rocket science to figure it out.
Either your client can gain some common sense and worry about real scary things instead of "OMG I'm sharing an IP" or he can pony up the money for his own host. Pick one and live with it.
@vonskippy:
You could educate your client and let him know how stupid that fear is.
Rational discussion is out the window once a client sees both business.com and horseboners.com on the same IP.
> You could educate your client and let him know how stupid that fear is. The web has a bazillion shared hosts out there with lots and lots and lots of websites all on one ip.
And there are dozens (if not hundreds) of sites that will tell you which other websites are on your IP - so it's neither an obscure bit of research or rocket science to figure it out.
Either your client can gain some common sense and worry about real scary things instead of "OMG I'm sharing an IP" or he can pony up the money for his own host. Pick one and live with it.
I can just hope all clients gain common sense. I have clients who would love to use comicsans with a heading of timesnewroman, and will argue to get it done.
@jeffml:
@vonskippy:You could educate your client and let him know how stupid that fear is.
Rational discussion is out the window once a client sees both business.com and horseboners.com on the same IP.
Of course, this is why you might have a second Linode to separate "serious business websites" from "funny or questionable websites". No need trying to gain a secondary IP for your server when there are two separate virtual servers, each with their own IP.
@hoopycat:
When I woke up this morning, I had absolutely no idea that the most surprising thing I'd learn is that horseboners.com isn't registered.
I didn't think of that when I saw that post, but when you mentioned that, I just had to do a WHOIS to see it for myself. I'd have to say that surprised me, too. (Horseboner.com, in singular form, is registered, though.)
horseboners.com
Registrar History: 3 registrars with 2 drops.
NS History: 30 changes on 13 unique name servers over 6 years.
IP History: 15 changes on 7 unique IP addresses over 6 years.
Whois History: 29 records have been archived since 2008-05-02
@hoopycat:
When I woke up this morning, I had absolutely no idea that the most surprising thing I'd learn is that horseboners.com isn't registered.
It is… now!
