No, DNS is a central part of an AD.
You can do that but there is very cheap solution to it (why burn company money, if the company did not get bailout from Fed). Install DNS as AD interated DNS and you do not need fail over separate server. Shahbaz
The XP cannot host AD ie you cannot install full AD on it. but yes we can make it dns server to resolve the dns queries in the network but it is advisable to use server platform to make a dns server. There is utility which is there ADAM with help of which the XP can have features of system having AD but it has limitations and less options.
a. All AD DS-integrated DNS zone records are stored in the Active Directory database. b. AD DS-integrated DNS uses the multimaster replication process of AD.
a. All AD DS-integrated DNS zone records are stored in the Active Directory database. b. AD DS-integrated DNS uses the multimaster replication process of AD.
(A máquina pode não estar configurada com cliente DNS dela própria O serviço de DNS pode não estar a correr) The machine cannot be configured with DNS client her own The DNS service cannot be run
BIND is actually the software that implements DNS. BIND is the software and DNS is the language it speaks-this means BIND is an application that provides DNS services like windows AD DNS does.
true
An AD-integrated zone is a DNS zone that is integrated with Active Directory. Typically this occurs on a Domain Controller (dc), which requires DNS to answer queries from Active Directory (LDAP).
DNS is always configured first for ad to work properly
You dont *need* DHCP in AD. Although most people just use it anyway. However you do need DNS in an AD.
An active directory (AD) is where you manage alot of your network from. Users, printers, gpo's, computers, security etc... Before you install your ad you will have install a DNS server. Otherwise your AD wont work. But dont worry about this, DNS is pretty straight forward. Learn a bit of theory and you'll have it up and going in no time. Next your AD. Again, just learn the basics about networking and domains and this wont spare you a second thought. If you start looking up ad's you are going to be hit with book after book telling you all about forests and trees and child domains and all this stuff that doesnt apply to small networks. Just learn network basics and then install the AD and after an hour or two of playing around with it you will have a good grasp on it. The hardest part I found about AD's was trying to memorise the difference between all the different accounts and groups (domain user, global user, power user etc) and who had what permissions.
Are you sure its the AD that's freezing up and not the server...?? I'd say more than likely an important file has become corrupt. Try exporting everything in the AD then delete, re-install and import the files. If the problem continues you may want to have a look at your DNS, the two of these work together. Though Ive never seen this a DNS causing this, but I guess its possible. Also sometimes a badly designed AD can put your memory usuage way up. Could be putting pressure on your server.