CL_RFC1034_3_6_NS_type - NS type in standard query
Verify that a NUT transmits correct standard query format for NS type
Client
CL_RFC1034_3_6_NS_type.seq [-tooloption ...]: KOI tool option
See also DNSConfig.pm
AP Server1(TN):ns.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 NS type of 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
|
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 |
example.com
|
QTYPE
|
NS (0x0002)
|
QCLASS
|
any
|
NUT_NETZ : DNS Client1(NUT)'s address
SV_NETY : DNS Server1(TN)'s address
1. Standard query for NS type must be based on above Verification Points.
If NUT has cache function, clear the cache.
RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES
3.6. Resource Records
RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION
3.2.2. TYPE values