2.1Configuring and Managing BIND

Name resolution underlies nearly every network service. BIND (Berkeley Internet Name Domain; the running process is named) is the most widely deployed DNS server, and L2 tests whether you can handle its configuration file structure and query/operations commands precisely.

2.1.1The structure of named.conf

• named.conf is BIND's core config. An options { } block sets overall defaults (listen addresses, recursion, forwarding), followed by per-zone statements like zone "example.com" { type master; file "..."; };.
• A zone's type is chiefly master (primary; holds the authoritative data), slave (secondary; replicates from a master via a zone transfer), or forward (answers nothing itself, only forwards to specified servers).
• Check syntax and typos with named-checkconf before starting the daemon—this habit prevents outages. Apply changes afterward with rndc reload and similar.

2.1.2Query and operations commands

• dig is the most detailed query tool. dig @ns1.example.com www.example.com A lets you specify the server, name, and record type explicitly, showing the ANSWER and AUTHORITY sections—making it the primary troubleshooting tool.
• host gives a quick resolution check (host www.example.com). nslookup is the traditional tool supporting both interactive and non-interactive use. Both produce simpler output than dig.
• rndc remotely controls a running named (rndc reload reloads config, rndc reload zone reloads just one zone, rndc flush clears the cache, rndc status). Its advantage is applying changes without stopping named.

A real scenario clarifies the roles. To stand up a new internal zone example.com as a master server, add zone "example.com" { type master; file "/var/named/example.com.zone"; }; to named.conf, verify no syntax errors with named-checkconf, then apply it to the running named with rndc reload. A secondary (slave) server uses the same zone name but type slave; masters { 192.0.2.1; };—specifying the master's IP address—and fetches data via a zone transfer on first startup. When queries fail to return, use dig to switch which server you are asking (the @ option), isolating whether the authoritative server returns correct records and whether recursive resolution through a caching server works. For small or embedded use, dnsmasq (lightweight DNS + DHCP) is common; Unbound suits a cache-only recursive resolver; NSD is a fast, simple authoritative-only implementation; and PowerDNS excels when backed by a database—so implementations other than BIND get chosen depending on requirements.

2.1.3Section summary

• named.conf zone type = master (primary) / slave (secondary; replicates via zone transfer) / forward (forward-only)
• named-checkconf = syntax check / rndc = operate without downtime / dig = detailed queries. Lightweight alternatives: dnsmasq, Unbound, NSD, PowerDNS