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
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
//! The NS record data type.
use Ordering;
use crate;
use crateCanonicalName;
use crateParseMessageBytes;
use crate;
use crate;
//----------- Ns -------------------------------------------------------------
/// The authoritative name server for this domain.
///
/// An [`Ns`] record indicates that a domain name is the apex of a DNS zone,
/// and it specifies (the domain name of) the name server that queries about
/// the domain name (and its descendants) should be sent to. A domain name
/// can be associated with multiple name servers (using multiple [`Ns`]
/// records).
///
/// DNS is designed around the concept of delegating responsibility for domain
/// names. If a name server responds to a query with an empty answer section,
/// but with [`Ns`] records in the authority section, it is claiming to not be
/// the authoritative source of information about the queried domain name;
/// the [`Ns`] records specify name servers to whom that authority has been
/// delegated.
///
/// While [`Ns`] records are typically served by a name server to indicate a
/// zone cut, that name server is not authoritative for the record; the [`Ns`]
/// record belongs to the delegated zone and the delegated name server(s).
///
/// [`Ns`] is specified by [RFC 1035, section 3.3.11].
///
/// [RFC 1035, section 3.3.11]: https://datatracker.ietf.org/doc/html/rfc1035#section-3.3.11
///
/// ## Wire format
///
/// The wire format of an [`Ns`] record is simply the domain name of the name
/// server. This domain name may be compressed in DNS messages.
///
/// ## Usage
///
/// Because [`Ns`] is a record data type, it is usually handled within an enum
/// like [`RecordData`]. This section describes how to use it independently
/// (or when building new record data from scratch).
///
/// [`RecordData`]: crate::new::rdata::RecordData
///
/// In order to build an [`Ns`], it's first important to choose a domain name
/// type. For short-term usage (where the [`Ns`] is a local variable), it is
/// common to pick [`RevNameBuf`]. If the [`Ns`] will be placed on the heap,
/// <code>Box<[`RevName`]></code> will be more efficient.
///
/// [`RevName`]: crate::new::base::name::RevName
/// [`RevNameBuf`]: crate::new::base::name::RevNameBuf
///
/// The primary way to build a new [`Ns`] is to construct each field manually.
/// To parse an [`Ns`] from a DNS message, use [`ParseMessageBytes`]. In case
/// the input bytes don't use name compression, [`ParseBytes`] can be used.
///
/// ```
/// # use domain::new::base::name::{Name, RevNameBuf};
/// # use domain::new::base::wire::{BuildBytes, ParseBytes, ParseBytesZC};
/// # use domain::new::rdata::Ns;
/// #
/// // Build an 'Ns' manually:
/// let manual: Ns<RevNameBuf> = Ns {
/// server: "example.org".parse().unwrap(),
/// };
///
/// // Its wire format serialization looks like:
/// let bytes = b"\x07example\x03org\x00";
/// # let mut buffer = [0u8; 13];
/// # manual.build_bytes(&mut buffer).unwrap();
/// # assert_eq!(*bytes, buffer);
///
/// // Parse an 'Ns' from the wire format, without name decompression:
/// let from_wire: Ns<RevNameBuf> = Ns::parse_bytes(bytes).unwrap();
/// # assert_eq!(manual, from_wire);
///
/// // See 'ParseMessageBytes' for parsing with name decompression.
/// ```
///
/// Since [`Ns`] is a sized type, and it implements [`Copy`] and [`Clone`],
/// it's straightforward to handle and move around. However, this depends on
/// the domain name type. It can be changed using [`Ns::map_name()`] and
/// [`Ns::map_name_by_ref()`].
///
/// For debugging, [`Ns`] can be formatted using [`fmt::Debug`].
///
/// [`fmt::Debug`]: core::fmt::Debug
///
/// To serialize an [`Ns`] in the wire format, use [`BuildInMessage`] (which
/// supports name compression). If name compression is not desired, use
/// [`BuildBytes`].
//--- Interaction
//--- Canonical operations
//--- Parsing from DNS messages
//--- Building into DNS messages
//--- Parsing record data