I need supporting documents why DNS is needed on this scenario
Posted on 2006-04-28
Here is my situation:
950 Users about 50 of them are MAC(9.x and 10.x). Two Windows 2003 DCs(one a GC). 6 Windows 2003 member servers, serving as SQL 2000, Exchange 2003 Enterprise Edition and file servers.
We are a private school. We're issued public static IPs. I know for a fact that we have external DNS(I am pretty sure they're unix boxes) because each time we add a new workstation, we have to call these guys above our local IT dept and provide the NIC mac addresss which they in turn provide us a new static IP. All of our XP workstations preferred and alternate DNS settings on TCP/IP are pointing to these external DNS IPs.
What are we missing here? Are we then wasting a lot of bandwidth for name resolutions since all these over 900 devices including servers resolve their names thru these external DNS? Would it not be better if say one DC or another be configured as local DNS and then point the forwarders tab to these external DNS. All the workstations then should be pointing to this local DNS and not to these external DNS.
I've been recommending a local DNS be configured in our environment but I keep getting a NO answer.
I appreciate any backing informations as to why I need a local DNS or why I don't need one.