The Domain Name System (DNS) stands as a pivotal service, serving the purpose of executing the process of name resolution. This procedure involves the intricate task of mapping domain names to their corresponding IP addresses and the reciprocal mapping of IP addresses to domain names. Despite the fundamental communication between systems relying on IP addresses, the daunting challenge of retaining the multitude of IP addresses for numerous clients within an expansive enterprise network becomes apparent. This is where the DNS service emerges, granting the capability to interact with systems via domain names, a far more manageable and memorable alternative to the labyrinthine realm of IP addresses.

Within the scope of this discourse, we shall elucidate the methodology to install and configure a DNS server on a Windows Server 2016 platform. Prior to embarking on the configuration journey of the DNS server, it is imperative to acquaint oneself with the underlying topology that we are poised to employ. Our elucidation of this meticulous guide will be accompanied by the utilization of the ensuing set of systems:

DC1: This designated entity embodies a preconfigured Windows Server 2016 domain controller, meticulously structured for the mcsalab.local domain. Its allocated IP address is set as 10.0.0.100/8, and its designated roles as a Primary DNS Server and Secondary DNS Server correspond to the IP addresses 10.0.0.100 and 10.0.0.101, respectively.

Server1: An integral component of the mcsalab.local domain, Server1 manifests as a Windows Server 2016 member server. Its assigned IP address reads as 10.0.0.101/8, while it dutifully undertakes the mantle of both a Primary DNS Server and Secondary DNS Server, the former being represented by the IP address 10.0.0.101, and the latter by 10.0.0.100.

3.1 Implementing DNS on Windows Server 2016 (Step by Step guide)

Transforming a Domain Member to a Domain Controller

When one aims to elevate a server’s status to become an additional domain controller, it is essential to have a DNS server in place. Such a DNS server aids in the efficient resolution of domain names within a network, thereby facilitating communication. The options available are either to leverage an already-established DNS server within the domain or to pave the way for its installation and configuration at a later juncture. It’s worth noting that during the configuration of the primary domain controller (often referred to as the root domain), direct modifications to the DNS Server role aren’t permitted, resulting in it being non-accessible or grayed out. For illustrative purposes, let’s use a situation where a pre-established DNS server exists on the root domain server (named DC1). The goal is to initiate the installation and adjustment of the DNS server on an additional domain controller, labeled Server1. For a smooth transformation of a domain member (Server1) into a domain controller, the following procedures need diligent execution:

Initiation Phase:

• Access the Server Manager dashboard;
• Initiate the ‘Add roles and features’ assistant.

Selection Phase:

• Navigate through the wizard until reaching the ‘Select server roles’ screen;
• Opt for ‘Active Directory Domain Services’ by marking its checkbox;
• Proceed by selecting ‘Add Features’ to integrate any requisite additional functionalities.

Completion Phase:

• Progress through the subsequent screens, keeping the default choices intact;
• Finalize the installation process.

Promotion Stage:

• Within the Server Manager interface, identify and click the Notifications symbol;
• Choose the ‘Promote this server to a domain controller’ option;
• DNS Server Configuration for Additional Domain Controller (ADC).

Deployment Settings:

• On the Deployment Configuration screen, ensure the choice ‘Add a domain controller to an existing domain’ is active;
• Within the ‘Supply the credentials for this operation’ segment, opt for ‘Change’ and provide credentials, ideally in the ‘DomainName\Administrator’ pattern.

Domain Controller Specifics:

• Navigate to the Domain Controller Options screen;
• Deselect the Domain Name System (DNS) server option. Further details on manual DNS Server Role installation are provided below.

Manual Installation of DNS Server Role

Password Configuration:

Designate a preferred DSRM (Directory Services Restore Mode) password.

Final Steps:

Navigate seamlessly through the assistant until reaching the ‘Prerequisites Check’ screen.

Opt to ‘Install’. Once the process concludes, a server restart is advised to ensure all changes take effect seamlessly.

Creation and Configuration of DNS Zones

Setting up a domain controller is the precursor to creating a DNS zone. Once the server (referred to as Server1) is established as a domain controller (DC1), the next step is the creation of the DNS zone. The process of establishing this zone, replicating it, and subsequently testing it on Server1 involves specific steps. These steps are outlined below:

Accessing the DNS Manager Console:

• Launch the Server Manager console on DC1;
• Under the Tools menu, locate and select the DNS Manager console to open it.

Zone Creation:

