The Windows 2000 DNS service can coexist with or migrate other DNS services, including the popular Berkeley Internet Name Domain (BIND) DNS service. The wizard takes the pain out of DNS administration. Ensure that Standard Primary is selected and click Next. Ensure that Forward Lookup Zone is selected and click Next. At the New Zone page, type the name of your zone (for example, fordummies.com) and click Next. Select Create a New File With This File Name and click Next.
One great place to find BIND information is the Internet Software Consortium Web site. Double-click Add/Remove Programs and then click Add/Remove Windows Components. In Components, select Networking Services and then click Details. In Subcomponents of Networking Services, select the Domain Name System (DNS) check box, click OK, and then click Next. In Copy Files From, type the full path to the Windows 2000 distribution files and then click OK. Windows 2000 launches the DNS Microsoft Management Console, from which you can perform your DNS administration.
I've been unsuccessful at finding a guide on how to integrate just ISC DHCP into an AD DNS environment.
The configuration file is below, but what I've noted when using ISC DHCP is that non-domain joined clients will not have an A record registered for them in forward/reverse lookup zones.
Many bug reports have been submitted regarding installation bases that relied on the wizard.
Also keep in mind that the Active Directory Installation wizard does not install a reverse lookup zone. Right-click the Forward Lookup Zone folder and choose New Zone. Click Next to continue when the New Zone wizard appears.
I will try to simply show you, how to do that very quickly using the least administrative effort because using DNS Management console is not very convenient and fast method (you need to create each records separately by hand).This time we will focus on the same activity but in reverse lookup zone.In my opinion this kind of task is much more frequently used that the previous on. Because in regular basis when you create host (A) record in forward lookup zone you don’t care about pointer (PTR) record in reverse lookup zone.you didn't use a proxy user to update DNS on behalf of DHCP).This should go away over time as DNS records expire, domain-joined Windows clients are automatically updating their own records.