{"id":8973,"date":"2026-05-30T00:46:03","date_gmt":"2026-05-29T22:46:03","guid":{"rendered":"https:\/\/mybox.com\/help\/?post_type=manual_kb&#038;p=8973"},"modified":"2026-06-08T10:35:48","modified_gmt":"2026-06-08T08:35:48","slug":"intelegerea-inregistrarii-srv","status":"publish","type":"manual_kb","link":"https:\/\/mybox.com\/help\/ro\/knowledgebase\/understanding-the-srv-record\/","title":{"rendered":"\u00cen\u021belegerea \u00eenregistr\u0103rii SRV"},"content":{"rendered":"<div class=\"translation-block translation-block-merged\">\n<p class=\"wp-block-paragraph\">In network administration, directory service architecture, and systems engineering, resolving a domain name to a simple IP address is often insufficient for complex multi-platform communications. An <strong>SRV record<\/strong> (Service Location Record) is a specialized Domain Name System (DNS) resource record designed explicitly for <strong>service discovery<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Unlike a standard A or AAAA record\u2014which merely maps a hostname to a physical network destination\u2014the SRV record specifies the exact location, protocol, port number, and priority parameters of specific network services available within a target domain zone. This enables client applications to dynamically discover backend servers running enterprise applications such as Unified Communications (SIP), instant messaging (XMPP), and directory mappings (Active Directory \/ LDAP) without hardcoding explicit network topology maps.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/understanding-the-srv-record\/#Structural_Breakdown_of_an_SRV_Record\" >Structural Breakdown of an SRV Record<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/understanding-the-srv-record\/#Operational_Analysis_of_a_Production_Example\" >Operational Analysis of a Production Example<\/a><\/li><\/ul><\/nav><\/div>\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Structural_Breakdown_of_an_SRV_Record\"><\/span>Structural Breakdown of an SRV Record<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<\/div>\n\n<div id=\"mybox-1802688390\" class=\"mybox-content mybox-entity-placement\"><div class=\"early-access-banner-inpost\">\r\n  <div class=\"banner-left-inpost\">\r\n    <div class=\"icon-box-inpost\">\r\n      <img decoding=\"async\" src=\"https:\/\/mybox.com\/help\/wp-content\/uploads\/2026\/02\/square-info-icon.svg\" alt=\"Info\">\r\n    <\/div>\r\n    <div class=\"text-box-inpost\">\r\n      <span class=\"label-inpost\"><span class=\"translation-block translation-block-banner-text\">Acces timpuriu<\/span><\/span>\r\n      <h4><span class=\"translation-block translation-block-banner-text\">Mai ave\u021bi nevoie de ajutor?<\/span><\/h4>\r\n      <p><span class=\"translation-block translation-block-banner-text\">Contacta\u021bi echipa noastr\u0103 de servicii pentru clien\u021bi.<\/span><\/p>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <div class=\"banner-right-inpost\">\r\n    <a href=\"https:\/\/panel.mybox.com\/helpdesk2\/v\/list\/\" class=\"banner-button-inpost\"><span class=\"translation-block translation-block-banner-text\">Trimite mesaj<\/span><\/a>\r\n  <\/div>\r\n<\/div><\/div>\n\n<div class=\"translation-block translation-block-merged\"><p class=\"wp-block-paragraph\">An SRV record relies on a strict syntax format to deliver multi-layered communication parameters within a single DNS query. The record configuration is split across two primary segments: the <strong>Name \/ Service Key Descriptor<\/strong> and the <strong>Target Value Matrix<\/strong>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">1. The Name \/ Service Key Descriptor Field<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">This string acts as the explicit query key and must be formatted using a precise, standardized structure that informs the requesting application exactly which service and transport protocol are being targeted:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Service Identifier:<\/strong> Must begin with an underscore (<code>_<\/code>) followed by the symbolic name of the targeted service (e.g., <code>_sip<\/code> for Session Initiation Protocol or <code>_xmpp-server<\/code>).<\/li>\n\n\n\n<li><strong>Protocol Identifier:<\/strong> Follows the service key, beginning with an underscore (<code>_<\/code>) to define the transport layer protocol (e.g., <code>_tcp<\/code>, <code>_udp<\/code>, or <code>_tls<\/code>).<\/li>\n\n\n\n<li><strong>Domain Origin:<\/strong> Concludes with the specific zone name or top-level apex domain being mapped.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">2. The Target Value Matrix<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">The value payload returns a composite array containing critical structural details required to establish an immediate network handshake:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Priority Configuration:<\/strong> A weight indicator used to balance connection hierarchies across multiple servers. Lower values receive priority routing.<\/li>\n\n\n\n<li><strong>Weight Variable:<\/strong> A load-balancing parameter used to distribute connection traffic proportionally among multiple target servers with identical priority scores.<\/li>\n\n\n\n<li><strong>Service Port Number:<\/strong> The exact physical or logical port on the target host where the application service listens for incoming connections (e.g., port <code>443<\/code> for secure web sockets or <code>5061<\/code> for encrypted SIP).<\/li>\n\n\n\n<li><strong>Target Host Domain Name:<\/strong> The fully qualified domain name (FQDN) of the machine providing the active service. This host must possess a valid A or AAAA mapping record within the global DNS tree.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Operational_Analysis_of_a_Production_Example\"><\/span>Operational Analysis of a Production Example<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review the following enterprise configuration row designed to route secure voice and video communication traffic through cloud servers:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">DNS Zone file<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>_sip._tls.yourdomain.com. 900 IN SRV 1 443 sipdir.online.lync.com.\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When an enterprise communication client queries this zone record, the infrastructure parses the string piece by piece:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><code>_sip<\/code><\/strong>  Identifies the Session Initiation Protocol communication framework.<\/li>\n\n\n\n<li><strong><code>_tls<\/code><\/strong>  Mandates that the connection must be wrapped inside a Transport Layer Security (TLS) cryptographic encryption tunnel.<\/li>\n\n\n\n<li><strong><code>yourdomain.com.<\/code><\/strong>  Specifies the core corporate domain zone being managed.<\/li>\n\n\n\n<li><strong><code>900<\/code><\/strong>  Represents the Time-To-Live (TTL) constant in seconds, dictating how long downstream edge servers can cache this routing path before re-polling the master nameserver.<\/li>\n\n\n\n<li><strong><code>1<\/code><\/strong>  Sets the connection weight factor for balancing server cluster distributions.<\/li>\n\n\n\n<li><strong><code>443<\/code><\/strong>  Directs the incoming application traffic directly to logical port 443 on the receiver.<\/li>\n\n\n\n<li><strong><code>sipdir.online.lync.com.<\/code><\/strong>  Establishes the exact external cloud server address responsible for processing the incoming handshake.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[62],"manual_kb_tag":[712,1678,6262,6263,6264,6265,6266,6267,6268,6269],"class_list":["post-8973","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-domain-management-in-panel","manual_kb_tag-domain-name-system","manual_kb_tag-srv-record","manual_kb_tag-service-location-record","manual_kb_tag-dns-srv","manual_kb_tag-service-discovery","manual_kb_tag-dns-resource-record","manual_kb_tag-service-record","manual_kb_tag-service-identifier","manual_kb_tag-protocol-identifier","manual_kb_tag-target-value-matrix"],"_links":{"self":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/8973","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":2,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/8973\/revisions"}],"predecessor-version":[{"id":8974,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/8973\/revisions\/8974"}],"wp:attachment":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/media?parent=8973"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manualknowledgebasecat?post=8973"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb_tag?post=8973"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}