No. | Title |
| Server Test |
| RFC 1034: Domain Concepts and Facilities |
| 3. DOMAIN NAME SPACE AND RESOURCE RECORDS |
| 3.1. Name space specifications and terminology |
1 | Label length |
2 | Case-insensitive manner |
3 | Domain Name length |
| 3.5. Preferred name syntax |
4 | Rule for label |
| 3.6. Resource Records |
| NAME |
| NAME (owner) is tested at TYPE test. |
| TYPE |
5 | A type |
6 | CNAME type |
7 | HINFO type |
8 | MX type |
9 | NS type |
10 | PTR type |
11 | SOA type |
| CLASS |
12 | IN class |
| CH class |
| TTL |
| RDATA |
13 | A resource data (IN class) |
| A resource data (CH class) |
14 | CNAME resource data |
15 | HINFO resource data |
16 | MX resource data |
17 | NS resource data |
18 | PTR resource data |
19 | SOA resource data |
| Caching |
20 | Zero TTL prohibits caching |
| 3.6.2. Aliases and canonical names |
21 | CNAME RR is present at a node, no other data should be present |
22 | * query should return just the CNAME |
| 3.7. Queries |
23 | Carried in TCP |
24 | Standard message format |
25 | Opcode (standard query) |
| Opcode (status query) |
| 3.7.1. Standard queries |
26 | Question section format |
| QTYPE |
27 | * type for query |
28 | * type for response |
| QCLASS |
29 | * class (the requestor is seeking data from more than one class) |
| 3.7.2. Inverse queries (Obsoleted by RFC3425) |
| 4. NAME SERVERS |
| 4.1. Introduction |
30 | The name server returns data w/ Authoritative Answer (AA) or not. |
| 4.2. How the database is divided into zone |
| 4.3. Name server internals |
| 4.3.1. Queries and responses |
31 | No-recursive queries |
32 | Name server acts in the role of a resolver |
| Recursive mode |
33 | Recursion Available (RA) bit is set or cleared by a name server in all responses |
34 | Recursion desired (RD) |
| Recursion is available case |
35 | The answer with CNAME to the query. |
36 | A name error indicating that the name does not exist. |
37 | A temporary error indication. |
| Recursion is not available case |
38 | An authoritative name error indicating that the name does not exist. |
| A temporary error indication |
| (Tested at 4.3.1. No-recursive queries) |
| 4.3.2. Algorithm |
| A. And the whole of QNAME is matched |
39 | The data at the node is a CNAME, and QTYPE doesn't match CNAME case. |
40 | The data at the node is except the above-mentioned. |
| B. A match take QNAME out of the authoritative data, QNAME has a referral. |
41 | QNAME is found in the cache. |
42 | QNAME is not found in the cache. |
| C. At some label, a match is impossible. |
43 | The "*" label does not exist, the name is original. |
| The "*" label does exist. |
| (Tested at 4.3.3. Wildcards) |
| Recursion service is available and requested via the RD bit in the query. |
| (Tested at 5.3.3. Algorithm.) |
| 4.3.3. Wildcards |
44 | Caching wildcards queries |
45 | Wildcards is not applied case |
| 4.3.4. Negative response caching (Optional) |
| 4.3.5. Zone maintenance and transfers |
46 | Zone maintenance and transfers |
47 | Zone transfer is not completed case |
48 | Distribute zone |
| 5. RESOLVERS |
| 5.1 Introduction |
| 5.2. Client-resolver interface |
| 5.2.1. Typical functions |
49 | Returning of answer |
50 | Returning of name error |
51 | Returning of data not found error |
| 5.2.2. Aliases |
52 | Encounters a CNAME |
53 | Multiple levels of aliases should be avoided, but should not be signaled as an error |
| 5.2.3. Temporary failures |
| 5.3. Resolver internals |
| 5.3.1. Stub resolvers |
| 5.3.2. Resources |
54 | Cache data vs authoritative data |
| 5.3.3. Algorithm |
55 | Answer in local information |
56 | Sending query to server |
57 | Analyze the response (delegation) |
58 | Analyze the response (caching delegation) |
59 | Analyze the response (caching CNAME) |
60 | Analyze the response (answer is invalid) |
61 | Analyze the response (delegation is invalid) |
| RFC 1035: Domain Implementation and Specification |
| 2.3.1. Preferred name syntax |
| 2.3.2. Data Transmission Order |
62 | Order of transmission of octets and bits |
| 2.3.3. Character Case |
| 2.3.4. Size limits |
| 3. DOMAIN NAME SPACE AND RR DEFINITIONS |
| 3.1. Name space definitions |
63 | Label format |
64 | Label of root |
| 3.2. RR definitions |
| 3.2.1. Format |
| 3.2.2. TYPE values |
65 | WKS type |
66 | TXT type |
| 3.3. Standard RRs |
| (Tested at 3.2.2. TYPE values) |
| 3.3.14. TXT RDATA format |
67 | TXT resource data |
| 3.4. Internet specific RRs |
| 3.4.1. A RDATA format |
| 3.4.2. WKS RDATA format |
68 | WKS resource data |
| 3.5. IN-ADDR.ARPA domain |
| (Tested at 3.3.12. PTR RDATA format) |
| 4. MESSAGES |
| 4.1. Format |
| 4.1.1. Header section format |
69 | Header section format (query) |
70 | Header section format (response) |
71 | Format error (RCODE=1) |
72 | Server failure (RCODE=2) |
73 | Not Implemented (RCODE=4) |
74 | Refused (RCODE=5) for query |
75 | Refused (RCODE=5) for zone transfer |
| 4.1.2. Question section format |
| 4.1.3. Resource record format |
76 | Answer section format |
77 | Authority section format |
78 | Additional section format |
| 4.1.4. Message compression |
79 | Message compression |
80 | Message compression format |
| 4.2. Transport |
| 4.2.1. UDP usage |
81 | Messages carried by UDP are restricted to 512 bytes |
82 | Not depend on response in order |
| 4.2.2. TCP usage |
83 | TCP connection management check |
| 6. NAME SERVER IMPLEMENTATION |
| 6.1. Architecture |
| 6.1.1. Control |
84 | Accept UDP while server waits TCP connecting |
| 6.1.2. Database |
| 6.1.3. Time |
| 6.2. Standard query processing |
85 | Processing queries with QCLASS=* |
86 | Duplicate answer is omitted from the additional section |
87 | Authority section guarantee uniqueness of the answer |
| 6.3. Zone refresh and reload processing |
| 6.4. Inverse queries (Optional) |
| Obsoleted by RFC3425 |
| 7. RESOLVER IMPLEMENTATION |
| 7.1. Transforming a user request into a query |
| 7.2. Sending the queries |
| 7.3. Processing response |
88 | Invalid response (query is returned) |
89 | Invalid response (RRs are incorrectly formatted) |
90 | Invalid response (long TTL) (optional) |
91 | Invalid response (ID does not match) |
92 | Invalid response (invalid question section) |
| 7.4. Using the cache |
93 | Caching several RRs of same type |
| RFC 1123: Requirements for Internet Hosts -- Application and Support |
| 6. SUPPORT SERVICES |
| 6.1. DOMAIN NAME TRANSACTION |
| 6.1.1. INTRODUCTION |
| 6.1.2. PROTOCOL WALK-THROUGH |
| 6.1.2.1. Resource Records with Zero TTL: RFC-1035 Section 3.2.1 |
| Resource Records with Zero. |
| 6.1.2.2. QCLASS Values: RFC-1035 Section 3.2.5 |
| 6.1.2.3. Unused Fields: RFC-1035 Section 4.1.1 |
94 | Unused fields in a query |
| Unused fields in a query. |
| 6.1.2.4. Compression: RFC-1035 Section 4.1.4 |
| Message compression. |
| 6.1.2.5. Misusing Configuration Info: RFC-1035 Section 6.1.2 |
| 6.1.3. SPECIFC ISSUES |
| 6.1.3.1 Resolver Implementation |
95 | Multiplex concurrent requests |
| (A) Full-Service Resolver |
96 | Time out of cache |
| (B) Stub Resolver |
| 6.1.3.2 Transport Protocols |
97 | Not refuse TCP query (query) |
98 | Not refuse TCP query (response) |
99 | Caching truncated responses |
100 | Processing UDP query while zone transfering |
101 | Broadcast/Multicast query |
102 | Server ignores queries via broadcast or multicast address |
| 6.1.3.3 Efficient Resource Usage |
103 | Retransmission control |
104 | Caching of temporary failure |
| 6.1.3.4 Multihomed Hosts |
| 6.1.3.5 Extensibility |
| 6.1.3.6 Status of RR Types |
| Server loads zone files without obsolete RR types |
| 6.1.3.7 Robustness |
105 | Continue to provide service |
| 6.1.3.8 Local Host Table |
| 6.1.4. DNS USER INTERFACE |
| 6.1.4.1 DNS Administration |
| 6.1.4.2 DNS User Interface |
| 6.1.4.3 Interface Abbreviation Facilities |
| Caching of negative response. |
| (Tested at 6.1.3.3. Efficient Resource Usage) |
| RFC 1995: Incremental Zone Transfer in DNS |
| 2. Brief Description of the Protocol |
106 | An IXFR client sends an IXFR message |
107 | An IXFR client receive an IXFR response with the full zone transfer message |
108 | An IXFR client receive an IXFR response with the incremental message (add) |
109 | An IXFR client receive an IXFR response with the incremental message (remove) |
110 | An IXFR client receive an IXFR response with the incremental message (change) |
111 | An IXFR client receive an IXFR response with the incremental message (remove/add/change) |
112 | An IXFR client tries an AXFR, if the query type is not recognized by the server. |
113 | An IXFR client tries to use TCP, if the reply does not fit in a single DNS packet. |
114 | An IXFR server transmits an IXFR response with the incremental message (add). |
115 | An IXFR server transmits an IXFR response with the incremental message (remove). |
116 | An IXFR server transmits an IXFR response with the incremental message (change). |
117 | An IXFR server received an IXFR request with an older version number. |
118 | An IXFR server received an IXFR request with a same version number. |
119 | An IXFR server received an IXFR request with a newer version number. |
120 | An IXFR server sends a single SOA record of the server's current version, if the UDP reply does not fit in a single DNS packet. |
| 4. Response Format |
| 5. Purging Strategy |
| 6. Optional Condensation of Multiple Versions |
121 | An IXFR client receive an IXFR response with the condensed incremental message |
| RFC 1996: DNS NOTIFY |
| 1. Rationale and Scope |
| 1.1 |
| 1.2 The DNS NOTIFY transaction allows master servers to inform salve servers when the zone has changed |
122 | An IXFR client sends an IXFR message through NOTIFY mechanism |
| 3. NOTIFY Message |
| 3.1 |
| 3.2 |
123 | A master ignores message if fields are not to be filled with binary zero (0). |
124 | A slave ignores message if fields are not to be filled with binary zero (0). |
| 3.3 |
125 | Slave server sends a NOTIFY response back to the NOTIFY request's source. |
| 3.4 |
126 | Primary Master sends a NOTIFY query |
| 3.5 |
| TCP |
127 | A master continue to offer name service during the NOTIFY transaction. |
128 | A slave sends a once a NOTIFY request until timeout |
| 3.6 |
| UDP |
129 | A master periodically sends a NOTIFY request to a slave until timeout. |
130 | A master periodically sends a NOTIFY request to a slave until ICMP message indicating. |
131 | A master periodically sends a NOTIFY request to a slave until a NOTIFY response is received. |
| 3.7 |
132 | ANCOUNT=0 and the answer section differs from the slave's local data |
133 | ANCOUNT>0 and the answer section differs from the slave's local data |
| 3.8 |
| 3.9 |
| 3.10 |
134 | A slave ignores a NOTIFY request from a unknown master for the zone. |
| 3.11 |
| 3.12 |
135 | A master receives a NOTIMP (unimplemented feature error) message. |
| RFC 2181: Clarifications to the DNS Specification |
| 4.1. UDP Source Address Selection |
136 | UDP Source Address Selection |
| 4.2. Port Number Selection |
137 | Port number selection |
| 5. Resource Record Sets |
| 5.1 Sending RRs from an RRSet |
138 | Sending RRs from an RRSet |
| 5.2. TTLs of RRs in an RRSet |
139 | TTLs of all RRs in an RRSet must be the same |
140 | Treat Differing TTLs from non-authoritative source as error |
141 | Differing TTLs from non-authoritative source |
142 | Differing TTLs from authoritative source |
| 5.3. DNSSEC Special Cases |
| 5.4. Receiving RRSets |
143 | Never merge RRs from response with RRs in cache |
144 | Update the TTL in cache with the TTL of the received answer |
| 5.4.1. Ranking data |
145 | Server makes a judgment by the reliability of data (Data from the answer section of an authoritative answer v.s. Data from the authority section of an authoritative answer) |
146 | Server makes a judgment by the reliability of data (Data from the answer section of an authoritative answer v.s. Non-authoritative data from the answer section of an authoritative answer) |
147 | Server makes a judgment by the reliability of data (Data from the answer section of an authoritative answer v.s. Data from the additional section of an authoritative answer) |
148 | Server makes a judgment by the reliability of data (Data from the authority section of an authoritative answer v.s. Data from the answer section of a non-authoritative answer) |
149 | Server makes a judgment by the reliability of data (Data from the authority section of an authoritative answer v.s. Data from the authority section of a non-authoritative answer) |
150 | Server makes a judgment by the reliability of data (Data from the answer section of an non-authoritative answer v.s. Data from the additional section of a authoritative answer) |
151 | Least reliability data should not return as answer (Additional section from an authoritative answer) |
152 | Least reliability data should not return as answer (Authority section from a non-authoritative answer) |
153 | Least reliability data should not return as answer (Additional section from a non-authoritative answer) |
| 5.5. Sending RRSets (reprise) |
154 | A Resource Record Set should only be included once in any DNS reply |
| 6. Zone Cuts |
| 6.1. Zone Authority |
155 | A server for a zone should not return authoritative answer for queries related to names in another name |
| 6.2. DNSSEC issues |
| 7. SOA RRs |
| 7.1. Placement of SOA RRs in authoritative answers |
156 | SOA records are to be placed in the authority section |
| 8. Time to Live (TTL) |
157 | Time to live |
158 | Received with the most significant bit is set |
| 9. The TC (truncated) header bit |
159 | Case of the TC header bit is not set |
| 10. Naming issues |
| 10.1. CNAME resource records |
| 10.2. PTR records |
160 | RRSet for PTR record |
| RFC 2308: DNS NCACHE |
| 2. Negative Response |
| 2.1. Name Error |
161 | Name error (RCODE=NXDOMAIN) |
| 2.1.1. Special Handling of Name Error |
| 2.2. No Data |
162 | No Data |
| 3. Negative Answers from Authoritative Servers |
| (Related to DNSSEC) |
| 4. SOA Minimum Field |
| 5. Caching Negative Answers |
163 | TTL expired negative cache MUST NOT be used (NXDOMAIN) |
164 | TTL expired negative cache MUST NOT be used (NODATA) |
165 | Caching of name error (NXDOMAIN) |
166 | Caching of name error (NXDOMAIN) for query tuple |
167 | Caching of no data (NODATA) |
168 | Caching of no data (NODATA) for query tuple |
| NXT record is stored |
| (Related to DNSSEC) |
| NXT record has the same owner name |
| (Related to DNSSEC) |
169 | Negative responses without SOA records |
| 6. Negative answers from the cache |
| NXT record is added to the authority section |
| (Related to DNSSEC) |
| SIG record is added to the authority section |
| (Related to DNSSEC) |
170 | Negative answer should have an implicit referral built into the answer (NXDOMAIN) |
171 | Negative answer should have an implicit referral built into the answer (NODATA) |
| 7. Other Negative Responses |
| 7.1. Server Failure (OPTIONAL) |
172 | Resolver cache a server failure response |
173 | Resolver cache a server failure response for query tuple |
174 | Limit of time (5 minutes) for caching (Server Failure) |
| 7.2. Dead / Unreachable Server (OPTIONAL) |
175 | Caching of dead server indication |
176 | Caching of dead server indication for query tuple |
177 | Limit of time (5 minutes) for caching (Dead/Unreachable Server) |
| 8. Changes from RFC1034 |
| Resolver cache a server failure response |
| (Tested at 7.1. Server Failure) |
178 | Caching of SOA record |
| Caching of name error (NXDOMAIN) |
| (Tested at 5. Caching Negative Answers) |
| Caching of no data (NODATA) |
| (Tested at 5. Caching Negative Answers) |
| Negative answers from the cache |
| (Tested at 6. Negative answers from the cache) |
| $TTL directive define default TTL |
| (Tested at 4. SOA Minimum Field) |
| RFC 2671: Extension Mechanisms for DNS (EDNS0) |
| 4. OPT pseudo-RR |
179 | OPT pseudo-RR |
180 | OPT pseudo-RR (recursive) |
| 5. Transport Consideration |
| 5.1. |
181 | The presence of an OPT pseuduo-RR |
| 5.2. |
182 | The lack of an OPT pseuduo-RR |
| 5.3. |
183 | Responders don't understand OPT RR |
| RFC 2782: DNS SRV RR |
184 | SRV type |
185 | SRV resource record |
| RFC 3401: DDDS - The Comprehensive DDDS RFC 3402: DDDS - The Algorithm RFC 3403: DDDS DNS Database RFC 3404: DDDS Based URI Resolution RFC 3405: URI.ARPA Assignment Procedures |
| RFC3401 Part One: The Comprehensive DDDS |
| RFC3402 Part Two: The Algorithm |
| RFC3403 Part Three: The Domain Name System (DNS) Database |
| 4. NAPTR RR Format |
| 4.1 Packet Format |
186 | NAPTR type |
187 | Caching NAPTR resource record |
188 | NAPTR resource record |
189 | Multiple NAPTR resource records with several ORDER and PREFERENCE |
190 | Invalid NAPTR resource record format |
| RFC3404 Part Four: The Uniform Resource Identifiers (URI) Resolution Application |
| 4. The URI and URN Resolution Application Specifications |
| 4.3 Flags |
191 | Flag in NAPTR resource record (empty) |
192 | Flag in NAPTR resource record (P flag) |
193 | Flag in NAPTR resource record (A flag) |
194 | Flag in NAPTR resource record (S flag) |
195 | Multiple Flags in NAPTR resource record (X,Y flag) |
| 4.5 Valid Databases |
196 | Additional Section Processing for NAPTR resource record (A flag) |
197 | Additional Section Processing for NAPTR resource record (S flag) |
| RFC3405 Part Five: URI.ARPA Assignment Procedures |
| RFC 3425: Obsoleting IQUERY |
| 3 - Effect on RFC 1035 |
198 | Returning Not Implemented error |
| RFC 3596: DNS Extensions to Support IPv6 |
| 2. New resource record definition and domain |
| 2.1. AAAA record type |
| 2.2. AAAA data format |
| 2.3. AAAA query |
199 | AAAA type |
200 | AAAA resource record |
| 2.4. Textual format of AAAA records |
| 2.5. IP6.ARPA Domain |
201 | PTR type |
202 | PTR resource data |
| Client Test |
| RFC 1034: Domain Concepts and Facilities |
| 3. DOMAIN NAME SPACE AND RESOURCE RECORDS |
| Name syntax |
203 | Label length |
204 | Domain Name length |
205 | Rule for label |
| 3.6. Resource Records |
| type |
206 | A record |
207 | CNAME record |
208 | HINFO record |
209 | MX record |
210 | NS record |
211 | PTR record (A) |
212 | PTR record (AAAA) |
213 | SOA record |
| class |
214 | IN class |
215 | CH class |
| Caching |
216 | Zero TTL prohibits caching |
| 3.7.Queries |
217 | Carried in TCP |
218 | Standard message format |
219 | Opcode (standard query) |
220 | Opcode (status query) |
| 3.7.1. Standard queries |
221 | Question section format |
| QTYPE |
222 | AXFR record |
223 | * record |
| QCLASS |
224 | * class |
| 4.3.1. Queries and responses |
225 | Recursion desired (RD) |
| 4.3.3. Wildcards |
226 | Caching wildcards response |
| 5. RESOLVERS |
| 5.2. Client-resolver interface |
227 | Returning of answer |
228 | Returning of name error |
229 | Returning of data not found error |
| 5.2.2. Aliases |
230 | Encounters a CNAME |
| 5.2.3. Temporary failures |
| 5.3. Resolver internals |
| 5.3.2. Resources |
231 | Cache data vs authoritative data |
| 5.3.3. Algorithm |
232 | Answer in local information |
233 | Sending query to servers |
234 | Analyze the response (delegation) |
235 | Analyze the response (caching delegation) |
236 | Analyze the response (caching CNAME) |
237 | Analyze the response (answer is invalid for recursive) |
238 | Analyze the response (answer is invalid for caching) |
239 | Analyze the response (delegation is invalid) |
| RFC 1035: Domain Implementation and Specification |
| 2.3.2 Data Transmission Order |
240 | Order of transmission of octets and bits |
| 3.1 Name space definitions |
241 | Label format |
242 | Label of root |
| 3.2.1 Format |
| 3.2.2 TYPE values |
243 | MB record |
244 | MG record |
245 | MR record |
246 | NULL record |
247 | WKS record |
248 | MINFO record |
249 | TXT record |
| 3.2.3 QTYPE values |
250 | MAILB record |
| 3.2.4 CLASS values |
251 | HS class |
| 4.1 Format |
252 | Header section format |
| 4.1.4 Message compression |
253 | Message compression |
| 4.2.1 UDP usage |
254 | Not depend on response in order |
| 7.3 UDP Processing responses |
255 | Invalid response (Query is returned) |
256 | Invalid response (RRs are incorrectly formatted) |
257 | Invalid response (Long TTL) (optional) |
258 | Invalid response (ID does not match) |
259 | Invalid response (Invalid question section) |
| 7.4 Using the cache |
260 | Caching several RRs of same type |
| RFC 1123: Requirements for Internet Hosts -- Application and Support |
| 6. SUPPORT SERVICES |
| 6.1 DOMAIN NAME TRANSLATION |
| 6.1.2 PROTOCOL WALK-THROUGH |
| 6.1.2.3 Unused Fields: RFC-1035 Section 4.1.1 |
261 | Unused fields in a query |
| 6.1.3.1 Resolver Implementation |
262 | Multiplex concurrent requests |
| Full-Service Resolver |
263 | Time out of cache |
| 6.1.3.2 Transport Protocols |
264 | Caching truncated responses |
265 | Multicast query |
| 6.1.3.3 Efficient Resource Usage |
266 | Retransmission control |
267 | Caching of temporary failure |
| RFC 2181: Clarifications to the DNS Specification |
| 5.2 TTLs of RRs in an RRSet |
268 | Differing TTLs from non-authoritative source |
269 | Differing TTLs from authoritative source |
| 8. Time to Live (TTL) |
270 | Received with most significant bit is set |
| RFC 2308: DNS NCACHE |
| 5. Caching Negative Answers |
271 | Caching of name error (NXDOMAIN) |
272 | TTL expired negative cache MUST NOT be used (NXDOMAIN) |
273 | Caching of name error (NXDOMAIN) for query tuple |
274 | Caching of no data (NODATA) |
275 | TTL expired negative cache MUST NOT be used (NODATA) |
276 | Caching of no data (NODATA) for query tuple |
277 | Negative responses without SOA records |
| 7.1 Server Failure (OPTIONAL) |
278 | Resolver cache a server failure response |
279 | Resolver cache a server failure response for query tuple |
280 | Limit of time (5 minutes) for caching (Server Failure) |
| 7.2 Dead / Unreachable Server (OPTIONAL) |
281 | Caching of dead server indication |
282 | Caching of dead server indication for query tuple |
283 | Limit of time (5 minutes) for caching (Dead/Unreachable Server) |
| 8 Changes from RFC1034 |
284 | Caching of SOA record |
| RFC 2671: Extension Mechanisms for DNS (EDNS0) |
| 4 - OPT pseudo-RR |
285 | OPT pseudo-RR |
286 | The quantity of OPT pseudo-RRs |
287 | Check OPT RR format |
288 | Check Sender's UDP payload size |
| 5 - Transport Considerations |
289 | Responders don't understand OPT RR |
| RFC 2782: DNS SRV RR |
290 | SRV record |
291 | Returning of answer |
292 | Returning of answer (w/o Additional Data section) |
293 | Priority comparison |
294 | Priority comparison (round-robin) |
295 | Weight comparison |
296 | NXDOMAIN |
| RFC 3401: DDDS - The Comprehensive DDDS RFC 3402: DDDS - The Algorithm RFC 3403: DDDS DNS Database RFC 3404: DDDS Based URI Resolution RFC 3405: DDDS URI.ARPA Assignment Procedures |
| RFC3402 Part Two: The Domain Name System (DNS) Database |
| RFC3403 Part Three: The Domain Name System (DNS) Database |
297 | NAPTR resource record query |
| 4. NAPTR RR Format |
| 4.1 Packet Format |
298 | Order comparison |
299 | Preference comparison |
300 | Flag "" to control rewriting and interpretation |
301 | Flag "A" to control rewriting and interpretation |
302 | Flag "S" to control rewriting and interpretation |
303 | Selection of services |
304 | Encounter Unknown flag |
305 | Both REGEXP and REPLACEMENT fields exist. |
| 6. Example |
306 | E164 to Uniform Resource Identifiers (URI) |
| RFC3404 Part Four: The Uniform Resource Identifiers (URI) Resolution Application |
| 5. Examples |
307 | URN resolution |
| RFC3405 Part Five: URI.ARPA Assignment Procedures |
| RFC3425 Obsoleting IQUERY |
| 3 - Effect on RFC 1035 |
308 | Obsoleting IQUERY |
| RFC3596 DNS Extensions to Support IP Version 6 |
| 2 New resource record definition and domain |
| 2.1 AAAA record type |
309 | AAAA record |