Custom DNS records used when an application needs the location of a specific service are called what records?

Custom DNS records used when an application needs the location of a specific service are called what records?

• A. PTR Records
• B. AAAA Records
• C. A Records
• D. SRV Records

Answer: (D)

SRV records provide a way for applications to locate a specific service within a domain by describing the host and port where that service runs. Each SRV entry includes the service name, the protocol (TCP or UDP), the domain, the target host, the port, and priority/weight for failover and load balancing. When a client needs a service, it looks up the SRV record named like _service._proto.name and then connects to the target at the specified port, preferring lower-priority entries and using weight to distribute among equals. This is different from A records (which map a hostname to an IPv4 address), AAAA records (IPv6 addresses), or PTR records (reverse mappings from IP to name). In many services and domain setups, SRV records are used for discovering where a particular service resides (for example, LDAP, SIP, Kerberos, or other application services), and you would configure them in DNS with the service, protocol, domain, target, port, and the priority/weight.

SRV records provide a way for applications to locate a specific service within a domain by describing the host and port where that service runs. Each SRV entry includes the service name, the protocol (TCP or UDP), the domain, the target host, the port, and priority/weight for failover and load balancing. When a client needs a service, it looks up the SRV record named like _service._proto.name and then connects to the target at the specified port, preferring lower-priority entries and using weight to distribute among equals.

This is different from A records (which map a hostname to an IPv4 address), AAAA records (IPv6 addresses), or PTR records (reverse mappings from IP to name). In many services and domain setups, SRV records are used for discovering where a particular service resides (for example, LDAP, SIP, Kerberos, or other application services), and you would configure them in DNS with the service, protocol, domain, target, port, and the priority/weight.