NAME

        SV_RFC1996_3_3_slave_NOTIFY_response - Slave server sends a NOTIFY response back to the NOTIFY request's source.

VERIFICATION POINTS

        Verify that a NUT sends a NOTIFY response back to the NOTIFY request's source.

NOTIFY is similar to QUERY in that it has a request message with
the header QR flag "clear" and a response message with QR "set". The
response message contains no useful information, but its reception by
the master is an indication that the slave has received the NOTIFY
and that the master can remove the slave from any retry queue for
this NOTIFY event.

TARGET

        Server (an IXFR client)

SYNOPSIS

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

INITIALIZATION

Network Topology

                   |
                   |                     sec.example.com domain
                 Router (TN)             DNS Server7
                   |3ffe:501:ffff:100::1   |3ffe:501:ffff:100::31
                   |192.168.0.1            |192.168.0.31
                   |                       |
                   |                       |
Net-z   --+--------+---------------+-------+------------------- 3ffe:501:ffff:100::/64
          |                        |                            192.168.0/24
          |                        |
        DNS Server1 (NUT)         DNS Client1 (TN)
           3ffe:501:ffff:100::10    3ffe:501:ffff:100::20
           192.168.0.10             192.168.0.20
	

	

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 incremental zone transfer function.


Enable Notify mechanism function.



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

	
For IPv4 transport
zone "sec.example.com" {
	type slave;
	masters {192.168.0.31;};
	file "s/sec.example.com";
};
	
For IPv6 transport
zone "sec.example.com" {
	type slave;
	masters {3ffe:501:ffff:100::31;};
	file "s/sec.example.com";
};
	

Transferred sec.example.com zone information:


$TTL    86400	; TTL of 1 day
@ IN SOA NS7.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	NS7.sec.example.com.
	IN	NS	NS1.sec.example.com.
	IN	MX	10	NS7
NS7	IN	A	192.168.0.31
	IN	AAAA	3ffe:501:ffff:100::31
NS1	IN	A	192.168.0.10
	IN	AAAA	3ffe:501:ffff:100::10
;
CL1	IN	A	192.168.0.20
CL2	IN	A	192.168.0.21
	

PRE-TEST SEQUENCE

        After all zone information are transferred between primary DNS server7 (TN) 
        and slave DNS server1 (NUT), following pre-test sequence is performed.

    DNS Client1 (TN)             DNS Server1 (NUT)              DNS Server7 (TN)
        |                              |                              |
        |----------------------------->|                              |
        | 1. Send standard query       |                              |
        |  RD = 0                      |                              |
        |  QNAME = CL2.sec.example.com |                              |
        |  QTYPE = A                   |                              |
        |                              |                              |
        |<-----------------------------|                              |
        | 2. Standard query response   |                              |
        |  AA = 0                      |                              |
        |  RD = 0                      |                              |
        |  RA = 1                      |                              |
        |  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                              v

TEST PROCEDURE

        This test sequence is following.
        NOTE: SOA's parameter and $TTL are same as above sec.example.com zone information.
              TN includes NS7 and NS1.sub.example.com into Authority section as type = NS.
              Also TN includes NS7 and NS1.sub.example.com address into Additional section.
              Thus NUT may reply to answer client with Authority and Additional section including
              those values.

    DNS Client1 (TN)             DNS Server1 (NUT)              DNS Server7 (TN)
        |                              |                              |
        |                              |                              |
        |                              |<-----------------------------|
        |                              | 1. A NOTIFY request          |
        |                              |  OPCODE = NOTIFY (4)         |
        |                              |  QNAME = sec.example.com     |
        |                              |  QTYPE = SOA (0x0006)        |
        |                              |                              |
        |                              |----------------------------->|
        |                              | 2. A NOTIFY response         |
        |                              |  OPCODE = NOTIFY (4)         |
        |                              |  QNAME = sec.example.com     |
        |                              |  QTYPE = SOA (0x0006)        |
        |                              |                              |
        v                              v                              v

        This test sequence is following.

        1. DNS Server7 (TN) sends NOTIFY request to DNS Server1 (NUT).

        2. DNS Server1 (NUT) sends NOTIFY response to DNS Server7 (TN). (Judgment *2)

Packet Description



1st packet.

Standard query from DNS Server1 (NUT) to Server7 (TN)
IP Header	Source Address	SV7_NETZ
	Destination Address	NUT_NETZ
UDP Header	Src Port	2000
	Dst Port	53
DNS Header	ID	0x1000
	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.

Standard query response from DNS Server7 (TN) to Server1 (NUT)
IP Header	Source Address	NUT_NETZ
	Destination Address	SV7_NETZ
UDP Header	Src Port	53
	Dst Port	2000
DNS Header	ID	0x1000
	QR	1
	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)




Exp.


NUT_NETZ	DNS Server1's (NUT) Net-z address
CL1_NETZ	DNS Client1's (TN) Net-z address
SV7_NETZ	DNS Server7's (TN) Net-z address

JUDGMENT

        2. DNS Server1 (NUT) sends NOTIFY response to DNS Server7 (TN).

TERMINATION

        None

REFERENCE

        RFC 1996 DNS NOTIFY
        3. NOTIFY Message