Version information
This version is compatible with:
- ,
Start using this module
Add this module to your Puppetfile:
mod 'icann-knot', '0.3.7'
Learn more about managing modules with a PuppetfileDocumentation
knot
WARNING version 0.2.x is NOT backwards compatible with 0.1.x
Table of Contents
- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with knot
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Overview
Manage the installation and configuration of KNOT 1.* and zone files.
Module Description
This module allows for the management of all aspects of the KNOT configuration file, keys and zonefiles.
Setup
What knot affects
- Manages configuration the knot configueration file
- Manages zone data in the zone dir
- dynamicly sets processor count based on installed processes
- can manage knot control
Setup Requirements OPTIONAL
- puppetlabs-stdlib 4.11.0
- icann-tea 0.2.8
- puppetlabs-concat 1.2.0
Beginning with knot
Install the package an make sure it is enabled and running with default options:
class { '::knot': }
With some basic configueration
class { '::knot':
ip_addresses => ['192.0.2.1'],
rrl_size => 1000,
}
and in hiera
knot::ip_addresses:
- 192.0.2.1
rrl_size: 1000
Usage
Add config with primary tsig key
class {'::knot':
default_tsig_name: 'test',
tsigs => {
'test',=> {
'algo' => 'hmac-sha256',
'data' => 'adsasdasdasd='
}
}
}
or with hiera
knot::default_tsig_name: test
knot::tsigs:
test:
algo: hmac-sha256
data: adsasdasdasd=
add zone files. zone files are added with sets of common config.
class {'::knot':
remotes => {
master_v4 => { 'address4' => '192.0.2.1' },
master_v6 => { 'address6' => '2001:DB8::1' },
slave => { 'address4' => '192.0.2.2' },
}
zones => {
'example.com' => {
'masters' => ['master_v4', 'master_v6']
'provide_xfrs' => ['slave'],
},
'example.net' => {
'masters' => ['master_v4', 'master_v6']
'provide_xfrs' => ['slave'],
}
'example.org' => {
'masters' => ['master_v4', 'master_v6']
'provide_xfrs' => ['slave'],
}
}
}
in hiera
knot::remotes:
master_v4:
address4: 192.0.2.1
master_v6:
address4: 2001:DB8::1
slave:
address4: 192.0.2.2
knot::zones:
example.com:
masters: &id001
- master_v4
- master_v6
provide_xfrs: &id002
- slave
example.net:
masters: *id001
slave: *id002
example.org:
masters: *id001
slave: *id002
create and as112, please look at the as112 class to see how this works under the hood
class {'::nsd::as112': }
Reference
Classes
Public Classes
Class: knot
Guides the basic setup and installation of KNOT on your system
Parameters (all optional)
default_tsig_name
(Optional[String], Default: undef): the default tsig to use when fetching zone data. Knot::Tsig[$default_tsig_name] must existdefault_masters
(Array[String], Default: []): Array of Knot::Remote names to use as the default master servers if none are specified in the zone hashdefault_provide_xfrs
(Array[String], Default: []): Array of Knot::Remote names to use as the provide_xfr servers if none are specified in the zone hashenable
(Bool, Default: true): enable or disable the knot service, config files are still configuered.zones
: a hash which is passed to create_resoure(knot::zone, $zones). Default: Empty.files
(Hash, Default: {}): a hash which is passed to create_resoure(knot::file, $files).tsigs
(Hash, Default: {}): a hash which is passed to create_resoure(knot::tsig, $tsigs)remotes
(Hash, Default: {}): a hash which is passed to create_resoure(knot::remote, $remotes)ip_addresses
(Array, Default: [$::ipaddress]): Array of IP addresses to listen on.identity
(String, Default: $::fqdn): A string to specify the identity when asked for CH TXT ID.SERVERnsid
(String, Default: $::fqdn): A string representing the nsid to add to the EDNS section of the answer when queried with an NSID EDNS enabled packet.log_target
(Knot::Log_target, Default: syslog): where to send logs.log_zone_level
(Knot::Log_level, Default: notice): Log level for zone messageslog_server_level
(Knot::Log_level, Default: info): Log level for server messageslog_any_level
(Knot::Log_level, Default: error): Log level for any messagesserver_count (Integer. Default: $::processorcount)
: Start this many KNOT workers.max_tcp_clients
(Integer, Default: 250): The maximum number of concurrent, active TCP connections by each server. valid options: Integer.max_udp_payload
(Integer < 4097, Default: 4096): Preferred EDNS buffer size.pidfile
(Tea::Absolutepath, Default: OS Specific): Use the pid file.port
(Tea::Port, Default: 53): Port to listen on.username
(String, Default: knot): After binding the socket, drop user privileges and assume the username.zonesdir
(Tea::Absolutepath, Default: OS Specific): The data directoryhide_version
: (Boolean, Default: false): Prevent KNOT from replying with the version string on CHAOS class queries.rrl_size
: (Integet, Default: 1000000): This option gives the size of the hashtable.rrl_limit
(Integer, Default: 200): The max qps allowed.rrl_slip
(Integer, Default: 2): This option controls the number of packets discarded before we send back a SLIP responsecontrol_enable
(Bool, Default: false): Enable remote controlcontrol_interface
(Array, Default: undef): the interfaces for remote control servicecontrol_port
(Tea::Port, Default: 8952): the port number for remote control servicepackage_name
(String, Default: OS Specific): The package to installservice_name
(String, Default: OS Specific): The service to managezone_subdir
(Tea::Absolutepath, Default: OS Specific): The zone directoryconf_file
(File Path, Default: OS Specific): The config filepuppetdb_server
(Tea::Ip_address, Default: '127.0.0.1'): the ip address of the puppet database server. This is only used for exported resources and the script that uses it runs from the puppet master server. So in a monalithic install localhost should be fine. None monolithic installs will need some way of allowing this connection from the masterpuppetdb_port
(Tea::Port, Default: 8080): the port of the puppet database server unencrypted API interface. This is only used for exported resources and the script that uses it runs from the puppet master server. So in a monalithic install localhost should be fine. None monolithic installs will need some way of allowing this connection from the masternetwork_status
(File Path, Default: undef): if present the upstart script will halt untill this script exits with 0. used to ensure the network is up before starting knot. [ upstarts network started trigger fires when the first interface is configuered so knot might not start at boot if you have multible addresses on the same interface]server_template
(File Path, Default: 'knot/etc/knot/knot.server.conf.'): template file to use for server config. only change if you know what you are doing.zones_template
(File Path, Default: 'knot/etc/knot/knot.zones.conf.erb'): template file to use for zone config. only change if you know what you are doing.remotes_template
(File Path, Default: 'knot/etc/knot/knot.remotes.conf.erb'): template file to use for zone config. only change if you know what you are doing.groups_template
(File Path, Default: 'knot/etc/knot/knot.groups.conf.erb'): template file to use for zone config. only change if you know what you are doing.groups_slave_temp
(File Path, Default: 'knot/etc/knot/knot.groups_slave.conf.erb'): template file to use for zone config. only change if you know what you are doing.
Private Classes
Class knot::params
Set os specific parameters
Private Defined Types
Defined knot::file
Manage files used by knot
Parameters
ensure
(File Path: Default 'present'): how to ensure the fileowner
(String: Default root): the owner of the filegroup
(String: Default knot): the group of the filemode
(String /^\d+$/: Default '0640'): the mode of the fileorigin
(String: Default undef): the zones origin used to check zonecontentsource
(File Path: Default undef): the source location of the filecontent
(string: Default undef): the content to liad to the filecontent_template
(File Path: Default undef): the template location
Defined knot::tsig
Manage tsig keys used by knot
Parameters
algo
(String '^hmac-sha(1|224|256|384|512)$' or '^hmac-md5$', Default: 'hmac-sha256' ): The tsig algorithem of the keydata
(String, Required: true): The tsig key informationtemplate
(Path, Default: 'knot/etc/knot/knot.key.conf.erb'): template to use for tsig config
Defined knot::zone
Manage a zone set conifg for knot
Parameters
masters
(Array, Default: []): List of master server to configurenotify_addresses
(Array, Default: []): List of serveres to notifyallow_notify
(Array, Default: []): List of servers allowed to notifyprovide_xfr
(Array, Default: []): List of servers allowed to preform xfrzones
(Array, Default: []): List of zones with this configuerationzonefile
(String, Default: undef): zonefile name, (will be used for all zones)zone_dir
(File Path, Default: undef): override default zone path
Defined knot::remote
used to define remote serveres these are used later to configure the system
Parameters
address4
(Optional[Variant[Tea::Ipv4, Tea::Ipv4_cidr]]): ipv4 address or prefix for this remoteaddress6
(Optional[Variant[Tea::Ipv6, Tea::Ipv6_cidr]]): ipv6 address or prefix for this remotetsig_name
: (Optional[String]): nsd::tsig to useport
: (Tea::Port, Default: 53): port use to talk to remote.
Facts
Fact knot_version
Determins the version of knot by parsing the output of knot -v
Limitations
This module has been tested on:
- Ubuntu 14.04
- FreeBSD 10
Development
Pull requests welcome but please also update documentation and tests.
2018-02-12 0.3.7
- add additional syntax checking
2018-02-09 0.3.6
- Feature: Support mod-rrl when knot is 2.4 or greater
2017-09-26 0.3.5
- fix dependencies
2017-09-26 0.3.4
- update
get_exported_titles
so it returns a sorted array
2017-09-26 0.3.3
- Fix version string in knot 2.x. if hide_version is set to false then version.server queries will recive the string hidden. in future version we should extend this with the abbility to pass a string
2017-09-26 0.3.2
- use correct knotc arguments
2017-09-26 0.3.1
- use apt::pin to pin knot1 if force_knot is used
2017-09-22 0.3.0
- add support for knot 2.x.
2017-08-16 0.2.8
- change the name of the remote acl to allow localhost acls in other parts of knot
2017-08-16 0.2.7
- Add restart command to check config before restarting
- Remove rouge comma
- updated spec tests
- added gitlab-ci tests
2017-07-27 0.2.6
- Remove a sparse comma
2017-07-27 0.2.5
- Add acceptance tests to check notifies are working
2017-07-26 0.2.4
- Change how we handle exported resources so they are all added/removed in one run
2017-04-26 0.2.3
- FIX: never use TSIG for notifies. this was the default in previosu versions. in future versions we will make tsig configueration more flexible
2017-04-26 0.2.2
- FIX: missing notify in statments
2017-04-10 0.2.1
- Fix a few typos
- Add NOKEY support
2017-04-06 0.2.0
- Complete rewrite of the zones hash.
- depricated the old $tsig hash now all hashs have to be defined in $tsisg and then refrenced by name in the remotes
- added new nsd::remotes define. allows you to define data about remote servers and then refrence them by name where ever a zone paramter would require a server e.g. masters, provide_xfrs, notifis etc
- added default_tsig_name. this specifies which nsd::tsig should be used by default
- added default_masters. this specifies an array of nsd::remote to use by default
- added default_provide_xfrs. this specifies an array of nsd::remote to use by default
2016-08-08 0.1.3
- fix variable scope for future parser
2016-05-06 0.1.2
- Fix refrence to nsd::tsig which should have been knot::tsig
- Fix refrence to nsd::file which should have been knot::file
- add support for slave addresses
- refactor config names and update rspec test
2016-05-06 0.1.1
- Add support for exporting nagis check
2016-05-06 0.1.0
- Initial Release
Dependencies
- puppetlabs-stdlib (>= 4.11.0 <5.0.0)
- puppetlabs-concat (>= 4.0.0 <5.0.0)
- puppetlabs-apt (>= 2.2.2 <5.0.0)
- icann-tea (>= 0.2.13 <1.0.0)
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "{}" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright {yyyy} {name of copyright owner} Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.