Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have to run differents services in a lab enviroment where I'll have 6 computers working as servers, what services can I put together, and what cannot be, in order to prevent security risks, and considering that if one service goes down, affects less possible the function of the server farm, the services are:

  • MySql
  • Http for intranet
  • Https
  • DHCP
  • IPP
  • SMTP
  • LDAP
  • VPN
  • SSH
  • NTP
  • DNS
  • NFS

I'll use linux

share|improve this question

closed as not a real question by Chopper3, freiheit, HopelessN00b, Zoredache, Greg Askew Oct 1 '12 at 22:13

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

every of listed service can be done on linu,x no problem – alexus Oct 1 '12 at 21:53
But the question is: with 6 computers, what services can I put together in order to prevent security risks and when one of those services goes down, affect less the farm server... – poz2k4444 Oct 1 '12 at 21:56
if you configure them properly there is no security risk for another service – alexus Oct 1 '12 at 21:58
Well, I think my question is vague, but I mean, for example if MySQL goes down, I want to have the DNS and DHCP working, so, what services should I put together to affect less the performance and aviability on the farm server – poz2k4444 Oct 1 '12 at 22:01
This question is along the lines of How long is a piece of string? or What killed the cat?. At the very least you're conflating security and redundancy (which is Bad). All we can really offer you is the general rule: Separate your services logically, and have two of everything for redundancy... – voretaq7 Oct 1 '12 at 22:04
up vote 0 down vote accepted

in order to prevent security risks

Generally most mitigation of security risks is done by having a firewall in front of everything. Anything after the firewall, well, that entirely depends on the security of the actual application you use. You can make things as separate as you like, but if your app has a remote shell vulnerability then all bets are off.

Apart from that, just put things into whatever availability groups you want. If your MySQl is only used by the web server, then you may as well put them together.

If you want DHCP work with your VPN, then put them on the same server.

There are no rules here, just group them however best suits your requirements; we can't really answer that for you.

share|improve this answer
Well, I think my question is vague, but I mean, for example if MySQL goes down, I want to have the DNS and DHCP working, but I don't really know how could affect if the DNS and DHCP goes down together, if it's better to put them together or not... – poz2k4444 Oct 1 '12 at 22:05

Not the answer you're looking for? Browse other questions tagged or ask your own question.