Sure - with domaintools.com (whois.sc) you can see every site on a given IP. I've have good business reason to separate some sites from other ones. The IPs are on seperate 24/s as well so the competition can't just guess the next IP number.Can you tell us why then? I would be interested in knowing
If nameservers are secured correctly, this isn't possible via zone transfer (that is, if an access list is used, as should be.) Regardless, Shaun's point still stands, as there are multiple providers out there who can tell you how many domains are hosted on a site/particular IP based on access to domain registration data and analysis against nameservers (whois.sc is one I think).As for the competition grabbing a list of sites on your server, moving them around isn't going to help, heck i can pull a list of all domains using your name servers quiet easily.
Right but this feature is already supported and was mentioned aboveActually there is another reason for putting sites on another IP. I do this for many of my sites so I can have all of a reseller's sites running under one IP. This is useful to lower DDOS risk for instance, if baddies DDOS that IP and we have to null-route it only that reseller is affected.
Sure but were talking about the default exim configuration, if we wanted to customize things by hand you could easily do this to make multiple shared ips for accounts owned by root by editing the httpd.conf and manually changing things per site.It is actually also possible to setup exim so that email for a particular domain, or group of domains, goes out on a different IP, although you'd have to do so manually. It can also be used to facilitate transfer to another server.
I will agree with this to a extent because it would eliminate a few steps in the move process but were talking about changes that take minutes, regarless if your shared or primary ip is being DOS'd you still have quiet a bit of a headache moving customers around. Also, the whm/cpanel is accessible on any ip bound to the server.For a related reason you should never make your main shared IP be the same as your server base IP. The reason for this is that if your shared IP is DDOSed and subsequently null routed the server won't be accessible via WHM, and possibly not available at all due to the way some datacenters handle their VLANs. Also cpanel licencing won't be able to call home so your cpanel installation won't work at all. Makes it really hard to fix things/determine the DDOS target!
Well thats true except i wasnt talking about doing zone transfers, you havnt been able to steel domain lists using zone transfers in forever (unless of course somebody enabled this by default in their named.conf), i cant even remember when that feature was enabled by default. The method i was talking about using i wouldnt even have to touch your server.If nameservers are secured correctly, this isn't possible via zone transfer (that is, if an access list is used, as should be.) Regardless, Shaun's point still stands, as there are multiple providers out there who can tell you how many domains are hosted on a site/particular IP based on access to domain registration data and analysis against nameservers (whois.sc is one I think).
That's whay I don't run name serves on my box and use various 3rd party name servers like enom that have a major load of clients.Like Shaun said, it's quite easy to get a list of all domains using your nameservers, or any variations of them.
That would be bad.One good reason is because you wouldnt want a screw up in the apache config to show a adult website on a domain that targets children..
I agree. But I was just wondering because quite a few big hosts (Dreamhost) allow adult on their shared accounts.it's just a better idea to keep the stuff seperate.
|Thread starter||Similar threads||Forum||Replies||Date|
|N||In Progress CPANEL-40703 - Security Questions not "compatible" with Reseller accounts ?||Account Administration||6|
|B||Assigning dedicated IP address to Cpanel account? Some questions||Account Administration||3|
|B||WHM Migration Questions & concerns||Account Administration||6|
|Questions about User's last access||Account Administration||3|
|O||2 questions, regarding IPs.||Account Administration||4|