zNetLaB › Guided labs › Enterprise
Web services — DNS and HTTP across a routed network
Enterprise Intermediate 6 devices 6 checked tasks 100 points Plan lab
A client on one subnet browses a web server on another. Route it, point the client at DNS, publish the record, then capture the whole exchange packet by packet. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
A client on one subnet browses a web server on another. Route it, point the client at DNS, publish the record, then capture the whole exchange packet by packet.
Your role: a network engineer on the enterprise team. Level: Intermediate Done when: all 6 goals show as passed (100 points).
Network status
Devices: 1 PC, 2 switchs, 1 router, 2 servers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. Client is a host with 10.20.1.10/24, gateway 10.20.1.1. WebServer is a host with 10.20.2.10/24, gateway 10.20.2.1. DNSServer is a host with 10.20.2.20/24, gateway 10.20.2.1. SW-Client, Router, SW-Server start with an empty configuration. Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure. Goals
Router interfaces addressed and up on both subnets (15 pts) Client can ping the web server across the router (15 pts) Client can load the page by IP address (20 pts) DNS server is running and has an A record for web.znetlab.local (20 pts) Client resolves web.znetlab.local to 10.20.2.10 (15 pts) Client can load the page by name (15 pts) The activity, in order
Router interfaces addressed and up on both subnets Why: A router interface routes nothing until it has an address and is up. Every other task builds on this one. Verify with: show ip interface brief Client can ping the web server across the router Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 10.20.2.10 Client can load the page by IP address Why: Each goal is a state the lab can check on the running device. Verify with: show running-config DNS server is running and has an A record for web.znetlab.local Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Client resolves web.znetlab.local to 10.20.2.10 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Client can load the page by name Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Why this matters
A client on one subnet browses a web server on another. Route it, point the client at DNS, publish the record, then capture the whole exchange packet by packet.
What you will be able to do
Router interfaces addressed and up on both subnets
Client can ping the web server across the router
Client can load the page by IP address
DNS server is running and has an A record for web.znetlab.local
The network
PC, Switch 8-port, ISR 2911, Server — 6 devices in all, already cabled.
Fa0 Fa0/1 Fa0/2 Gi0/0 Gi0/1 Fa0/1 Fa0/2 Fa0 Fa0/3 Fa0 Client 10.20.1.10/24 · gw 10.20.1.1 SW-Client Router SW-Server WebServer 10.20.2.10/24 · gw 10.20.2.1 DNSServer 10.20.2.20/24 · gw 10.20.2.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
Client PC 10.20.1.10 / 255.255.255.0 gw 10.20.1.1 SW-Client Switch 8-port configure it Router ISR 2911 configure it SW-Server Switch 8-port configure it WebServer Server 10.20.2.10 / 255.255.255.0 gw 10.20.2.1 DNSServer Server 10.20.2.20 / 255.255.255.0 gw 10.20.2.1
Cabling
Client Fa0 ↔ SW-Client Fa0/1 SW-Client Fa0/2 ↔ Router Gi0/0 Router Gi0/1 ↔ SW-Server Fa0/1 SW-Server Fa0/2 ↔ WebServer Fa0 SW-Server Fa0/3 ↔ DNSServer Fa0
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 Router interfaces addressed and up on both subnets 15 On Router: show ip interface brief — Gi0/0 has 10.20.1.1 and is up/up. and On Router: show ip interface brief — Gi0/1 has 10.20.2.1 and is up/up. 2 Client can ping the web server across the router 15 On Client: ping 10.20.2.10 must succeed. 3 Client can load the page by IP address 20 From Client, fetching 10.20.2.10 must work (the browser, or curl 10.20.2.10). 4 DNS server is running and has an A record for web.znetlab.local 20 Checked automatically against the device’s live state (serviceOn). and Checked automatically against the device’s live state (dnsRecord). 5 Client resolves web.znetlab.local to 10.20.2.10 15 On Client: nslookup web.znetlab.local resolves. 6 Client can load the page by name 15 From Client, fetching web.znetlab.local must work (the browser, or curl web.znetlab.local).
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
Router interface g0/0
ip address 10.20.1.1 255.255.255.0
no shutdown
exit
interface g0/1
ip address 10.20.2.1 255.255.255.0
no shutdown Where this is examined
This lab practises these topics in the zNetLaB certification courses:
OSI and TCP/IP models, TCP vs UDP — CCNA · Network Fundamentals DHCP, DNS, NTP, SNMP, Syslog — CCNA · IP Services Troubleshooting DHCP, NAT, SNMP, syslog, IP SLA, NetFlow — CCNP Enterprise · ENARSI · Infrastructure Services OSI model, ports and protocols — CompTIA Network+ · Networking Concepts DHCP, DNS, NTP and network services — CompTIA Network+ · Network Operations Footprinting, DNS and passive reconnaissance — Ethical Hacking (network level) · Reconnaissance, Scanning and Enumeration DNS, DHCP, HTTP and TLS in captures — Packet Analysis with Wireshark · Reading protocols
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.