SV_RFC1035_3_1_label_format - Label format
Verify that a NUT transmits correct standard query for label format
- Domain names in messages are expressed in terms of a sequence of labels.
Each label is represented as a one octet length field followed by that
number of octets.
- The high order two bits of every length octet must be zero, and the
remaining six bits of the length field limit the label to 63 octets or
less.
Caching Server
SV_RFC1035_3_1_label_format.seq [-tooloption ...]: KOI tool option
See also DNSConfig.pm
This test sequence is following.
DNS Client1 (TN) DNS Server1 (NUT) DNS Server2 (TN)
| | |
|----------------------------->| |
| 1. Send standard query | |
| QNAME=A.example.org | |
| QTYPE=A | |
| | |
| |-------------------------------->|
| | 2. Recv standard query |
| | QNAME=A.example.org |
| | QTYPE=A |
| | |
v v v
1. TN send standard query QNAME=A.example.org, QTYPE=A to NUT.
2. NUT transmits standard query to DNS Server2 (TN: root name server) (Judgment *2)
- Packet Description
- 1st packet.
|
Standard query from DNS Client1 (TN) to Server1 (NUT)
|
| IP Header |
Source Address |
CL1_NETZ |
| Destination Address |
NUT_NETZ |
| UDP Header |
Src Port |
2000 |
| Dst Port |
53 |
| DNS Header |
ID |
0x1000 |
| QR |
0 |
| OPCODE |
0 |
| AA |
0 |
| TC |
0 |
| RD |
1 |
| RA |
0 |
| Z |
0 |
| RCODE |
0 |
| QDCOUNT |
1 |
| ANCOUNT |
0 |
| NSCOUNT |
0 |
| ARCOUNT |
0 |
| DNS Question section |
QNAME |
A.example.org |
| QTYPE |
A (0x0001) |
| QCLASS |
IN (0x0001) |
- 2nd packet.
|
Standard query from DNS Server1 (NUT) to Server2 (TN)
|
| IP Header |
Source Address |
NUT_NETZ |
| Destination Address |
SV2_NETY |
| UDP Header |
Src Port |
any |
| Dst Port |
53 |
| DNS Header |
ID |
any |
| QR |
0 |
| OPCODE |
0 |
| AA |
any |
| TC |
0 |
| RD |
0 |
| RA |
any |
| Z |
any |
| RCODE |
any |
| QDCOUNT |
1 |
| ANCOUNT |
0 |
| NSCOUNT |
0 |
| ARCOUNT |
any |
| DNS Question section |
QNAME |
A.example.org |
| QTYPE |
A (0x0001) |
| QCLASS |
IN (0x0001) |
- Exp.
| NUT_NETZ |
DNS Server1's (NUT) Net-z address |
| CL1_NETZ |
DNS Client1's (TN) Net-z address |
| SV2_NETY |
DNS Server2's (TN) Net-y address |
| SV3_NETY |
DNS Server3's (TN) Net-y address |
| SV4_NETY |
DNS Server4's (TN) Net-y address |
2. Standard query must be based on above Verification Points.
*In DNS Question section, QNAME field must include following data.
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 0 0 0 0 0 0 0 1| a |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 0 0 0 0 0 1 1 1| e |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| x | a |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| m | p |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| l | e |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 0 0 0 0 0 0 1 1| o |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| r | g |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
None
RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION
3.1. Name space definitions