Why would you use forward zones?

• A. To centralize external DNS resolution and reduce recursive load
• B. To host dynamic updates locally
• C. To duplicate all DNS data locally
• D. To enable zone transfers to secondary servers

Answer: (A)

Forward zones route queries for a specific set of domain names to an upstream DNS server instead of resolving them on your own resolver. This centralizes how external lookups are performed and reduces the recursive work your internal DNS servers must do, since they hand off those lookups to a designated forwarder. The result is more controlled, potentially faster external resolution and consistent results due to caching at the forwarder, which is especially useful in organizations that want to polices or optimize internet-bound traffic.

Hosting dynamic updates locally, duplicating all DNS data locally, or transferring zones to secondary servers are different concepts. Dynamic updates concern how records are updated in a zone, not where queries are resolved. Duplicating data locally would involve maintaining copies of zone data (as in a secondary or master-slave setup), not forwarding. Zone transfers to secondary servers describe replication between masters and slaves, not forwarding queries to an external resolver.