Fraîche Flow

Linux · Infrastructure · Networking · Virtualisation

docs/DNS with BIND9
59 lines1.88 KB

DNS with BIND9

MILOUD NECILI

Fraîche Flow · IT Systems Integration

Project objective

Provide central name resolution for hosts and service names in the internal fraicheflow.test zone.

My implementation

  • Edited the BIND zone on ff-core-01 and incremented SOA serial numbers in a controlled manner.
  • Set up an A record for ff-app-01 and the portal alias.
  • Resolved nextcloud.fraicheflow.test to 192.168.10.13.
  • Checked zone syntax, reloaded the zone and compared direct queries with client-side queries.

Technical context

DNS server 192.168.10.11
Zone fraicheflow.test
Zone file /etc/bind/db.fraicheflow.test
Evidenced serial numbers 2026022004 and 2026022005

Result

named-checkzone returned OK. Queries for ff-app-01, portal and nextcloud returned the expected mapping to 192.168.10.13.

Verification and operational evidence

sudo named-checkzone fraicheflow.test /etc/bind/db.fraicheflow.test
sudo rndc reload fraicheflow.test
dig @192.168.10.11 nextcloud.fraicheflow.test +short
getent hosts ff-app-01.fraicheflow.test

BIND9 zone validation and DNS resolution on ff-core-01

Practical troubleshooting

A correctly saved zone had initially not been loaded. After rndc reload, the new Nextcloud record was returned. An incorrect client resolver independently caused SSH name resolution errors.

Security and technical context

Back up the zone file before changes. Load only validated zones. The Kuma monitor named DNS ff-core-01 is a ping test, not a DNS protocol test.

Transferable skills

DNS zone maintenance, understanding A/CNAME/MX records, resolver diagnosis and controlled changes.

Project status

Completed according to confirmation from the project lead.