Soru

Zorluk: Çok zorDNS Infrastructure and Record Types

A network architect is implementing specialized DNS configurations across an enterprise hybrid cloud environment. Match each operational requirement on the left with its corresponding DNS resource record type on the right.

  • Specifying transport protocol, service port number, priority, and weight for dynamic service locationSRV Record
  • Publishing public key cryptographic signatures and policy details to validate email sender domain authenticityTXT Record
  • Mapping an IP address back to a canonical fully qualified domain name for reverse resolution auditingPTR Record
  • Establishing domain zone authority, primary master server, administrator email, and zone transfer timersSOA Record

Cevap

Dynamic service discovery with port/protocol parameters maps to SRV Record; email security and cryptographic key publishing maps to TXT Record; IP address to FQDN reverse lookups map to PTR Record; zone authority and synchronization timing metadata map to SOA Record.
Each requirement aligns with the specific functional specification of the corresponding DNS record type: SRV enables port/protocol service discovery, TXT provides text key storage for DKIM/SPF, PTR provides IP-to-FQDN reverse resolution, and SOA governs zone authority and replication timers.

Adım Adım Çözüm

1
Analyze service location requirements
Dynamic location of network services requiring specific port numbers, transport protocols, priorities, and weights strictly mandates an SRV record.
Standard host records (A/AAAA/CNAME) do not store protocol or port configuration details.
2
Analyze email security authentication specifications
Storing public keys (DKIM) and SPF policy statements requires a TXT record.
TXT records provide text payload storage designed for security authentication policies without requiring dedicated custom record types.
3
Analyze reverse IP lookup requirements
Mapping an IP address back to its associated FQDN requires a PTR record.
PTR records populate the reverse lookup zone structure (in-addr.arpa / ip6.arpa) specifically used for security validation and logging.
4
Analyze zone administrative parameter requirements
Defining primary name server authority, contact email, serial number, and secondary server refresh timers mandates an SOA record.
Every valid DNS zone must contain exactly one SOA record at the apex to govern zone replication and administrative parameters.

Anahtar Kavram

DNS Infrastructure and Resource Record Functionality
Tahmini Süre:2m 0s
Bu soruyu puanla