SV_RFC3403_4_1_multi_NAPTR - Multiple NAPTR resource records with several ORDER and PREFERENCE
Verify that a NUT transmits correct message including multiple NAPTR resource records with several ORDER and PREFERENCE
ORDER : | A 16-bit unsigned integer specifying the order in which the NAPTR records MUST be processed in order to accurately represent the ordered list of Rules.The ordering is from lowest to highest. If two records have the same order value then they are considered to be the same rule and should be selected based on the combination of the Preference values and Services offered. |
PREFERENCE : | Although it is called "preference" in deference to DNS terminology, this field is equivalent to the Priority value in the DDDS Algorithm. It is a 16-bit unsigned integer that specifies the order in which NAPTR records with equal Order values SHOULD be processed, low numbers being processed before high numbers. This is similar to the preference field in an MX record, and is used so domain administrators can direct clients towards more capable hosts or lighter weight protocols. A client MAY look at records with higher preference values if it has a good reason to do so such as not supporting some protocol or service very well. |
Authoritative Server
SV_RFC3403_4_1_multi_NAPTR.seq [-tooloption ...]: KOI tool option See also DNSConfig.pm
AP Server1 (TN) |3ffe:501:ffff:101::10 |192.168.1.10 | Net-y --+--------+-------------------------- 3ffe:501:ffff:101::/64 | 192.168.1/24 | | Router (TN) |3ffe:501:ffff:100::1 |192.168.0.1 | | Net-z --+--------+-----------------+-------- 3ffe:501:ffff:100::/64 | | 192.168.0/24 | | DNS Server1 (NUT) DNS Client1 (TN) 3ffe:501:ffff:100::XXXX 3ffe:501:ffff:100::20 3ffe:501:ffff:100::10 192.168.0.10 192.168.0.20
XXXX: EUI64
$TTL 86400 ; TTL of 1 day @ IN SOA NS1.example.com. root.example.com. ( 2005081600 ; serial 3600 ; refresh every 1 hr 900 ; retry every 15 min 604800 ; expire after a week 3600 ; Minimum TTL of a 1 hr ) ; IN NS NS1.example.com. NS1 IN A 192.168.0.10 ; A IN A 192.168.1.10
$TTL 86400 ; TTL of 1 day @ IN SOA NS1.example.com. root.example.com. ( 2005081600 ; serial 3600 ; refresh after 1 hr 900 ; retry after 15 min 604800 ; expire after 1 week 3600 ; Minimum TTL of 1 hr ) ; IN NS NS1.example.com. ; 1.0.0.0 IN NAPTR 100 10 "U" "sip+E2U" "!^.*$!sip:info1@example.com!i" . ; 1.0.0.0 IN NAPTR 100 11 "U" "sip+E2U" "!^.*$!sip:info2@example.com!i" . ; 1.0.0.0 IN NAPTR 101 10 "U" "sip+E2U" "!^.*$!sip:info3@example.com!i" . ; 1.0.0.0 IN NAPTR 101 10 "U" "sip+E2U" "!^.*$!sip:info4@example.com!i" .
This test sequence is following.
DNS Client1 (TN) DNS Server1 (NUT) | | |------------------------------------->| | 1. Send standard query | | QNAME = 1.0.0.0.1.1.1.1.0.9.1.8.e164.arpa. | QTYPE= NAPTR | | | |<-------------------------------------| | 2. Standard query response | | | | | v v
1. TN send standard query QNAME=1.0.0.0.1.1.1.1.0.9.1.8.e164.arpa., QTYPE=NAPTR to NUT. 2. NUT reply query response w/ NAPTR resource records to TN (Judgment *2)
|
||
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 | 1.0.0.0.1.1.1.1.0.9.1.8.e164.arpa. |
QTYPE | NAPTR (0x0023) | |
QCLASS | IN (0x0001) |
|
||
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 | 1 | |
TC | 0 | |
RD | 0 | |
RA | 0 | |
Z | ANY | |
RCODE | 0 | |
QDCOUNT | 1 | |
ANCOUNT | 4 | |
NSCOUNT | 1 | |
ARCOUNT | 1 | |
DNS Question section | QNAME | 1.0.0.0.1.1.1.1.0.9.1.8.e164.arpa |
QTYPE | NAPTR (0x0023) | |
QCLASS | IN (0x0001) | |
DNS Answer section | NAME | 1.0.0.0.1.1.1.1.0.9.1.8.e164.arpa (Pointer 0xC00C) |
TYPE | NAPTR (0x0023) | |
CLASS | IN (0x0001) | |
TTL | 86400sec | |
RDLENGTH | 45 | |
ORDER | 100 | |
PREFERENCE | 10 | |
FLAGS | U | |
SERVICES | sip+E2U | |
REGEXP | !^.*$!sip:info1@example.com!i | |
REPLACEMENT | . | |
DNS Answer section | NAME | 1.0.0.0.1.1.1.1.0.9.1.8.e164.arpa (Pointer 0xC00C) |
TYPE | NAPTR (0x0023) | |
CLASS | IN (0x0001) | |
TTL | 86400sec | |
RDLENGTH | 45 | |
ORDER | 100 | |
PREFERENCE | 11 | |
FLAGS | U | |
SERVICES | sip+E2U | |
REGEXP | !^.*$!sip:info2@example.com!i | |
REPLACEMENT | . | |
DNS Answer section | NAME | 1.0.0.0.1.1.1.1.0.9.1.8.e164.arpa (Pointer 0xC00C) |
TYPE | NAPTR (0x0023) | |
CLASS | IN (0x0001) | |
TTL | 86400sec | |
RDLENGTH | 45 | |
ORDER | 101 | |
PREFERENCE | 10 | |
FLAGS | U | |
SERVICES | sip+E2U | |
REGEXP | !^.*$!sip:info3@example.com!i | |
REPLACEMENT | . | |
DNS Answer section | NAME | 1.0.0.0.1.1.1.1.0.9.1.8.e164.arpa (Pointer 0xC00C) |
TYPE | NAPTR (0x0023) | |
CLASS | IN (0x0001) | |
TTL | 86400sec | |
RDLENGTH | 45 | |
ORDER | 101 | |
PREFERENCE | 10 | |
FLAGS | U | |
SERVICES | sip+E2U | |
REGEXP | !^.*$!sip:info4@example.com!i | |
REPLACEMENT | . | |
DNS Authority section | NAME | 1.1.1.1.0.9.1.8.e164.arpa. (Pointer 0xC014) |
TYPE | NS (0x0002) | |
CLASS | IN (0x0001) | |
TTL | 1 day (86400) | |
RDLENGTH | 17 | |
NSDNAME | NS1.example.com | |
DNS Additional section | NAME | NS1.example.com (Pointer 0xC123) |
TYPE | A (0x0001) | |
CLASS | IN (0x0001) | |
TTL | 1 day (86400) | |
RDLENGTH | 4 | |
ADDRESS | 192.168.0.10 |
NUT_NETZ | DNS Server1's (NUT) Net-z address |
CL1_NETZ | DNS Client1's (TN) Net-z address |
2. Received standard query response including NAPTR resource records.
None
RFC3403 Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database 4. NAPTR RR Format 4.1 Packet Format