English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

2006-08-20 01:38:59 · 3 answers · asked by saunrayz 1 in Computers & Internet Computer Networking

3 answers

There should be one DNS server in the Network - ideally not on the PDC - so BDC would be fine - or even a non Domain Controller.

2006-08-20 01:42:44 · answer #1 · answered by MM 3 · 0 0

Assuming that you're talking about a Windows NT network (not Active Directory) DNS isn't particularly necessary. Windows NT networks are not dependant upon DNS and the DNS service bundled with Windows NT Server does not dynamically update so you have to manually add A records for every host on the network.

It might have some value as a caching DNS server if you have a lot of hosts accessing the internet as it will minimize external DNS queries somewhat. It also may have some value as you prepare for an upgrade to Active Directory if you will have a DNS server at the same IP address after the upgrade.

Unless you have a very large network or are using very old hardware there's no reason why you can't install DNS on a Domain Controller, either the PDC or a BDC.

I've installed hundreds of Windows NT networks and only once used DNS on an NT network and that was on a huge corporate network with nearly 100 NT domains at over 200 sites.

2006-08-20 02:34:33 · answer #2 · answered by Bostonian In MO 7 · 0 0

DNS is a service. Yes, you can run that service on your PDC and or your BDC.

Unless you are short servers it is not a good idea. Domain controllers should do just that, control access / validate access to the domain, you don't want them doing everything under the sun unless you don't have the resources.

2006-08-20 01:45:46 · answer #3 · answered by TARFU 3 · 0 0

fedest.com, questions and answers