NAME

        SV_RFC1996_3_12_master_recv_NOTIMP - a master receives a NOTIMP (unimplemented feature error) message.

VERIFICATION POINTS

        If a NOTIFY request is received by a slave who does not
        implement the NOTIFY opcode, it will respond with a NOTIMP
        (unimplemented feature error) message.  A master server who receives
        such a NOTIMP should consider the NOTIFY transaction complete for
        that slave.

TARGET

        Server (AXFR/IXFR server)

SYNOPSIS

	SV_RFC1996_3_12_master_recv_NOTIMP.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 UDP)                  |
        |                              |
        |  QR = 0                      |
        |  OPCODE = NOTIFY (4)         |
        |  QDCOUNT >  0                |
        |  ANCOUNT >= 0                |
        |  NSCOUNT >= 0                |
        |  ARCOUNT >= 0                |
        |  QNAME = sec.example.com     |
        |  QTYPE = SOA (0x0006)        |
        |                              |
        |<-----------------------------|
        | 2. A NOTIFY response         |
        |    (in UDP)                  |
        |                              |
        |  QR = 1                      |
        |  RCODE = 4                   |
        |  QNAME = sec.example.com     |
        |  QTYPE = SOA (0x0006)        |
        |                              |
        |----------------------------->|
        | 3. 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 Server2 (TN) sends a standard response with RCODE=4 to DNS Server1 (NUT).
        3. DNS Server1 (NUT) doesn't sends a NOTIFY request to DNS Server2 (TN) for 60 seconds. (Judgment *3)

Packet Description



1st packet.

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



2nd packet.

A NOTIFY request from DNS Server2 (TN) to Server1 (NUT)
IP Header	Source Address	SV2_NETZ
	Destination Address	NUT_NETZ
UDP Header	Src Port	53
	Dst Port	same as Src Port of 1st packet
DNS Header	ID	same value as 3rd packet
	QR	1
	OPCODE	0
	AA	0
	TC	0
	RD	0
	RA	0
	Z	0
	RCODE	4
	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
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) doesn't sends a NOTIFY request to DNS Server2 (TN) for 60 seconds.

TERMINATION

        None

REFERENCE

        RFC1996 DNS NOTIFY
        3. NOTIFY Message