• Within the DNS Manager, you will find an option to expand the domain server. Do so;
• Seek out the ‘Forward Lookup Zones’ and give it a right-click. From the context menu that pops up, choose the ‘New Zone’ option.

Setting the Zone Type:

• You’ll then be directed to the ‘Zone Type’ page;
• Ensure the ‘Primary zone’ radio button is chosen;
• There’s an option that says ‘Store the zone in Active Directory’; deselect this by removing the check mark.
• Click on ‘Next’ to proceed.

Naming the Zone:

• When you reach the ‘Zone Name’ page, enter a name for your zone;
• Once done, click on ‘Next’.

Dynamic Update Settings:

• Move on to the ‘Dynamic Update’ page;
• Select the ‘Do not allow dynamic updates’ radio button;
• To continue, click ‘Next’. Conclude the process by completing the wizard.

Integrating Hosts to the DNS Zone

Having created the DNS zone, the next step involves adding specific hosts. For instance, in the provided scenario, the objective is to integrate the host ‘Server1’ into the established DNS zone. Here’s how you can go about it:

Access the Desired Zone:

• Within the DNS Manager console, find and expand the ‘Forward Lookup Zones’;
• Once you locate the zone you’ve created, right-click it. From the dropdown, select ‘New Host (A or AAAA)’.

Host Details Entry:

• A dialog box titled ‘New Host’ will appear;
• Here, you’ll need to input the Hostname and IP address corresponding to your host;
• To add the host, click on the ‘Add Host’ button.

Completion:

• After integrating all the necessary hosts, finalize the process by clicking ‘Done’.

Note: Familiarity with the DNS server settings, especially when working with platforms like Windows Server 2016, can be beneficial for smooth operations. Always ensure you have the correct permissions and backup configurations when making changes.

DNS Server Role Installation

DNS (Domain Name System) is a foundational element for internet infrastructure, converting human-readable domain names to IP addresses. In previous operations, a DNS zone was set up on the domain controller and a host was added to this zone. To further strengthen the DNS architecture, consider installing the DNS Server role on a secondary server. This action bolsters redundancy and can improve reliability. Here’s how to undertake this crucial task:

• Accessing the Server Management Tool: Begin by launching the Server Manager console on the secondary server, termed ‘Server1’ for reference. This console is pivotal for managing server roles and features;
• Launching the Wizard: Within the Server Manager, initiate the “Add roles and features” wizard. This tool streamlines the process of augmenting the server’s capabilities;
• Choosing the DNS Server Role: Navigate through the wizard until reaching the “Select server roles” page. Here, pinpoint and select the ‘DNS Server role’ option;
• Finalizing the Installation: Upon choosing the role, opt for the ‘Add Features’ button. Then, click ‘Next’ on the subsequent pages. Once all selections are appropriately made, finalize the process to install the role.

Replication of DNS Zones

With the DNS server role now active, replication becomes paramount. This ensures the secondary DNS server mirrors the configurations of the primary, enhancing fault tolerance. Here’s how to execute this replication process on Server1:

DNS Zone Verification:

On Server1, initiate the DNS Management console. Upon refreshing, it should display the DNS zones of the primary DNS server. It’s imperative to check this to ascertain the accuracy of replication.

Special Note: If zones aren’t visible, do not worry. Continue to the steps outlined below.

Active Directory Sites Replication:

• Launch the Active Directory Sites and Services console;
• Expand the ‘Sites’ category and then tap on ‘Default-First-Site-Name’;
• Delve into the ‘Servers’ section and select the primary domain controller, referred to as ‘DC1’;
• Navigate to ‘NTDS Settings’. Once there, locate the replication connection for Server1. Right-click and opt for ‘Replicate Now’. This initiates the replication of DNS modifications.

Attention: An error message might occasionally pop up during this process. Should this occur, there’s a further step to address it.

Addressing Replication Errors:

Within the NTDS Settings area, pinpoint the replication connection for DC1. Right-click, select ‘Replicate Now’, and affirm with an ‘OK’. Afterward, head back to the DNS Manager console, refresh, and inspect if the DNS zones now appear. This step rectifies replication issues and ensures a consistent DNS environment.

Conclusion

Within this article, we’ve thoroughly examined the process of setting up and fine-tuning a DNS Server on the Windows Server 2016 platform. However, your journey doesn’t conclude at this juncture; there’s more to accomplish. Keep yourself engaged for our upcoming publication, where we’ll delve into the meticulous steps of configuring a DNS forwarder within the Windows Server environment. If you’ve found this content compelling, we encourage you to spread the love by sharing this article with your peers.