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

I'm setting up a small network that contains all 2008 servers. No domain controllers, and no DNS (as of yet). Most of the servers will be IIS servers and part of a web farm/pool. Now I have configured the host names to be me more then 15 characters long. eg. NAME-LOCATION-PROD-WEB1. Now I know that NETbios is soon to be a thing of the past and none of our applications require netbios name resolution. Should I set up a DNS server with a primary/secondary zone to contain the hostnames? Should I be concerned about the Duplicate name warning if no Netbios resolution will be taking place? Should I take a look at global name zones? What are your thoughts?

share|improve this question
up vote 4 down vote accepted

If you don't require it and it isn't causing any problems, then there's nothing to worry about. If these boxes don't need to communicate via hostname you don't really need DNS, though it should help with management in general.

share|improve this answer
I would actualy like to connect with host names DNS servers are probably going to be a must. Beats adding entries manually to each host file on each server. What do you think? – RomeNYRR Jan 31 '12 at 23:00
Absolutely use DNS. – MDMarra Jan 31 '12 at 23:25
Absolutely use public DNS – Mathias R. Jessen Feb 1 '12 at 7:50
@MathiasR.Jessen what good will public DNS do? If he needs these machines to resolve each others names, local DNS seems like a more reasonable bet. – MDMarra Feb 1 '12 at 12:11
@MDMarra hadn't thought that comment through, my apologies – Mathias R. Jessen Feb 1 '12 at 16:24

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.