named1.conf.in revision 1.1.1.3
1/* 2 * Copyright (C) Internet Systems Consortium, Inc. ("ISC") 3 * 4 * SPDX-License-Identifier: MPL-2.0 5 * 6 * This Source Code Form is subject to the terms of the Mozilla Public 7 * License, v. 2.0. If a copy of the MPL was not distributed with this 8 * file, you can obtain one at https://mozilla.org/MPL/2.0/. 9 * 10 * See the COPYRIGHT file distributed with this work for additional 11 * information regarding copyright ownership. 12 */ 13 14include "../../common/rndc.key"; 15 16controls { 17 inet 10.53.0.2 port @CONTROLPORT@ allow { any; } keys { rndc_key; }; 18}; 19 20options { 21 query-source address 10.53.0.2; 22 notify-source 10.53.0.2; 23 transfer-source 10.53.0.2; 24 port @PORT@; 25 pid-file "named.pid"; 26 listen-on { 10.53.0.2; }; 27 listen-on-v6 { fd92:7065:b8e:ffff::2; }; 28 notify no; 29 recursion no; 30 serial-query-rate 100; 31 catalog-zones { 32 zone "catalog1.example" 33 default-masters { 10.53.0.1; } 34 in-memory no 35 zone-directory "zonedir"; 36 zone "catalog2.example" 37 default-masters { 10.53.0.1 port @EXTRAPORT1@; } 38 in-memory yes; 39 zone "catalog3.example" 40 default-masters { 10.53.0.1; } 41 zone-directory "nonexistent"; 42#T1 zone "catalog4.example" 43#T1 default-masters { 10.53.0.1; }; 44#T2 zone "catalog5.example" 45#T2 default-masters { 10.53.0.1; }; 46 }; 47}; 48 49# A faulty dlz configuration to check if named and catz survive a certain class 50# of failed configuration attempts (see GL #3060). 51# We use "dlz" because the dlz processing code is located in an ideal place in 52# the view configuration function for the test to cover the view reverting code. 53#T3dlz "bad-dlz" { 54#T3 database "dlopen bad-dlz.so example.org"; 55#T3}; 56 57zone "catalog1.example" { 58 type secondary; 59 file "catalog1.example.db"; 60 primaries { 10.53.0.1; }; 61}; 62 63zone "catalog2.example" { 64 type secondary; 65 file "catalog2.example.db"; 66 primaries { 10.53.0.3; }; 67}; 68 69zone "catalog3.example" { 70 type secondary; 71 file "catalog3.example.db"; 72 primaries { 10.53.0.1; }; 73}; 74 75zone "catalog4.example" { 76 type secondary; 77 file "catalog4.example.db"; 78 primaries { 10.53.0.1; }; 79}; 80 81# When the following zone configuration is enabled, "dom3.example" should 82# already exist as a member of "catalog1.example", and named should be able 83# to deal with that situation (see GL #3911). Make sure that this duplicate 84# zone comes after the the "catalog1.example" zone in the configuration file. 85#T4zone "dom3.example" { 86#T4 type secondary; 87#T4 file "dom2.example.db"; 88#T4}; 89 90key tsig_key. { 91 secret "LSAnCU+Z"; 92 algorithm @DEFAULT_HMAC@; 93}; 94 95key next_key. { 96 secret "LaAnCU+Z"; 97 algorithm @DEFAULT_HMAC@; 98}; 99