Types of DNS Zones.
Ans : There are two types of zones, forward lookup and reverse lookup.
Forward lookup zones contain information needed to resolve names within the DNS domain. They must include SOA and NS records and can include any type of resource record except the PTR resource record.
Reverse lookup zones contain information needed to perform reverse lookups. They usually include SOA, NS, PTR, and CNAME records.
With most queries, the client supplies a name and requests the IP address that corresponds to that name. This type of query is typically described as a forward lookup. Active Directory requires forward lookup zones.
However, what if a client already has a computer's IP address and wants to determine the DNS name for the computer? This is important for programs that implement security based on the connecting FQDN, and is used for TCP/IP network troubleshooting. The DNS standard provides for this possibility through reverse lookups.
Once you have installed Active Directory, you have two options for storing your zones when operating the DNS server at the new domain controller:
Standard Zone
Zones stored this way are located in .dns text files that are stored in the %SystemRoot%\System32\Dns folder on each computer operating a DNS server. Zone file names correspond to the name you choose for the zone when creating it, such as Example.microsoft.com.dns if the zone name was example.microsoft.com.
This type offers the choice of using either a Standard Primary zone or a Standard Secondary zone.
Standard Primary Zone
For standard primary-type zones, only a single DNS server can host and load the master copy of the zone. If you create a zone and keep it as a standard primary zone, no additional primary servers for the zone are permitted. Only one server is allowed to accept dynamic updates, also known as DDNS, and process zone changes. The standard primary model implies a single point of failure.
Standard Secondary Zone
A secondary name server gets the data for its zones from another name server (either a primary name server or another secondary name server) for that zone across the network. The data in a Secondary zone is Read only, and updated information must come from additional zone transfers. The process of obtaining this zone information (i.e., the database file) across the network is referred to as a zone transfer. Zone transfers occur over TCP port 53.
Secondary servers can provide a means to offload DNS query traffic in areas of the network where a zone is heavily queried and used. Additionally, if a primary server is down, a secondary server can provide some name resolution in the zone until the primary server is available.
Ans : There are two types of zones, forward lookup and reverse lookup.
Forward lookup zones contain information needed to resolve names within the DNS domain. They must include SOA and NS records and can include any type of resource record except the PTR resource record.
Reverse lookup zones contain information needed to perform reverse lookups. They usually include SOA, NS, PTR, and CNAME records.
With most queries, the client supplies a name and requests the IP address that corresponds to that name. This type of query is typically described as a forward lookup. Active Directory requires forward lookup zones.
However, what if a client already has a computer's IP address and wants to determine the DNS name for the computer? This is important for programs that implement security based on the connecting FQDN, and is used for TCP/IP network troubleshooting. The DNS standard provides for this possibility through reverse lookups.
Once you have installed Active Directory, you have two options for storing your zones when operating the DNS server at the new domain controller:
Standard Zone
Zones stored this way are located in .dns text files that are stored in the %SystemRoot%\System32\Dns folder on each computer operating a DNS server. Zone file names correspond to the name you choose for the zone when creating it, such as Example.microsoft.com.dns if the zone name was example.microsoft.com.
This type offers the choice of using either a Standard Primary zone or a Standard Secondary zone.
Standard Primary Zone
For standard primary-type zones, only a single DNS server can host and load the master copy of the zone. If you create a zone and keep it as a standard primary zone, no additional primary servers for the zone are permitted. Only one server is allowed to accept dynamic updates, also known as DDNS, and process zone changes. The standard primary model implies a single point of failure.
Standard Secondary Zone
A secondary name server gets the data for its zones from another name server (either a primary name server or another secondary name server) for that zone across the network. The data in a Secondary zone is Read only, and updated information must come from additional zone transfers. The process of obtaining this zone information (i.e., the database file) across the network is referred to as a zone transfer. Zone transfers occur over TCP port 53.
Secondary servers can provide a means to offload DNS query traffic in areas of the network where a zone is heavily queried and used. Additionally, if a primary server is down, a secondary server can provide some name resolution in the zone until the primary server is available.