What DNS record is required for MRA to function with TLS?

Prepare for the Cisco CLCOR 350-801 exam with detailed flashcards and multiple choice questions. Understand core technologies, and explore hints and explanations for a comprehensive learning experience. Equip yourself for success!

Multiple Choice

What DNS record is required for MRA to function with TLS?

Explanation:
When MRA uses TLS, clients locate the edge service through a DNS SRV record that specifies the service name and the protocol. The SRV record format is _service._proto, so for the collab-edge service over TLS you publish a record named _collab-edge._tls. This tells the client to contact the edge using TLS (for SIP signaling) at the resolved host and port. The other formats don’t fit SRV naming rules or indicate a non-TLS connection (_tcp), or misuse the syntax (omitting the leading underscore or using a dot instead of the required structure). That’s why the TLS-specific SRV entry _collab-edge._tls is the correct one for TLS-enabled MRA.

When MRA uses TLS, clients locate the edge service through a DNS SRV record that specifies the service name and the protocol. The SRV record format is _service._proto, so for the collab-edge service over TLS you publish a record named _collab-edge._tls. This tells the client to contact the edge using TLS (for SIP signaling) at the resolved host and port.

The other formats don’t fit SRV naming rules or indicate a non-TLS connection (_tcp), or misuse the syntax (omitting the leading underscore or using a dot instead of the required structure). That’s why the TLS-specific SRV entry _collab-edge._tls is the correct one for TLS-enabled MRA.

More Multiple Choice Questions
Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy