NAME

        SV_RFC1996_3_9_master_NOTIFY_continue_service - a master continue to offer name service during the NOTIFY transaction.

VERIFICATION POINTS

        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.

The interval between transmissions, and the total number of

retransmissions, should be operational parameters specifiable by

the name server administrator, perhaps on a per-zone basis.

Reasonable defaults are a 60 second interval (or timeout if

using TCP), and a maximum of 5 retransmissions (for UDP). It is

considered reasonable to use additive or exponential backoff for

the retry interval.

TARGET

        Server (AXFR/IXFR server)

SYNOPSIS

	SV_RFC1996_3_9_master_NOTIFY_continue_service.seq [-tooloption ...]: KOI tool option
	See also DNSConfig.pm

INITIALIZATION

Network Topology

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

Setup

Set the DNS Server1's (NUT) address as above mentioned Network Topology.

Configure the Server1's: (NUT)

zone file to response query from TN.

configuration file as slave server about sec.example.com zone.

Enable zone transfer function.

Enable Notify mechanism function.

Example of DNS server configuration on DNS Server1 (NUT):

	
For IPv4 transport
zone "sec.example.com" {
	type master;
	allow-transfer { 192.168.0.30; };
	also-notify    { 192.168.0.30; };
	file "master/sec.example.com";
};
	
For IPv6 transport
zone "sec.example.com" {
	type master;
	allow-transfer { 3ffe:501:ffff:100::30; };
	also-notify    { 3ffe:501:ffff:100::30; };
	file "master/sec.example.com";
};

Transferred sec.example.com zone information:

$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

PRE-TEST SEQUENCE

Update sec.example.com zone like following on DNS Server1 (NUT)

$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

TEST PROCEDURE

        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. Send standard query       |
        |                              |
        |  QNAME = CL2.sec.example.com |
        |  QTYPE = A                   |
        |                              |
        |----------------------------->|
        |                              |
        | 3. Standard query response   |
        |  QNAME = CL2.sec.example.com |
        |  QTYPE = A                   |
        |  ANSWER Name                 |
        |        = CL2.sec.example.com |
        |  ANSWER Type                 |
        |        = A (0x0001)          |
        |  ANSWER Address              |
        |        = 192.168.0.21        |
        |                              |
        v                              v

        This test sequence is following.

        1. DNS Server1 (NUT) sends a NOTIFY request to DNS Server2 (TN). (Judgment *1)
        2. DNS Server2 (TN) sends a standard request QNAME=CL2.sec.example.com QTYPE=A to DNS Server1 (TN).
        3. DNS Server1 (NUT) sends a standard reply CL2.sec.example.com A 192.168.0.21 to DNS Server2 (TN). (Judgment *3)

Packet Description

1st packet.

A NOTIFY request from DNS Server1 (NUT) to Server2 (TN)
IP Header	Source Address	NUT_NETZ
IP Header	Destination Address	SV2_NETZ
TCP Header	Src Port	any
TCP Header	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)

2nd packet.

A standard request from DNS Server2 (TN) to Server1 (NUT)
IP Header	Source Address	SV2_NETZ
IP Header	Destination Address	NUT_NETZ
TCP Header	Src Port	2000
TCP Header	Dst Port	53
DNS Header	ID	0x1000
	QR	0
	OPCODE	0
	AA	0
	TC	0
	RD	0
	RA	0
	Z	0
	RCODE	0
	QDCOUNT	1
	ANCOUNT	0
	NSCOUNT	0
	ARCOUNT	0
DNS Question section	QNAME	CL2.sec.example.com
	QTYPE	A (0x0001)
	QCLASS	IN (0x0001)

3rd packet.

A standard response from DNS Server1 (NUT) to Server2 (TN)
IP Header	Source Address	NUT_NETZ
IP Header	Destination Address	SV2_NETZ
TCP Header	Src Port	53
TCP Header	Dst Port	2000
DNS Header	ID	0x1000
	QR	1
	OPCODE	0
	AA	1
	TC	0
	RD	0
	RA	0
	Z	0
	RCODE	0
	QDCOUNT	1
	ANCOUNT	1
	NSCOUNT	2
	ARCOUNT	4
DNS Question section	QNAME	CL2.sec.example.com
	QTYPE	A (0x0001)
	QCLASS	IN (0x0001)
DNS Answer section	NAME	CL2.sec.example.com (Pointer 0xC00C)
	TYPE	A (0x0001)
	CLASS	IN (0x0001)
	TTL	1 day (86400)
	RDLENGTH	4
	ADDRESS	192.168.0.21
DNS Authority section	NAME	sec.example.com (Pointer 0xC010)
	TYPE	NS (0x0002)
	CLASS	IN (0x0001)
	TTL	1 day (86400)
	RDLENGTH	6
	NSDNAME	NS1.sec.example.com. (NS1 + Pointer 0xC010)
DNS Authority section	NAME	sec.example.com
	TYPE	NS (0x0002)
	CLASS	IN (0x0001)
	TTL	1 day (86400)
	RDLENGTH	6
	NSDNAME	NS2.sec.example.com. (NS2 + Pointer 0xC010)
DNS Additional section	NAME	NS1.sec.example.com (Pointer 0xC041)
	TYPE	A (0x0001)
	CLASS	IN (0x0001)
	TTL	1 day (86400)
	RDLENGTH	4
	NSDNAME	192.168.0.10
DNS Additional section	NAME	NS1.sec.example.com (Pointer 0xC041)
	TYPE	AAAA (0x001C)
	CLASS	IN (0x0001)
	TTL	1 day (86400)
	RDLENGTH	16
	NSDNAME	3ffe:501:ffff:100::10
DNS Additional section	NAME	NS2.sec.example.com (Pointer 0xC053)
	TYPE	A (0x0001)
	CLASS	IN (0x0001)
	TTL	1 day (86400)
	RDLENGTH	4
	NSDNAME	192.168.0.30
DNS Additional section	NAME	NS2.sec.example.com (Pointer 0xC053)
	TYPE	AAAA (0x001C)
	CLASS	IN (0x0001)
	TTL	1 day (86400)
	RDLENGTH	16
	NSDNAME	3ffe:501:ffff:100::30

Exp.

NUT_NETZ	DNS Server1's (NUT) Net-z address
SV2_NETZ	DNS Server7's (TN) Net-z address

JUDGMENT

        1. DNS Server1 (NUT) sends a NOTIFY request to DNS Server2 (TN).
        3. DNS Server1 (NUT) sends a standard reply CL2.sec.example.com A 192.168.0.21 to DNS Server2 (TN).

TERMINATION

        None

REFERENCE

        RFC1996 DNS NOTIFY
        3. NOTIFY Message