DNS Server Administration with BIND9
Intermediate60 min5 objectives

DNS Server Administration with BIND9

Practice DNS Server Administration with BIND9 in a deterministic local workspace without unavailable external infrastructure.

Briefing

### Scenario You are a dns practitioner handling a realistic client engagement. For DNS Server Administration with BIND9, the client has provided a staging environment that mirrors production but is isolated to this lab. Your task is to demonstrate the core technique on the local target without touching external systems. The scenario is intentionally scoped to what you can verify inside the container. ### Environment and scope Use the Ubuntu 22.04 practice container. Working directory is `/home/student/lab-work` (create it with `mkdir -p`). Target is `127.0.0.1` and `127.0.0.1:8080` where a `python3 -m http.server` or service-specific daemon runs. Install only needed tools via `sudo apt-get update && sudo apt-get install -y bind9, dnsutils` then verify with `named -v (9.18.39) && dig -v`. Credentials: `student:lab123` with `sudo` (created via `useradd` + `chpasswd` + `sudoers.d` as in `labs.service.ts:554`). Do not scan or query outside 127.0.0.0/8 or lab-work. Scope is strictly container-only; no external cloud, hardware, or nested container engines. ### Mission objective For DNS Server Administration with BIND9: install and verify tooling, prepare the local target (`bind9 on 127.0.0.1 with lab.internal zone`), execute the technique step-by-step, and collect evidence. Each walkthrough step produces a verifiable artifact (file, command output, or service state) that you will cite in your submission. ### Success criteria You have completed the lab when: - Tooling verification passes (`named -v (9.18.39) && dig -v` returns expected version without error) - Local target is running and responds (`curl -s http://127.0.0.1:8080/` or `dig @127.0.0.1` or `tshark -r` shows expected output) - `solution.md` in `lab-work` documents each step's exact command, raw output excerpt, and your interpretation (what the output proves) - All flag answers are direct values from your local output (e.g., version string, status code, IP, header name) and no external hosts were targeted (`history | grep -E "nmap|dig|tshark|openssl|nikto|curl"` shows only 127.0.0.1) Runtime mode: portable artifact validation

Objectives

  • 1Prepare workspace and verify tooling
  • 2Prepare local target for DNS Server Administration with BIND9
  • 3Start BIND without systemd
  • 4Create and validate zone
  • 5Complete dig Query Results
  • 6Complete Zone File Syntax
  • 7Tune and interpret
  • 8Compile and verify submission

Flags

dig Query Results+250 pts

Submit the verifiable output value for dig Query Results as produced by the local tool on 127.0.0.1 (e.g., version, status, IP, or header).

Zone File Syntax+150 pts

Submit the synthesized artifact value for Zone File Syntax (e.g., IP 127.0.0.2 or zone name) as verified by dig or cat /etc/bind/.

DNSSEC Key Generation+200 pts

Submit the verifiable output value for DNSSEC Key Generation as produced by the local tool on 127.0.0.1 (e.g., version, status, IP, or header).

named.conf Options+150 pts

Submit the verifiable output value for named.conf Options as produced by the local tool on 127.0.0.1 (e.g., version, status, IP, or header).

SOA Record Values+100 pts

Submit the verifiable output value for SOA Record Values as produced by the local tool on 127.0.0.1 (e.g., version, status, IP, or header).

Deploy Lab — 30sCreate Free Account