NAME

        CL_RFC1034_5_3_2_Cache_vs_auth - Cache data vs authoritative data


VERIFICATION POINTS

        Verify that a NUT uses the authoritative data in preference to cached data


TARGET

        Client (with Caching function)


SYNOPSIS

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


INITIALIZATION


TEST PROCEDURE

	This test sequence is following.

DNS Client1 (NUT) DNS Server1 (TN) | | |--------------------------------------------->| | 1. Send standard query | | QNAME=A.example.com | | | |<---------------------------------------------| | 2. Standard query response | | | | *disregard the cached data | |--------------------------------------------->| | 3. Send standard query | | QNAME=A.example.com | v v
1. NUT send standard query to TN. Judgment (Check *1) 2. TN send standard query response to NUT. 3. The function to disregard the cached data is set. NUT send standard query to TN. Judgment (Check *3)


JUDGMENT

        1. Received standard query QNAME=A.example.com from NUT.
        3. Received standard query QNAME=A.example.com from NUT.


TERMINATION

        If NUT has cache function, clear the cache.


REFERENCE

	RFC1034 DOMAIN NAMES - CONCEPTS AND FACILITIES
	5.3.2. Resouces
	5.3.3. Algorithm

RFC1035 DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION 7.4. Using the cache