Question

how to Creating and Configuring DNS Zones and Records.

provide the reference APA

Answer 1

How the Domain Name System (DNS) zones and DNS records are created and configured:
Basically, you would be required to create and configure your DNS zones and records for resolving hostnames in your public domain, so DNS servers use these zones for resolving client DNS queries. Assuming you have already purchased a domain name, for example, example.com, from a domain registrar:
In general, from a broad perspective, and from a vendor-neutral perspective:
* First, the server where your application or website is hosted, deployed, or running is located where you want to add a zone.
* Right-click the server.
* Click "Create DNS zone".
* From the "Create DNS zone" dialog box that opens up, in the "General Properties", choose a "Zone" category, a "Zone" type, type in a name in the "Zone" name.

In certain other consoles below would be the steps to be followed:
* In a DNS Manager console, a primary zone will need to be created first. Hence, in the console right-clicking the "Forward Lookup Zones" node, you get the option to create a new zone. Click "New Zone".
* In the "New Zone" wizard, click "Next" on the "Welcome To The New Zone Wizard page".
* Select "Primary Zone" on the "Zone Type", and click "Next".
* Type in the zone name, for example, example.com, in the given "Zone name" box shown on the "Zone Name" page.
* On the "Zone File" page, in case you already have a DNS zone file to populate your zone, choose the option clicking "Use This Existing File" specifying the path to the file, and click "Next".
* Otherwise, click "Create A New File With This File Name", and click "Next".
* On the "Dynamic Update" page, either choose "Allow Only Secure Dynamic Updates (Recommended For Active Directory)", "Allow Both Nonsecure And Secure Dynamic Updates", or "Do Not Allow Dynamic Updates", ad click "Next".
* Click "Finish" on the "Completing The New Zone Wizard" page.

You are basically required to store details in DNS zones about domains and subdomains and the relationship between them. The zone can be stored in files on the DNS server or in the Active Directory Domain Services (AD DS) database. Depending on the business requirement you would need to create primary, secondary, delegated, ADDS–integrated, and stub zones.

For the clients (users) to perform forward lookup queries go resolve a hostname to a corresponding Internet Protocol Version 4 (IPv4) or Internet Protocol Version 6 (IPv6) address, these need to be resolved by reference to forward lookup zones. Hence, these forward lookup zones need to be created to hold a variety of DNS record types such as Host or A records, Alias or Canonical Name (CNAME) records, records to identify which server is hosting a service such as Service (SRV) records and Mail exchanger (MX) records.

Creation and configuration of DNS resource records involve the below steps:
Zones hold DNS records pointing to name servers, services, hosts, or other zones. Once created, zones must be populated with DNS resource records that are appropriate and relevant to your organizations' company's network. These DNS resource records include:
* "Host A" host record: This record contains the IPv4 address and AAAA records hold the IPv6 address for the specified hostname. These would exist in forwarding lookup zones.
* Pointer: It is called PTR records. These enable a DNS client for resolving an IPv4 or IPv6 address into a hostname. These records are found in reverse lookup zones.
* Start of Authority: It is also called SOA record. It is created when a primary zone is created. It contains details about the authoritative server for the zone, contact information for the zone, and other details, that include Time-To-Live (TTL) values to be used for resource records in the zone.
* "Name Server" Name server (NS) records: These are used for identifying name servers in the zone, which includes primary and secondary servers.
* Service Location records: These are also called SRV records, used for enabling you for specifying by service, protocol, and DNS domain name, and which servers have been hosting particular apps or services.
* Alias CNAME records: These enable letting us create an alias for a host.
* Mail Exchanger records: These are also called MX records. These are used by Simple Mail Transfer Protocol (SMTP) hosts to transfer emails around the Internet. MX records are created in, say, the example.com namespace for advertising which hosts provide this service.

Examples:

"A" (Address) records map a name to an IPv4 address such as example.com to 192.168.1.3)
CNAME records map a name to another name such as www.example.com > example.com)
MX records control where email is to be sent.
NS records confirm your server controls.

In the process, you would have configured the A record define your primary (NS1) and secondary (NS2) name servers, individually. Later it requires to configure the domain to use the NS1 and NS2 records.