SV_RFC1996_3_5_master_NOTIFY_retransmission - a slave sends a once a NOTIFY request until timeout.
If TCP is used, both master and slave must continue to offer name service during the transaction, even when the TCP transaction is not making progress. The NOTIFY request is sent once, and a "timeout" is said to have occurred if no NOTIFY response is received within a reasonable interval.
Server (AXFR/IXFR server)
SV_RFC1996_3_5_master_NOTIFY_retransmission.seq [-tooloption ...]: KOI tool option See also DNSConfig.pm
Net-z --+------------------------+--------------------------- 3ffe:501:ffff:100::/64 | | 192.168.0/24 | | sec.example.com domain DNS Server1 (NUT) DNS Server2 (TN) 3ffe:501:ffff:100::10 3ffe:501:ffff:100::30 192.168.0.10 192.168.0.30
$TTL 86400 ; TTL of 1 day @ IN SOA NS1.sec.example.com. root.sec.example.com. ( 1 ; serial 180 ; refresh every 3 min 30 ; retry every 30 sec 360 ; expire after 6 min 30 ; Minimum TTL of 30 sec ) ; IN NS NS1.sec.example.com. IN NS NS2.sec.example.com. NS1 IN A 192.168.0.10 IN AAAA 3ffe:501:ffff:100::10 NS2 IN A 192.168.0.30 IN AAAA 3ffe:501:ffff:100::30 ; CL1 IN A 192.168.0.20
$TTL 86400 ; TTL of 1 day @ IN SOA NS1.sec.example.com. root.sec.example.com. ( 2 ; 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.sec.example.com. IN NS NS2.sec.example.com. NS1 IN A 192.168.0.10 NS1 IN AAAA 3ffe:501:ffff:100::10 NS2 IN A 192.168.0.30 NS2 IN AAAA 3ffe:501:ffff:100::30 ; CL1 IN A 192.168.0.20 CL2 IN A 192.168.0.21
This test sequence is following.
DNS Server1 (NUT) DNS Server2 (TN) | | |----------------------------->| | 1. NOTIFY requests | | (in TCP) | | | | QR = 0 | | OPCODE = NOTIFY (4) | | QDCOUNT > 0 | | ANCOUNT >= 0 | | NSCOUNT >= 0 | | ARCOUNT >= 0 | | QNAME = sec.example.com | | QTYPE = SOA (0x0006) | | | |----------------------------->| | 2. no response | | for 60 seconds | | | v v
This test sequence is following.
1. DNS Server1 (NUT) sends a NOTIFY request to DNS Server2 (TN). (Judgment *1) 2. DNS Server1 (NUT) doesn't sends a NOTIFY request to DNS Server2 (TN) for 60 seconds. (Judgment *2)
|
||
IP Header | Source Address | NUT_NETZ |
Destination Address | SV2_NETZ | |
TCP Header | Src Port | any |
Dst Port | 53 | |
DNS Header | ID | any |
QR | 0 | |
OPCODE | 4 | |
AA | 1 | |
TC | 0 | |
RD | 0 | |
RA | 0 | |
Z | 0 | |
RCODE | 0 | |
QDCOUNT | 1 | |
ANCOUNT | >=0 | |
NSCOUNT | >=0 | |
ARCOUNT | >=0 | |
DNS Question section | QNAME | sec.example.com |
QTYPE | SOA (0x0006) | |
QCLASS | IN (0x0001) |
NUT_NETZ | DNS Server1's (NUT) Net-z address |
SV2_NETZ | DNS Server7's (TN) Net-z address |
1. DNS Server1 (NUT) sends a NOTIFY request to DNS Server2 (TN). 2. DNS Server1 (NUT) doesn't sends a NOTIFY request to DNS Server2 (TN) for 60 seconds.
None
RFC1996 DNS NOTIFY 3. NOTIFY Message