🌐 Homelab Chronicles: Why Can’t I Connect? Demystifying DNS and DHCP from Scratch

If you walk into any entry-level IT Helpdesk role on your very first day, you can guarantee that a massive chunk of your incoming network tickets will involve variations of one single complaint: "I can't connect to the internet," or "I can't access the company's internal shared drive."

In a corporate enterprise environment, computers don't just magically know what their IP addresses are, nor do they inherently know how to find the company's local file servers. If either of these back-end infrastructure systems fails or is misconfigured, the entire company grinds to a halt, and the helpdesk phone queue immediately fills up.

In this edition of the Homelab Chronicles, we are taking network control away from our home internet router. Using our VirtualBox setup, we will configure a dedicated DHCP (Dynamic Host Configuration Protocol) server to automatically lease IP addresses to our clients, and deploy a local DNS (Domain Name System) infrastructure so our machines can seamlessly talk to the domain controller and browse the external web.

🧠 But First… What the Heck are DHCP and DNS?

Let's skip the complex jargon. If you are sitting in a job interview, these are the exact definitions you need to know:

1. DHCP (Dynamic Host Configuration Protocol)

DHCP is an automated network protocol that automatically assigns IP configuration details to devices when they connect to a network.

• The Core Job: It acts as a automated manager that leases every device a unique IP Address, Subnet Mask, Default Gateway, and DNS Server address.
• Why it matters: Without DHCP, an IT technician would have to manually sit at every single laptop and desktop in the building to type in these numbers by hand.

2. DNS (Domain Name System)

DNS is the phonebook of the network and the internet. It translates human-readable domain names into machine-readable IP addresses.

• The Core Job: Computers only understand numbers (like 142.250.190.46), but humans understand words (like google.com). When you type a website or a local file server name into a browser, DNS instantly translates that name into its corresponding numerical IP address so your computer can connect to it.

The One-Line Summary: **DHCP hands out the network identity (IP address), while DNS **translates human names into those network identities.

💻 My Homelab Lab Specs

• Hypervisor: Oracle VM VirtualBox
• Domain Controller: Windows Server 2022 Standard (Static IP: 192.168.10.10)
• Client Machine: Windows 10 Pro (Ready to receive network configuration)
• Virtual Network Mode: Internal Network / NAT Network (Isolated from home LAN)

🛠️ Phase 1: Installing the Core Network Roles Before our server can hand out IP addresses or resolve domain names, we must install the necessary infrastructure components using Server Manager.

Step 1: Open Add Roles and Features Wizard

• Log into your Windows Server 2022 Domain Controller.
• Open Server Manager, click Tools or Manage in the top-right corner, and select Add Roles and Features.
• Click Next through the prompt screens until you reach the Server Roles selection window.

Step 2: Enable DHCP and DNS

• In the roles list, check the box for DHCP Server. Click Add Features on the popup window that appears.
• Check the box for DNS Server (if it wasn't already installed during your Active Directory setup). Click Add Features.
• Click Next through the remaining default windows, and click Install. Wait for the installation to finish.

🔒 Phase 2: Authorizing and Configuring the DHCP Scope Now that the software is installed, we must create a defined pool of IP addresses (a Scope) that our server is authorized to distribute to network clients.

Step 3: Post-Deployment Configuration

• In Server Manager, look for the yellow notification flag at the top right and click Complete DHCP configuration.
• Follow the quick wizard to authorize the DHCP server within your Active Directory domain. This requires Domain Admin credentials.

Step 4: Create a New IPv4 Scope

• Go to Server Manager ➔ Tools ➔ DHCP.
• Expand your server name, right-click IPv4, and select New Scope.
• Name the scope something descriptive, like Corp_Client_LAN.
• Define your IP Address Range. For this lab, set the Start IP address to 192.168.10.50 and the End IP address to 192.168.10.150. Set the Subnet Mask to length 24 (255.255.255.0).
• Click Next through exclusions. Leave the default Lease Duration at 8 days.

Step 5: Configure Crucial DHCP Options

• When prompted to configure DHCP options, select Yes, I want to configure these options now.
• Router (Default Gateway): Type the IP of your lab's network gateway router (e.g., 192.168.10.1) and click Add.
• DNS Server: This is the most crucial part! Ensure the list points exactly to your Windows Server 2022 Domain Controller IP (192.168.10.10). Delete any external router IPs here. Clients must use the DC for DNS to properly communicate with the domain.
• Click Next and select Activate this scope.

⚡ Phase 3: Configuring DNS Forwarders for External Web Access Your client machine can now find the server, but if it tries to go to google.com, your local server won't know where that is. We need to tell our DNS server to forward unknown public web queries to an external public provider.

Step 6: Setup DNS Forwarders

• Go to Server Manager ➔ Tools ➔ DNS.
• Right-click your server name in the left pane and select Properties.
• Navigate to the Forwarders tab and click Edit…
• Type in a reliable public DNS address, such as Google's 8.8.8.8 or Cloudflare's 1.1.1.1.
• Click OK and then click Apply. Your server can now resolve internal corporate locations while safely outsourcing public internet lookups.

🧪 Phase 4: Testing & Verification on the Client Machine Let's step back into our Helpdesk engineer shoes. We need to go to our Windows 10 workstation, force it to dump its old networking information, and grab our fresh corporate configuration.

Step 7: Refresh and Inspect Client Network Settings

• Switch over to your Windows 10 Pro Client VM.
• Open the Command Prompt (cmd) as an administrator and execute the following two commands back-to-back:

ipconfig /release
ipconfig /renew

ipconfig /release
ipconfig /renew

• Once the adapter pulls a new IP address, verify the configuration by typing:

ipconfig /all

ipconfig /all

• The Final Result: Verify that your IPv4 address falls within the .50 to .150 pool, and confirm that the DHCP Server and DNS Server fields point precisely to your Windows Server 2022 IP.

🚀 Bonus Helpdesk Pro-Tip: Mastering Command-Line Diagnostics (nslookup) When a user tells you an app isn't loading, don't just guess. Use nslookup directly inside the client command prompt to pinpoint whether it is a network connectivity issue or a DNS failure:

• Type nslookup google.com on the client.
• The first two lines of output show you which DNS server answered the request (it should be your Windows Server IP). The lines below show the public IP destination.
• If nslookup fails to return an answer but you can successfully ping your server's IP address directly (ping 192.168.10.10), you know immediately that the network path is open, but the DNS Server service on the controller is stopped or misconfigured!

📝 Summary By completing this infrastructure deployment lab, you have mastered the underlying networking dependencies of any corporate environment:

• Dynamic Address Allocation: Building and activating authorized DHCP scopes to manage automated IP leasing.
• Name Resolution Architecture: Setting up local DNS infrastructure to support Active Directory domain record tracking.
• External Traffic Routing: Implementing DNS Forwarders to bind private local server namespaces seamlessly with public web targets.
• Network Command Utilities: Troubleshooting client stack dependencies using core support commands (ipconfig, nslookup).