Acronym's And Definitions Chapter 6 - Configuring Dns Zones And Replication

Front 1

Active- Directory Integrated Zone

Back 1

A Master writable copy of zone data stored and replicated form within AD DS.

(Poulton, 2012 p.249)

When you host your primary zones on a domain controller, the option to integrate these zones with AD DS becomes available. These zones are stored as directory objects in the AD-DS database file and replicated to other domain controllers as a component of AD DS replication. Using Active-Directory-Integrated zone provides the following benefits.
- Zone Security is enhanced
- Zone data are automatically replicated and synchronized to all domain controllers
- Administration of zone file replication across your network is facilitated
- Faster and more efficient replication is possible

(Poulton, 2012 p.250)

Front 2

Application directory partition

Back 2

First introduced in Windows Server 2003, an application directory partition simply called an application partition is a data structure in AD DS that contains application-specific data that needs to be replicated only to specific domain controllers in one or more domains of the Active Directory Forest. DNS stores its Active Directory-integrated zone data in the following application directory partition, which are automatically created when you install DNS during creation of your domain.
- ForestDnszones
- DomainDnsZones

(Poulton, 2012 p.274)

Front 3

caching-only server

Back 3

DNS servers don't rely solely on he information in their zone files. All DNS name servers cache queries that they have resolved that they have resolved. By contrast, caching only servers are DNS name servers whose-only job is to perform queries, caching the answers, and return the results. A caching- only server can only provide the information based on the results of the queries that it has already performed, it does not provide any type of zone file. It is not authoritative foe any zone.

(Poulton, 2012 p.255)

Front 4

DNS Notify

Back 4

DNS notify is a process in which the master DNS server for a zone notifies secondary servers of changes to the zone, so that the secondary servers can check to determine whether they need to initiate a zone transfer. You can configure the DNS server for the DNS notify by specifying the list of IP addresses to which notifications are to be sent. Configuring the notify list also helps you to prevent attempts by unknown DNS servers to request zone updates from your server.

(Poulton, 2012 p.281)

Front 5

DDNS

Back 5

Dynamic DNS

DDNS enables DNS zone files to be updated on the fly, so to speak, whenever DNS client computers update their TCP/IP configuration information. In other words, DNS clients can dynamically update their A and PTR records in the master zone file on start-up or whenever their configuration changes. First introduced in Windows 2000, client computers automatically report their TCP/IP information to the DNS server. If your network is using Dynamic Host Configuration Protocol (DHCP), and the DHCP server can update the DDNS server with each client computer's current IP address whenever it renews client IP address leases.

(Poulton, 2012 p.266)

Front 6

AXFR

Back 6

Full Zone transfer

The original specifications for DNS supported only the full zone transfer process in which the master server transmits the entire zone database to that zone's secondary servers. When a new secondary DNS server is added to the network, it uses AXFR to obtain a full copy of the zone's resource records. AXFR was the only zone transfer process supported by Windows NT 4.0 DNS. Furthermore, a Windows Server 2008 server, when replicating with non-Windows DNS server, such as UNIX BIND servers, must use AXFR.

(Poulton, 2012 p.2278)

Front 7

Global Names zone

Back 7

A Global/Name zone is a special type of Active Directory-Integrated zone that enables you to resolve static, global records with single-label names without the need for a Windows Internet Naming (WINS) Server . You can use this zone to manage older servers that are assigned static IP addresses and have been managed using WINS. You should not use this zone type to support the name resolution of records that are dynamically registered to the WINS.

(Poulton, 2012 p.252)

Front 8

IXFR

Back 8

Incremental zone transfer

The process of incremental zone transfer, as specified in RFC 1995, replication only the modified portion of each zone file. It is therefore more efficient and uses less bandwidth than the full zone transfer process.

(Poulton, 2012 p.278)

Front 9

NDDNS

Back 9

Non-dynamic DNS

