Network+ lab 14 of 27
DNS: records and lookups with forwarding and the hosts file
Run name resolution for an office. You publish A, AAAA, MX and NS records, look them up forwards and backwards with nslookup and dig, forward unknown names to an upstream server, and see how the hosts file overrides DNS and quietly causes faults.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 2,560 MB in total. That fits the free demo too.
In your workspace: Shared, then CompTIA Network Plus N10-009 guided labs, then 14 - DNS - records and lookups with forwarding and the hosts file
- Level
- Intermediate
- Time
- About 55 minutes
- Nodes need
- 4 vCPU, 2,560 MB
- Smallest plan
- Lite
The scenario
Harbour Logistics wants staff to use names instead of addresses: the intranet www, the mail server, and the file server. Partners' names must resolve too. Today nothing has a name. You'll publish the company's records on R1, make R1 forward everything else to the provider's server R2, and learn to prove and troubleshoot name resolution from the client side.
| Name (harbour.lab) | Type | Value |
|---|---|---|
| www | A | 10.10.10.80 |
| www | AAAA | 2001:db8:10::80 |
| A | 10.10.10.25 | |
| files | A | 10.10.10.30 |
| ns1 | A | 10.10.10.1 |
| harbour.lab | MX | 10 mail.harbour.lab |
| harbour.lab | NS | ns1.harbour.lab |
H1 gets its address, DNS server (10.10.10.1) and search domain (harbour.lab) from R1 by DHCP. NETOPS has dig.
What you’ll practise
- Explain DNS resolution: stub resolver, recursive resolver, authoritative server, caching and TTL
- Publish A, AAAA, MX and NS records and use automatic reverse (PTR) lookups
- Query each record type with nslookup and dig, and read dig's flags and sections
- Forward unknown names to an upstream server
- Use and troubleshoot the hosts file
- Describe DNSSEC, DNS over HTTPS and DNS over TLS
The tasks
- Look at the client side
- Publish the records
- Query every record type
- Reverse lookups
- Forward everything else upstream
- The hosts file, and how it bites
- Securing DNS
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- R1
Gi0/0to Office-LAN (network) - H1
eth0to Office-LAN (network) - NETOPS
eth0to Office-LAN (network) - R1
Gi0/1to R2Gi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| NETOPS | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CompTIA Network Plus N10-009 guided labs.Open
14 - DNS - records and lookups with forwarding and the hosts fileand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More Network+ labs
Related labs in other courses
CloudLabBox is independent of CompTIA, Cisco and Netgate. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.