511bc1b882
Just like with dynamic and/or inline-signing zones, check if no two or more zone configurations set the same filename. In these cases, the zone files are not read-only and named-checkconf should catch a configuration where multiple zone statements write to the same file. Add some bad configuration tests where KASP zones reference the same zone file. Update the good-kasp test to allow for two zones configure the same file name, dnssec-policy none.
27 lines
657 B
Plaintext
27 lines
657 B
Plaintext
/*
|
|
* Copyright (C) Internet Systems Consortium, Inc. ("ISC")
|
|
*
|
|
* 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 http://mozilla.org/MPL/2.0/.
|
|
*
|
|
* See the COPYRIGHT file distributed with this work for additional
|
|
* information regarding copyright ownership.
|
|
*/
|
|
|
|
// One zone transitioning to insecure, the other with allow-update,
|
|
// with the same zone file.
|
|
|
|
zone "example1.net" {
|
|
type master;
|
|
file "example.db";
|
|
dnssec-policy "insecure";
|
|
};
|
|
|
|
zone "example2.net" {
|
|
type master;
|
|
file "example.db";
|
|
allow-update { any; };
|
|
};
|
|
|