CL_RFC1035_3_1_label_root - Label of root
Verify that a NUT transmits correct standard query for label of root
- Since every domain name ends with the null label of
- the root, a domain name is terminated by a length byte of zero.
Client
CL_RFC1035_3_1_label_root.seq [-tooloption ...]: KOI tool option
See also DNSConfig.pm
AP Server1(TN):A.example.com DNS Server1(TN)
|3ffe:501:ffff:101::10 |3ffe:501:ffff:101::20
|192.168.1.10 |192.168.1.20
| |
Net-y --+--------+-----------------------+-------- 3ffe:501:ffff:101::/64
| 192.168.1/24
|
|
ROUTER1(TN)
|3ffe:501:ffff:100::1
|192.168.0.1
|
Net-z --+--------+-------------------------------- 3ffe:501:ffff:100::/64
| 192.168.0/24
DNS Client1(NUT)
3ffe:501:ffff:100:XXXX
192.168.0.10
XXXX: EUI64 address
Setup
Set the DNS Server1(TN)'s address on NUT as above mentioned Network Topology.
Pre-Sequence
In order to send the query for A type of AP Server1(TN):A.example.com to the DNS Server1(TN),
NUT is configured.
This test sequence is following.
DNS Client1 (NUT) DNS Server1 (TN)
| |
|--------------------------------------------->|
| 1. Send standard query |
| |
v v
1. NUT send standard query to TN.
Judgment (Check *1)
- Packet Description
- 1st Packet
|
1. Standard query from DNS Client1 (NUT) to DNS Server1 (TN)
|
| IP Header |
Source Address |
NUT_NETZ |
| Destination Address |
SV_NETY |
UDP Header
|
Src Port
|
any
|
Dst Port
|
53
|
DNS Header
|
ID |
any |
QR
|
0
|
OPCODE
|
0
|
AA
|
any
|
| TC |
0 |
| RD |
any |
RA
|
any
|
Z
|
any
|
RCODE
|
any
|
QDCOUNT
|
1
|
ANCOUNT
|
0
|
NSCOUNT
|
0
|
ARCOUNT
|
any
|
DNS Question section
|
QNAME |
A.example.com
|
QTYPE
|
A (0x0001)
|
QCLASS
|
any
|
- Exp.
| NUT_NETZ |
DNS Client1's (NUT) Net-z address |
| SV_NETY |
DNS Server1's (TN) Net-y address |
1. 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| c |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| o | m |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| 0 0 0 0 0 0 0 0|
+--+--+--+--+--+--+--+--+
If NUT has cache function, clear the cache.
RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION
3.1. Name space definitions