SV_RFC2181_10_2_RRSet_PTR - RRSet for PTR record
Verify that a NUT transmits response including RRSet for PTR resource record
-
Confusion about canonical names has lead to a belief that a PTR
record should have exactly one RR in its RRSet. This is incorrect,
the relevant section of RFC1034 (section 3.6.2) indicates that the
value of a PTR record should be a canonical name. That is, it should
not be an alias. There is no implication in that section that only
one PTR record is permitted for a name. No such restriction should
be inferred.
Authoritative Server
SV_RFC2181_10_2_RRSet_PTR.seq [-tooloption ...]: KOI tool option
See also DNSConfig.pm
This test sequence is following.
DNS Client1 (TN) DNS Server1 (NUT)
| |
|------------------------------------->|
| 1. Send standard query |
| QNAME=10.1.168.192.IN-ADDR.ARPA |
| QTYPE=PTR |
| |
|<-------------------------------------|
| 2. Standard query response |
| |
| |
v v
1. TN send standard query QNAME=10.1.168.192.IN-ADDR.ARPA, QTYPE=PTR to NUT.
2. NUT reply query response w/ PTR=A.example.com, B.example.com to TN (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 |
10.1.168.192.IN-ADDR.ARPA |
| QTYPE |
PTR (0x000C) |
| QCLASS |
IN (0x0001) |
- 2nd packet.
|
Standard query response from DNS Server1 (NUT) to Client1 (TN)
|
| IP Header |
Source Address |
NUT_NETZ |
| Destination Address |
CL1_NETZ |
| UDP Header |
Src Port |
53 |
| Dst Port |
2000 |
| DNS Header |
ID |
0x1000 |
| QR |
1 |
| OPCODE |
0 |
| AA |
ANY |
| TC |
0 |
| RD |
1 |
| RA |
1 |
| Z |
0 |
| RCODE |
0 |
| QDCOUNT |
1 |
| ANCOUNT |
2 |
| NSCOUNT |
1 |
| ARCOUNT |
1 |
| DNS Question section |
QNAME |
10.1.168.192.IN-ADDR.ARPA |
| QTYPE |
PTR (0x000C) |
| QCLASS |
IN (0x0001) |
| DNS Answer section |
NAME |
10.1.168.192.IN-ADDR.ARPA (Pointer 0xC00C) |
| TYPE |
PTR (0x000C) |
| CLASS |
IN (0x0001) |
| TTL |
1 day (86400) |
| RDLENGTH |
15 |
| PTRDNAME |
A.example.com |
| DNS Answer section |
NAME |
10.1.168.192.IN-ADDR.ARPA (Pointer 0xC00C) |
| TYPE |
PTR (0x000C) |
| CLASS |
IN (0x0001) |
| TTL |
1 day (86400) |
| RDLENGTH |
4 |
| PTRDNAME |
B.example.com (B + Pointer 0xC039) |
| DNS Authority section |
NAME |
1.168.192.IN-ADDR.ARPA (Pointer 0xC00F) |
| TYPE |
NS (0x0002) |
| CLASS |
IN (0x0001) |
| TTL |
1 day (86400) |
| RDLENGTH |
6 |
| NSDNAME |
NS1.example.com (NS1 + Pointer 0xC039) |
| DNS Additional section |
NAME |
NS1.example.com (Pointer 0xC062) |
TYPE
|
A (0x0001) |
| CLASS |
IN (0x0001) |
| TTL |
1 day (86400) |
| RDLENGTH |
4 |
| ADDRESS |
192.168.0.10 |
- Exp.
| NUT_NETZ |
DNS Server1's (NUT) Net-z address |
| CL1_NETZ |
DNS Client1's (TN) Net-z address |
2. Received standard query response including RRSet for PTR resource record.
None
RFC2181 Clarifications to the DNS Specification
10.2. PTR records