Integrating Dns Structures

By Author: Mike Jones
Total Articles: 256

Most organizations have existing DNS structures they must maintain. This is especially true for any organization that already has a Microsoft exam 70-297 Active Directory installation. Further, companies that manage medium to large TCP/IP networks usually have existing DNS servers. In these organizations, you'll probably need to integrate the Windows 2003 Server Active Directory domain and any DNS configuration into the existing environment.
Organizations that already have Windows 2000 Active Directory implementations should be the easiest to integrate because the DNS structure will likely remain the same when the domain is upgraded to the Windows 2003 Server Active Directory domain. Organizations that do not have an existing Active Directory implementa?tion are likely to have a lot more planning to do. For example, the most prevalent non-Windows DNS implementation is the Berkeley Internet Name Domain (BIND), which is maintained by the Internet Software Consortium (ISC). If an organization chooses to keep their BIND DNS servers, there are three main methods for integrating an existing BIND and Active Directory:
Configure BIND DNS to handle all DNS records for Active Directory. In this case, you'd ensure that the BIND DNS server version could support SRV
records (BIND 4.9.7 and later versions work properly for this purpose). Also,it is highly desirable to use a BIND server that supports Dynamic DNS (BIND
versions 8.2.2 and later will do so).
Configure BIND DNS to delegate an 70-297 practice test specific subdomain.For example, if the company uses contoso.com, the Active Directory name
space might be ad.contoso.com. This is a very popular choice for many companies.

For more information on this subject, search the Microsoft Web site for "DNS Server Top Support Articles" or "Integrating Active Directory with an Existing DNS Infrastructure."
If you are upgrading from Microsoft Windows NT, it is likely that you will need to consolidate domains. The principles for defining multiple domains in Windows NT no longer apply in Windows Server 2003- These principles are the following:
Security Accounts Manager (SAM) size limitations In Windows NT, the SAM database had a limitation of about 40,000 objects per domain. In Windows Server
2003, each domain can contain more than one million objects, so it is no longer necessary to define a new domain just to handle more objects.
In Windows NT, only one computer in a domain, the PDC, could accept updates to the domain database. In Windows Server 2003, all domain controllers accept updates, eliminating the need to define new domains just to provide fault tolerance.
In Windows NT, domains were the smallest units of administrative delegation. In Windows Server 2003, free Microsoft questions allow you to partition domains to delegate administration, eliminating the need to define domains just for delegation.