CloudLabBox
Try the free demo

MikroTik MTCTCE lab 6 of 8

DNS cache, DHCP relay and options, and the web proxy

Fernvale's new Quayside branch has no servers of its own. Make the branch router a caching DNS server with local names, relay the branch's DHCP to the head office server with built-in and custom options and a reserved address, and put a transparent web proxy in the path that blocks what the policy forbids.

Run this lab

It needs Lite: its 3 nodes are set to 3 vCPU and 768 MB in total. That fits the free demo too.

In your workspace: Shared, then MikroTik MTCTCE RouterOS v7 guided labs, then 06 - DNS cache DHCP relay and options and the web proxy

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 60 minutes
Nodes need
3 vCPU, 768 MB
Smallest plan
Lite

The scenario

Fernvale has opened a small branch at Quayside. It has a router and staff PCs, but no servers: the head office (HQ, 192.0.2.1 across a private link) already runs Fernvale's DNS, DHCP, NTP and intranet web servers. Your job is to make the branch work as if those services were local, and to control what the staff can browse:

  • QUAYSIDE answers the branch's DNS queries from its cache, with a few local names of its own.
  • Branch PCs get their addresses from HQ's DHCP server, through a relay on QUAYSIDE.
  • All web traffic from the branch goes through QUAYSIDE's web proxy, which blocks the /blocked/ area of every site.
DeviceInterfaceAddress
HQether1192.0.2.1/30 (DNS, DHCP, NTP and web server)
QUAYSIDEether1 · ether2192.0.2.2/30 · 192.168.60.1/24
PC1 (a RouterOS router playing a staff PC)ether1DHCP, reserved later as 192.168.60.50

What you’ll practise

  • Run the router as a caching DNS server with static A, CNAME and NXDOMAIN entries, and keep it closed to the WAN
  • Serve DHCP for a remote LAN from a central server through a DHCP relay
  • Hand out built-in options from the DHCP network and a custom option from the option table
  • Read the DHCP exchange in the log and reserve an address for a client
  • Redirect web traffic into a transparent web proxy and deny requests with the access list

The tasks

  1. A caching DNS server at the branch
  2. A central DHCP server, reached through a relay
  3. Watch a client get its lease
  4. A custom option and a reserved address
  5. A transparent web proxy with an access list

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.

Topology of DNS cache DHCP relay and options and the web proxy3 nodes, 2 links. Every link is listed as text below the diagram.HQQUAYSIDEPC1ether1ether1ether2ether1
3 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • HQ ether1 to QUAYSIDE ether1
  • QUAYSIDE ether2 to PC1 ether1
Nodes in DNS cache, DHCP relay and options, and the web proxy, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
HQMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
QUAYSIDEMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PC1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder MikroTik MTCTCE RouterOS v7 guided labs.

  3. Open 06 - DNS cache DHCP relay and options and the web proxy and 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 MikroTik MTCTCE labs

All MikroTik MTCTCE labs

Related labs in other courses

CloudLabBox is independent of MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.