📢Configurar 🖥 servidor DNS en Windows Server 2022

How to Configure a DNS Server on Windows Server

Introduction to DNS

• The video begins with an introduction to configuring a DNS server on Windows Server 2022.

• A brief explanation of the network setup is provided, including two network adapters: one in NAT mode configured via DHCP and another with a static IP (192.168.1.7).

Client Configuration

• The client machine running Windows 10 is set up in DHCP mode, receiving an IP address automatically within the specified range (192.168.1.100 - 192.168.1.150).

• The importance of DNS is highlighted; it resolves domain names into IP addresses, facilitating internet access.

Understanding DNS Functionality

• An example is given where the client uses ipconfig /all to check its configuration, revealing the assigned IP and subnet mask.

• When attempting to resolve a domain name like google.es, the request goes to the Windows Server's DNS for resolution.

Role of Forwarders in DNS

• If the local DNS does not have information about a requested domain (e.g., google.es), it queries configured forwarders for assistance.

• The process involves checking if local records exist before forwarding requests externally.

Setting Up Zones in Windows Server

• The tutorial transitions into setting up zones within Windows Server 2022’s DNS management console.

• It explains how to navigate through existing configurations and verify that default roles are installed correctly.

Creating New Zones

• A demonstration follows on creating new forward lookup zones, specifically for "clubword.local."

• After creating zones, testing with pings shows whether they resolve correctly based on existing records or require external queries.

Adding Hosts and Testing Resolution

• Instructions are provided for adding new hosts within created zones and verifying their functionality through ping tests.

• The process emphasizes ensuring that newly added hosts can be resolved by the server as intended.

Understanding DNS Resolution in Windows 10

Overview of DNS Configuration

• The process begins with Windows 10 querying the configured DNS server for a domain, such as www.asir.com. If the host is not found locally, it forwards the request to designated forwarders.

Checking Connectivity and Cache Management

• A ping test is conducted to check connectivity; however, results may be affected by cached data that needs to be cleared.

• Using ipconfig /? reveals various options for managing network configurations. The focus here is on clearing the DNS cache using ipconfig /flushdns.

Displaying Cached Entries

• Executing ipconfig /displaydns shows cached entries, including asir.com, which allows for quicker resolution of previously accessed domains.

• After flushing the DNS cache successfully, running ipconfig /displaydns again confirms that no entries remain.

Domain Name Resolution Process

• When attempting to ping www.asir.com post-cache flush, Windows queries its DNS server for the current IP address associated with the domain.

Creating New Zones in DNS

• A new forward lookup zone for facebook.com is created. However, without any hosts added under this zone, pings will fail due to unresolved addresses.

• Attempting a ping to facebook.com results in failure because no corresponding host entry exists within the newly created zone.

Handling Unresolved Domains

• For domains like YouTube or Facebook that lack defined hosts in local zones, Windows queries external forwarders configured in DHCP settings.

Forwarder Configuration and Internet Access

• Right-clicking on the domain properties reveals existing forwarders (e.g., Google’s DNS). This setup allows resolution of external domains not present in local zones.

• If an external domain (like google.es) is queried but not found locally, it checks configured forwarders (e.g., Google's 8.8.8.8).

Impact of Removing Forwarders

• Removing Google from forwarders leads to failed resolutions when accessing unconfigured domains since there are no alternative paths available for name resolution.

Conclusion on Internet Access Issues

• While internet connectivity remains intact (as verified by pinging an IP), resolving domain names fails without proper configuration of DNS servers or caches.

Understanding DNS Configuration in Windows Server

Overview of DNS and Connectivity Issues

• The speaker discusses the inability to access certain websites (e.g., facebook.com, youtube.es) due to DNS configuration issues on their server.

• An explanation of the Domain Name System (DNS) is provided, likening it to a database that maps domain names (like google.es, facebook.com) to their corresponding IP addresses.

• The speaker attempts to add an IP address for connectivity but faces challenges due to misconfiguration in the DNS settings.

Resolving Domain Names with DNS

• To connect to youtube.es, the system queries the DNS for its IP address. If not found locally, it forwards the request to Google's DNS server.

• The process of configuring a Windows Server as a DNS server is outlined, emphasizing how it resolves domain names effectively by accessing external DNS servers when necessary.

Importance of Correct DNS Configuration

• It is crucial for Windows 10 machines within a network to have their DNS set correctly (to 192.168.1.7), which points them towards the Windows Server for domain joining.

• When attempting to join a domain (e.g., clockwork.local), Windows first checks with the specified DNS server if it recognizes the domain name before proceeding with connection.

Conclusion