Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

We are setting up a small Datacenter, about 300 amps power and max 50 racks,

I have studied networking mostly Microsoft and Windows based systems , but I do not understand the IP addressing, DNS management and configuration works in a Datacenter, and unfortunately I have to setup everything by myself but,we will have some staff to do some job.

My questions

Datacenter IP Addressing

Suppose we have got a block of 200 IP addresses from our ISP,

  1. How can I manage these block of IP addresses, is there any software out there to simplify this I heard that using DHCP server in a datacenter is not recommended, otherwise what would you say about MS DHCL serverconsidering we need to have backup server(s) in case of failure

  2. How can I assign a block of IPs to a specific rack, I know with different software and management its different but Im asking how it is done normally

  3. IP addresses are exposed to the whole network, what if a customer tries to use an IP address and is not assigned to their server or rack , how can I prevent this or how can I track the IP usage

DNS Management

Im goin to setup at least two servers for our DNS servers, I know nothing about Datacenter DNS system, but I have configured DNS server in normal networks and also for webservers, Now I wanna know.

  1. What exactly needs to be done for a DNS in a datacenter that is not done for normal networks.

  2. How can I configure PTR records

  3. why cant I configure PTR records on my webserver side DNS server and it should be done on datacenter DNS server , I mean what is the difference in DC DNS servers that allow us to to so , I know the question is very silly and simple but Im confused

Is there any software outthere to allow doing the whole thing, I mean automatically add records to the DNS and also managin IP addresses !?

Thanks in advance

share|improve this question
300A over 50 racks is 6A a rack. That's awfully low. More to the point, a Datacenter is just a physical place to put hardware. It has little or nothing to do with how things are connected and networked. Any meaningful answer to your questions will need more info about how these systems are to be used (private network, Internet connected, etc.), and how they are to be connected together (swtiches, routers, etc). – Jeff Leyser Jan 2 '11 at 4:43
I would say that 20A per rack is a little low. If you are using a bunch of 1U servers you'll probably need 3 20A power circuits per rack. If you have blade servers or high end storage (EMC, IBM XIV, etc.) then you'll be looking at 60A of 208v power per rack (if not more). – mrdenny Jan 2 '11 at 11:28
Wait, you think adding more power to racks is easy? It most certainly is not easy. You need to understand, once those servers go in to the rack it's going to be nearly impossible to change anything. – blueben Jan 3 '11 at 11:10
I think the point people are getting at here is that you sound like you are in way over your head. – blueben Jan 3 '11 at 11:24
You're putting a lot of focus on things that are less important, and less focus on things that are absolutely critical. The fact that you aren't worried about your power situation is, frankly, frightening. 6 amps per rack means you should only maintain 4 amps average usage to leave room for peak spikes. 4 amps isn't enough to power a decent quarter rack, let alone a whole one. – blueben Jan 3 '11 at 11:31

It's not the answer you're looking for per-se but I'd reccomened getting a contracter in or hiring someone who knows what they are doing rather than asking on a FaQ site.

Also, are you sure you can make it? What's to separate you from the hundreds and thousands of hosting companies?

share|improve this answer
+1. This really sounds like someone without a clue being taesked with a complicated task - and thus getting totally lost. Get someone in who knows what to do. – TomTom Jan 3 '11 at 12:15
Okay let me explain it :) my main job is Web Applications programmer, but I studied Network and Systems Engineering, I know a lot about Systemes engineering specially about Microsoft systems , Im very good at managing and securing web servers, but the problem is that at a DC everything is about routers and switches which I have no experience working with, yes I think we can make it , coz our prices will be much less than the other DCs and as I said its a small dc for the start. we have got two pre orders so far, by end of this month everything should be done. – user65248 Jan 3 '11 at 12:55
Besides , we have invested a lot so far, the internet link itself was a lot , Dell agreed to give us leasing services, we've got Microsoft volume licensing services, the place , facilities .... – user65248 Jan 3 '11 at 13:01
You bought a car and have no driver's license. This is going to be sweet. – mfinni Jan 3 '11 at 13:42

The answers to your questions are very very complex depending on how and what you want to do, so I second the previous comments about getting professional help to sort all of this out. You don't want to do this wrong, because if you do you risk crashing the entire company, trust of your customers, allow your customers data to be stolen or worse scenarios.

Invest the money in a consultant or two to help you out, you will earn that money back tenfolds by avoiding the mistakes you will unavoidably do without them. I don't mean any disrespect but this is the harsh truth!

To comment specifically on a few points; yes there are quite a few softwares out there to help out with adress management and lots of other datacenter tasks.

One IP address management is, for example, IPplan found at:

Regarding IP segmentation you have to build a structure where you can limit customers from stealing IP addresses randomly, exactly how you do this depends on the type of network design you will end up chosing, what brand of hardware and software you end up using, etc. but basically you will have to create a network structure that blocks people from using IP addresses they're not supposed to use.

Regarding DNS; there is no such thing as "webserver side DNS" or "datacenter DNS". You usually only want to separate the nameservers into authorative nameservers and recursive/caching nameserver.

The authorative nameservers is where you place you and/or customers domains that you'll be responsible for (or delegate management through, depending on how you chose to build the DNS solution), and the recursive/caching ones are the ones you configure on your servers for adress lookups. Its usually good practice to separate these two roles.

Not exactly an answer in itself, but atleast some pointers.

Good luck!

share|improve this answer
Ouch, I didn't see that this was a thread from a year ago, thought it was january 2012. :P – Mattias Ahnberg Jan 22 '12 at 20:09
Don't let that put you off.. There's badges to be gained from answering old questions! – Tom O'Connor Jan 22 '12 at 21:55

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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