jmroberts70
2[H]4U
- Joined
- Oct 15, 2002
- Messages
- 2,953
I'm working on building a new network inside an office of about 150 clients. The server administrator has setup their server to be the DNS server for the building. It's running Server 2008 right now with plans to upgrade to 2012 shortly. My question is:
1. Is it a good idea to do this? It seems to me that this should be handled by the router in the event that the server goes down. It also seems like it would be a hassle to have to manually configure each machine for this in the network settings.
2. Are there advantages or good reasons to "roll your own" DNS server when there are so many good ones out there to chose from? Is there maybe a performance benefit or a special function of Active Directory that needs this to work?
I have a suspicion that our server admin isn't that gifted with networking principles and may be causing more trouble than its worth.
1. Is it a good idea to do this? It seems to me that this should be handled by the router in the event that the server goes down. It also seems like it would be a hassle to have to manually configure each machine for this in the network settings.
2. Are there advantages or good reasons to "roll your own" DNS server when there are so many good ones out there to chose from? Is there maybe a performance benefit or a special function of Active Directory that needs this to work?
I have a suspicion that our server admin isn't that gifted with networking principles and may be causing more trouble than its worth.