Non-Dynamic DNS was the default prior to Windows 2000. At that time, the administrator was required to enter A record manually to keep the DNS database up-to-date, although it was possible to integrate DNS with WIN to provide a "pseudo" dynamic version of DNS.

(Poulton, 2012 p.266)

Front 10

NSLOOKUP

Back 10

The nslookup command enables you to check the connectivity to DNS servers and display information from theses servers from the command prompt. You can use this command in either of two modes.
- Interactive MOde
- Noninteractive Mode

(Poulton, 2012 p.288)

Front 11

Primary Zone

Back 11

A master writable copy of zone data stored in a text file and administered from the server on which it is stored.

(Poulton, 2012 p.249)

Each Primary zone contains the read/write database for its zone and is stored on a DNS name server known as the primary name server. This DNS server is the primary source for information concerning this zone, and is referred to as being authoritative for its zone. By default, this primary zone is called zone_name.dns and is stored in the keysystemriit&\system32\dns folder on the server. Note that any client computer can update its records within the primary zone.

(Poulton, 2012 p.249)

Front 12

Replication scope

Back 12

The replication scope of an Active Directory-integrated DNS zone refers to the subset of DNS servers or domain controllers that actively participate in replication of the specific zone. DNS in Windows Server 2008 makes available the replication scopes described in table 6-3..

(Poulton, 2012 p.275)

Front 13

Secondary zone

Back 13

A copy of an existing zone that has been replicated from another DNS server and is stored as a read-only text file.

(Poulton, 2012 p.249)

Other DNS servers can host secondary zones that are replicas of the primary zone located on another name server across the network that authoritative for that zone the process of obtaining this zone information (that, is the database file) across the network is referred to as a zone transfer. The file itself is read-only. Changes to the zone information cannot be made to a zone file stored in the secondary name server. Such a zone is stored as a text file in the %systemroot\system32\dns folder on its server, and cannot be integrated with AD DS. Zone transfers are discussed in detail later in this chapter.

(Poulton, 2012 p.250)

Front 14

SDDNS

Back 14

Secure Dynamic DNS

is an enhancement that enables you to permit dynamic updates only from the authorized client computer in an Active-Directory-integrated zone. Secure dynamic updates are defined by RFC 2137.

(Poulton, 2012 p.266)

Front 15

secure zone transfer

Back 15

If you are using DNS servers running BIND 9 or higher, you can specify that zone transfers be digitally signed. This feature enables secondary DNS servers to verify that the zone transfers are being received from a trusted source.

(Poulton, 2012 p.282)

Front 16

stub zone

Back 16

A secondary copy of an existing zone that contains only the resources records needed to identify the authoritative DNS server for the corresponding primary zone.

(Poulton, 2012 p.249)

A stub zone is similar to a secondary zone, but includes only information about the zones authoritative name servers. As with the secondary zones, information is replicated from the authoritative server hosting the corresponding primary zone

(Poulton, 2012 p.251)

Front 17

zone

Back 17

Each DNS serve stores information about a portion of the internet namespace. Such a portion is known as a zone, and the DNS server that is primarily responsible for each zone is considered to be authoritative for that zone. In other words. The DNS server is the main source of information regarding the Internet address contained within the zone. A zone can be considered as part of the big database that is DNS, and can contain information on one or more domain zones are defined by who looks after maintaining the records that they contain.

(Poulton, 2012 p.249)

Front 18

zone delegation

Back 18

zone transfers A mechanism that replicates and synchronizes all copies of the zone files between DNS name servers.

(Poulton, 2012 cd. glossary)

Front 19

zone file

Back 19

zone file A file that includes all resource records needed to completely define a zone and is kept on the DNS name server.

(Poulton, 2012 cd. glossary)

Front 20

zone transfers

Back 20

Zone Transfer, which can be used by all types of DNS zones. Active Directory-integrated zones also use zone transfer to replicate data to a standard secondary zone located on another DNS server operated for the purposes of fault tolerance, load balancing, and reduction of DNS network traffic.

(Poulton, 2012 p.274)