Authoritative BIND: Declare a Forward Zone and Write Its Zone File

MediumNetworking25-35 min

The brief

BIND is installed but serves no zones. Your per-session assignment is in /root/case/assignment.env (DOMAIN, HOST, IP, ZONEFILE); read it and stand up an authoritative forward zone.

Two tasks:

1. Declare the zone in /etc/bind/named.conf.local — a zone "DOMAIN" { type master; file "ZONEFILE"; }; block (type primary;, the newer spelling, is accepted too).

2. Write the zone file at ZONEFILE with a SOA record, at least one NS record, and an A record mapping HOST to IP.

Graded on named.conf.local and the zone file — it does not start named, so editing the files directly works. On a live server, named-checkconf validates the config and named-checkzone DOMAIN ZONEFILE validates the zone.

What you'll do

Declare an authoritative master forward zone in named.conf.local
Point the zone at its zone file
Write a valid zone file with SOA, NS, and an A record
Map the assigned host to its address

Hands-on lab: you work on a real Linux box in your browser, graded on the machine's actual state.