nerdexam
Linux_Foundation

LFCS · Question #378

Which of the following can be done to secure a BIND server? (Select THREE correct answers)

The correct answer is A. Run the BIND daemon as a nonroot user. B. Configure ACLs. D. Run the BIND daemon in a chroot jail. To enhance BIND server security, one should run the daemon with minimal privileges (as a non-root user), configure Access Control Lists (ACLs) to restrict access, and isolate the daemon within a chroot jail.

Submitted by rachelw· Apr 18, 2026Service Configuration

Question

Which of the following can be done to secure a BIND server? (Select THREE correct answers)

Options

  • ARun the BIND daemon as a nonroot user.
  • BConfigure ACLs.
  • CRequire clients to authenticate with a password before querying the server.
  • DRun the BIND daemon in a chroot jail
  • EEncrypt DNS traffic using SSL/TLS.

How the community answered

(47 responses)
  • A
    79% (37)
  • C
    15% (7)
  • E
    6% (3)

Why each option

To enhance BIND server security, one should run the daemon with minimal privileges (as a non-root user), configure Access Control Lists (ACLs) to restrict access, and isolate the daemon within a chroot jail.

ARun the BIND daemon as a nonroot user.Correct

Running BIND as a non-root user (e.g., `named` user) significantly reduces the impact of a potential compromise, as the daemon would only have limited system privileges.

BConfigure ACLs.Correct

Access Control Lists (ACLs) in BIND allow administrators to define which hosts or networks are permitted to query, transfer zones, or update DNS records, thus restricting unauthorized access.

CRequire clients to authenticate with a password before querying the server.

Standard DNS queries do not involve client authentication with passwords before querying the server; while DNSSEC provides authenticity, simple queries are unauthenticated.

DRun the BIND daemon in a chroot jailCorrect

Implementing a chroot jail isolates the BIND daemon's file system environment, confining it to a specific directory tree. This prevents a compromised BIND process from accessing or modifying other parts of the operating system.

EEncrypt DNS traffic using SSL/TLS.

While DNS over TLS (DoT) or DNS over HTTPS (DoH) can encrypt DNS traffic, this is a client-server protocol enhancement for privacy and integrity, not a direct security hardening for the BIND *server* itself to prevent attacks like cache poisoning.

Concept tested: BIND server security hardening

Source: https://bind9.readthedocs.io/en/latest/advanced.html#security-and-best-practices

Topics

#DNS server#Service security#Chroot#ACLs

Community Discussion

No community discussion yet for this question.

Full LFCS Practice