NAME

        CL_RFC1035_7_3_invalid_response - Invalid response(query is returned)


VERIFICATION POINTS

        Verify that a NUT checks the header of response


TARGET

        Client


SYNOPSIS

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


INITIALIZATION


TEST PROCEDURE

	This test sequence is following.

DNS Client1 (NUT) DNS Server1 (TN) AP Server1 (TN) | | | |--------------------------------------------->| | | 1. Send standard query | | | QNAME=B.example.com | | | | | |<---------------------------------------------| | | 2. Standard query response | | | QR=0 (query):invalid | | | | | |----------------------------------------------|------------------------------------------> X | | 3. Echo Request(Echo Message) | | | | | v v v
1. NUT send standard query to DNS Server1(TN). Judgment (Check *1) 2. TN send standard query response to NUT. 3. NUT send Echo Request(Echo Message) to to AP Server1(TN). Judgment (Check *3)


JUDGMENT

        1. Received standard query QNAME=B.example.com from NUT.
        3. Not received Echo Request(Echo Message) from NUT.


TERMINATION

        If NUT has cache function, clear the cache.


REFERENCE

	RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION
	7.3. Processing responses