Building Intuition for DNS

In this project, we will observe A-Record, CNAME Records, and Local DNS Cache

Environments and Technologies Used

• Microsoft Azure (Virtual Machines/Compute)
• Remote Desktop
• DNS

Operating Systems Used

• Windows 10 (21H2)
• Windows Server 2022

List of Prerequisites

• Active Directory lab done
• Client and Domain Controller Connected

Actions and Observations

Connect/log into SC-1 as your domain admin account. For me, it is mydomain.com\jane_admin. Then connect to Client-1 as the admin.

From Client-1, ping mainframe and notice how it fails.

Go to DC-1 VM and then to Server Manager. Click Tools then DNS and you should see something like the photo above.

Go to Forward Lookup Zone the mydomain.com. Now we are going to add an A Record called mainframe. Mainframe is going to have the same IP address as dc-1 does.

Go back to Client-1 and try to ping mainframe again. This time it should work.

Go back to DC-1 and change mainframe's IP address to 8.8.8.8

Go back to Client-1 and ping mainframe again. Observe that it still pings the old address because it is stored in the cache.

Now we are going to flush the dns by using the command ipconfig /flushdns. And the ping mainframe again and it should show the new IP address of 8.8.8.8

Go to DC-1 and create a CNAME record that points the host "search" to www.google.com. Return to Client-1 and try to ping "search'.

It should be able to ping "search"! This is the end of this project!