Files
bind9/bin/tests/system/dnstap
Tom Krizek 5f809e50b6 Check for proper file size output in dnstap test
Previously, the first check silently failed, as 454 is apparently (in my
local setup) the minimum output size for the dnstap output, rather than
470 which the test was expecting. Effectively, the check served as a 5
second sleep rather than waiting for the proper file size.

Additionally, check the expected file sizes and fail if expectations
aren't met.
2023-06-22 19:19:08 +02:00
..

Copyright (C) Internet Systems Consortium, Inc. ("ISC")

SPDX-License-Identifier: MPL-2.0

This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0.  If a copy of the MPL was not distributed with this
file, you can obtain one at https://mozilla.org/MPL/2.0/.

See the COPYRIGHT file distributed with this work for additional
information regarding copyright ownership.

The "large-answer.fstrm" file was generated by configuring a named instance
compiled with --enable-dnstap and --enable-fixed-rrset with the following
directives:

    minimal-responses yes;
    rrset-order { order fixed; };
    dnstap { auth response; };
    dnstap-identity none;
    dnstap-output file "large-answer.fstrm";

The captured RRset from the "example." zone was created using:

    $GENERATE 1-48 @ IN A 127.0.0.$

A server instance set up this way was then queried non-recursively (RD=0) for
"example/A".