Information Technology Reference
In-Depth Information
Secondary servers are often placed within the parts of an organization that have high-
speed network access. This prevents DNS queries from having to run across slow wide
area network (WAN) connections. For example, if there are two remote offices within
the
stellacon.com
organization, you may want to place a secondary DNS server in each
remote office. This way, when clients require name resolution, they will contact the nearest
server for this IP address information, thus preventing unnecessary WAN traffic.
Having too many secondary zone servers can actually cause an increase in
network traffic because of replication (especially if DNS changes are fairly
frequent). Therefore, you should always weigh the benefits and drawbacks
and properly plan for secondary zone servers.
Understanding Active Directory Integrated DNS
Windows Server 2000 introduced
Active Directory Integrated DNS
to the world. This zone
type was unique and was a separate choice during setup. In Windows Server 2003, this
zone type became an add-on to a primary zone. In Windows Server 2012 R2, it works the
same way. After choosing to set up a primary zone, you check the box labeled Store The
Zone In Active Directory (see Figure 2.6).
figure 2.6
Setting up an Active Directory Integrated zone
Disadvantages of Active Directory Integrated DNS
The main disadvantage of Active Directory Integrated DNS is that it has to reside on a
domain controller because the DNS database is stored in Active Directory. As a result, you
cannot load this zone type on a member server, and small organizations might not have the
resources to set up a dedicated domain controller.
Search WWH ::
Custom Search