NAME

        SV_RFC1034_3_6_2_no_other_data - CNAME RR is present at a node, no other data should be present

VERIFICATION POINTS

        Verify that a NUT does not transmit response including multiple CNAME RR.

If a CNAME RR is present at a node, no other data should be

present; this ensures that the data for a canonical name and its aliases

cannot be different. This rule also insures that a cached CNAME can be

used without checking with an authoritative server for other RR types.

TARGET

        Authoritative Server

SYNOPSIS

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

INITIALIZATION

Network Topology

        AP Server1 (TN)
          |3ffe:501:ffff:101::10,11
          |192.168.1.10,11
          |
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 
           192.168.0.10                192.168.0.20
	

	XXXX: EUI64

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.

Example of example.com zone file:

$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
A1	IN	A	192.168.1.10
A2	IN	A	192.168.1.11
;
B	IN	CNAME	A1.example.com.
B	IN	CNAME	A2.example.com.

TEST PROCEDURE

        This test sequence is following.

    DNS Client1 (TN)                       DNS Server1 (NUT)
        |                                      |
        |------------------------------------->|
        |   1. Send standard query             |
        |       QNAME=B.example.com            |
        |       QTYPE=CNAME                    |
        |                                      |
        | X <----------------------------------|
        |   2. Standard query response         |
        |       QNAME=B.example.com            |
        |       QTYPE=CNAME                    |
        |       ANSWER Name=B.example.com      |
        |       ANSWER Type=CNAME              |
        |       ANSWER CNAME=A1.example.com    |
        |       ANSWER Name=B.example.com      |
        |       ANSWER Type=CNAME              |
        |       ANSWER CNAME=A2.example.com    |
        |                                      |
        |                                      |
        v                                      v

        1. TN send standard query QNAME=B1.example.com, QTYPE=A to NUT.
        2. NUT reply query response including CNAME=A1.example.com, CNAME=A2.example.com to TN (Judgment *2)

Packet Description

1st packet.

Standard query from DNS Client1 (TN) to Server1 (NUT)
IP Header	Source Address	CL1_NETZ
IP Header	Destination Address	NUT_NETZ
UDP Header	Src Port	2000
UDP Header	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	B.example.com
	QTYPE	CNAME (0x0005)
	QCLASS	IN (0x0001)

Exp.

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

JUDGMENT

        2. Not received standard query response including CNAME.

TERMINATION

        None

REFERENCE

        RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES
        3.6.2. Aliases and canonical names