In DNS, what defines the scope and authority of a portion of the namespace?

In DNS, what defines the scope and authority of a portion of the namespace?

• A. A zone, which is managed by a particular DNS server.
• B. A region, defined by the network administrator's location.
• C. A file type, indicating how DNS records are stored.
• D. A TTL value that applies to all records in a domain.

Answer: (A)

In DNS, the scope and authority of a portion of the namespace is defined by a zone. A zone is the portion of the DNS namespace for which a specific set of DNS servers is authoritative. The boundary of that zone is established through delegation from the parent zone to the zone’s authoritative servers (via NS records), and the zone has its own zone file containing resource records such as SOA, NS, A/AAAA, MX, and more. This setup determines both what names are covered (the scope) and which servers answer authoritatively for those names (the authority). Other options don’t establish scope or control: region by location isn’t how DNS delegates responsibility, file type isn’t a mechanism for namespace scope, and TTL is just a caching parameter for records, not the boundary of authority.

In DNS, the scope and authority of a portion of the namespace is defined by a zone. A zone is the portion of the DNS namespace for which a specific set of DNS servers is authoritative. The boundary of that zone is established through delegation from the parent zone to the zone’s authoritative servers (via NS records), and the zone has its own zone file containing resource records such as SOA, NS, A/AAAA, MX, and more. This setup determines both what names are covered (the scope) and which servers answer authoritatively for those names (the authority). Other options don’t establish scope or control: region by location isn’t how DNS delegates responsibility, file type isn’t a mechanism for namespace scope, and TTL is just a caching parameter for records, not the boundary of authority.