1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
use ;
use ;
/// [RFC 2782, DNS SRV RR, February 2000](https://tools.ietf.org/html/rfc2782)
///
/// ```text
/// Introductory example
///
/// If a SRV-cognizant LDAP client wants to discover a LDAP server that
/// supports TCP protocol and provides LDAP service for the domain
/// example.com., it does a lookup of
///
/// _ldap._tcp.example.com
///
/// as described in [ARM]. The example zone file near the end of this
/// memo contains answering RRs for an SRV query.
///
/// Note: LDAP is chosen as an example for illustrative purposes only,
/// and the LDAP examples used in this document should not be considered
/// a definitive statement on the recommended way for LDAP to use SRV
/// records. As described in the earlier applicability section, consult
/// the appropriate LDAP documents for the recommended procedures.
///
/// The format of the SRV RR
///
/// Here is the format of the SRV RR, whose DNS type code is 33:
///
/// _Service._Proto.Name TTL Class SRV Priority Weight Port Target
///
/// (There is an example near the end of this document.)
///
/// Service
/// The symbolic name of the desired service, as defined in Assigned
/// Numbers [STD 2] or locally. An underscore (_) is prepended to
/// the service identifier to avoid collisions with DNS labels that
/// occur in nature.
///
/// Some widely used services, notably POP, don't have a single
/// universal name. If Assigned Numbers names the service
/// indicated, that name is the only name which is legal for SRV
/// lookups. The Service is case insensitive.
///
/// Proto
/// The symbolic name of the desired protocol, with an underscore
/// (_) prepended to prevent collisions with DNS labels that occur
/// in nature. _TCP and _UDP are at present the most useful values
/// for this field, though any name defined by Assigned Numbers or
/// locally may be used (as for Service). The Proto is case
/// insensitive.
///
/// Name
/// The domain this RR refers to. The SRV RR is unique in that the
/// name one searches for is not this name; the example near the end
/// shows this clearly.
///
/// TTL
/// Standard DNS meaning [RFC 1035].
///
/// Class
/// Standard DNS meaning [RFC 1035]. SRV records occur in the IN
/// Class.
///
/// ```