DOCSLIB.ORG

Opendnssec 1.4.8 Debian 4.1.2, Centos 6.7 Integration Guide: Opendnssec 1.4.8

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Opendnssec 1.4.8 Debian 4.1.2, Centos 6.7 Integration Guide: Opendnssec 1.4.8 Integration Guide OpenDNSSEC 1.4.8 Debian 4.1.2, CentOS 6.7 Integration Guide: OpenDNSSEC 1.4.8 Imprint copyright 2016 Utimaco IS GmbH Germanusstrasse 4 D-52080 Aachen Germany phone +49 (0)241 / 1696-200 fax +49 (0)241 / 1696-199 web http://hsm.utimaco.com email [email protected] document version 1.2.0 date January 2016 author System Engineering HSM document no. IG_OpenDNSSEC all rights reserved No part of this documentation may be reproduced in any form (printing, photocopy or according to any other process) without the written approval of Utimaco IS GmbH or be processed, reproduced or distributed using electronic systems. Utimaco IS GmbH reserves the right to modify or amend the documentation at any time without prior notice. Utimaco IS GmbH assumes no liability for typographical errors and damages incurred due to them. All trademarks and registered trademarks are the property of their respective owners. Contents 1 Introduction 4 2 Overview 4 3 Requirements 5 3.1 Tested Operating Systems ................................... 5 4 Procedures 6 4.1 Install CryptoServer Hardware ................................. 6 4.2 Install SecurityServer Software ................................ 6 4.3 Configure PKCS#11 R2 ..................................... 6 4.3.1 PKCS#11 R2 Slot Initialization ............................ 6 4.4 Setup OpenDNSSEC ...................................... 7 4.4.1 Configure OpenDNSSEC ................................ 7 4.4.2 Integration Test ..................................... 8 4.4.3 Sign a Domain Zone .................................. 10 5 Further Information 14 Integration Guide: OpenDNSSEC 1.4.8 1 Introduction This paper provides an integration guide explaining how to integrate a Hardware Security Module (HSM) – CryptoServer – with OpenDNSSEC 1.4.8 on a Linux operating system platform. Thereby OpenDNSSEC provides a complete zone signing system which operates on HSM automatically. Con- figuration details – especially to domain name system configuration – that go beyond normal con- figuration for the integration of hardware security module are not explained in this document. For further information to configure and setup e.g. BIND for a domain name system, it is referred to the documents and information of ISC1. 2 Overview The Domain Name System (DNS) is a hierarchical naming system built on a distributed database for computers, services, or any resource connected to the Internet or a private network. Most im- portantly, it translates domain names meaningful to human-readable identifiers into the numerical identifiers associated with networking equipment for the purpose of locating and addressing these devices worldwide. Often the Domain Name System is compared with the phone book of the worldwide internet. The orig- inal design of the Domain Name System did not include any security. Instead, it was developed as a simple scalable distributed system. The Domain Name System Security Extensions (DNSSEC) at- tempts to add security, while maintaining backwards compatibility to the existing Domain Name Sys- tem. The RFC 3833 attempts to document some of the known threats to the DNS and how DNSSEC tries to responds to those threats. DNSSEC was designed to protect Internet resolvers from forged DNS data, such as that created by e.g. DNS cache poisoning. All answers from DNSSEC enabled domain name system are digitally signed. By verifying the digital signature, a DNS resolver is able to check if the information is correct and complete to the information on the authoritative domain name server. While protecting IP addresses is the immediate concern for many users, DNSSEC can protect other information such as general- purpose cryptographic certificates too. Basically cryptographic keys are used to sign domain name related informations. The keys require extensively protection against being stolen or corrupted. A 1http://www.isc.org Page 4 hardware security module is the best solution in maintaining highest security and performance for the protection of those keys. The CryptoServer is a hardware security module developed by Utimaco IS GmbH , i.e. a physically pro- tected specialized computer unit designed to perform sensitive cryptographic tasks and to securely manage cryptographic keys and data. In a CryptoServer security system security-relevant actions can be executed and security relevant information can be stored. It can be used as a universal, indepen- dent security component for heterogeneous computer systems. 3 Requirements Ensure that you have a copy of the CryptoServer Administration Guide and the CryptoServer PKCS#11 R2 Interface. You should also have prepared an installed Linux operating system (ker- nel 2.6). If you are using PCIe card also compile and install the necessary driver for that card. This guide assumes that a Debian based Linux distribution is used. Software- and Hardware Requirements HSM Model Utimaco CryptoServer CSe-Series/Se-Series PCIe Utimaco CryptoServer CSe-Series/Se-Series LAN REINER SCT cyberJack e-com HSM Firmware Utimaco CryptoServer 3.30.0 Software Utimaco CryptoServer 3.30.0 OpenDNSSEC 1.4.8 3.1 Tested Operating Systems The interoperability of the CryptoServer solution, an operating system and the OpenDNSSEC have been tested successfully for the following combinations: Operating System CryptoServer OpenDNSSEC PCI Support Ethernet Support Version Version Debian 4.1.2 x86/amd64 3.00.2 1.3.0b1 Yes Yes CentOS 6.7 x86/amd64 3.30.0 1.4.8 Yes Yes Page 5 Integration Guide: OpenDNSSEC 1.4.8 4 Procedures To integrate the CryptoServer with OpenDNSSEC and verify the functionality, complete the following steps: 1. Install CryptoServer hardware 2. Install CryptoServer software 3. Configure PKCS#11 R2 4. Setup OpenDNSSEC 4.1 Install CryptoServer Hardware For more information on commonly installing and setting up CryptoServer PCIe/LAN, see the docu- mentation CryptoServer PCIe/LAN Operating and Installation Manual[3, 4]. There is no need to install any software specific for running CryptoServer. The CryptoServer comes with an already preinstalled set of firmware software. 4.2 Install SecurityServer Software The SecurityServer software – this includes administrative and library software – has to be installed on your computer system manually. To install the necessary PKCS#11 R2 libraries it is referred to the CryptoServer PKCS#11vR2 Developer Guide[1]. Further configuration steps are explained next. 4.3 Configure PKCS#11 R2 The PKCS#11 R2 library and configuration files for Linux operating system have to be installed man- ually. For further installations steps, please refer to QuickStart Guide PKCS#11 R2 [2]. 4.3.1 PKCS#11 R2 Slot Initialization Initialize a PKCS#11 R2 slot to store the necessary cryptographic keys used for OpenDNSSEC later in this document. CONSOLE # p11tool2 Login=ADMIN,:cs2:cyb:USB0 slot=0 Label=OpenDNSSEC InitToken=123456 # p11tool2 slot=0 LoginSO=123456 InitPin=utimaco123 Page 6 Here the InitPin parameter determines the PKCS#11 R2 user pin of a slot. This pin will be used later in this document for the PKCS#11 R2 user authentication. 4.4 Setup OpenDNSSEC Currently the OpenDNSSEC software is available as software package but only in the unstable branch of Debian. Therefore we are going to build OpenDNSSEC from source code. To build OpenDNSSEC suc- cessfully, it is necessary to install several open-source packages OpenDNSSEC depends on. Further information to dependencies can be found at their web site2. Make sure that you install all required software using e.g. apt-get or aptitude and gem. If some packages are still missing while configuring OpenDNSSEC, rerun configure after installing the proper packages. 1. Download and extract the sources for OpenDNSSEC 1.4.8.3 2. Install required packages listed at http://www.opendnssec.org/documentation/using-opendnssec/. 3. Configure : CONSOLE # ./configure 4. Build and install : CONSOLE # make # make install 4.4.1 Configure OpenDNSSEC After a successful installation of OpenDNSSEC several configuration files must be adjusted. The changes concern the configuration of HSM, location of zone files and signing policies. For the inte- gration we require to adjust the contents of the file conf.xml only. Among other configuration things – which are not part of this documentation – it contains a repository section. OpenDNSSEC manages keys in so called repositories. OpenDNSSEC has two types of repositories. They differ in their manner of storage of keys. We use the PKCS#11 R2 type here because will store all keys within the CryptoServer. We only are going to adjust the repository section to connect to the HSM. All 2http://www.opendnssec.org/documentation/using-opendnssec/ 3http://www.opendnssec.org/download/ Page 7 Integration Guide: OpenDNSSEC 1.4.8 other adjustment we not described here and it is referred to documentation . Adapt the configuration file conf.xml as follows: 1. Locate the repository section in /etc/opendnssec/conf.xml: <Repository name= ”SoftHSM”> <Module>/usr/local/lib/libsofthsm.so</Module> <TokenLabel>OpenDNSSEC</TokenLabel> <PIN>1234</PIN> </Repository> 2. Replace the name of the repository such as: <Repository name= ”UtimacoHSM”> The repository name is often later used as parameter of OpenDNSSEC commands. Most of the commands we will see in chapter 4.4.2. 3. Provide the location of the PKCS#11 R2 library as module information: <Module>/usr/lib/libcs2_pkcs11.so</Module> 4. Adjust the values for PKCS#11 R2 token label and PKCS#11 R2 the user pin. Use the informa- tion you have entered in chapter 4.3.1 e.g. <TokenLabel>OpenDNSSEC</TokenLabel> <PIN>utimaco123</PIN>
Load more

Recommended publications
  • DNS / DNSSEC Workshop
    1/22/18 DNS / DNSSEC Workshop Hong Kong 22-24 January 2018 Issue Date: Revision: Overview • DNS Overview • BIND DNS Configuration • Recursive and Forward DNS • Reverse DNS • Troubleshooting • DNS Security Overview • DNS Transactions • DNS Security Extensions (DNSSec) • DNSSec Key Management and Automation 2 1 1/22/18 Overview • DNS Overview • BIND DNS Configuration • Recursive and Forward DNS • Reverse DNS • Troubleshooting • DNS Security Overview • DNS Transactions • DNS Security Extensions (DNSSec) • DNSSec Key Management and Automation 3 Domain Name System • A lookup mechanism for translating objects into otHer objects – Mapping names to numbers and vice versa • A globally distributed, loosely coHerent, scalable, reliable, dynamic database • Comprised of tHree components – A “name space” – Servers making tHat name space available – Resolvers (clients) query tHe servers about tHe name space • A critical piece of tHe Internet infrastructure 4 2 1/22/18 IP Addresses vs Domain Names The Internet DNS www.apnic.net202.112.0.46 2001:0400:: 2001:0C00:8888::My Computer www.apnic.net2001:0400:: 5 Old Solution: hosts.txt • A centrally-maintained file, distributed to all Hosts on tHe Internet • Issues witH Having just one file – Becomes Huge after some time – Needs frequent copying to ALL Hosts – Consistency // hosts.txt – Always out-of-date SERVER1 128.4.13.9 WEBMAIL 4.98.133.7 – Name uniqueness FTPHOST 200.10.194.33 – Single point of administration THis feature still exists: [Unix] /etc/Hosts [Windows] c:\windows\Hosts 6 3 1/22/18 DNS Features • Global distribution – SHares tHe load and administration • Loose CoHerency – GeograpHically distributed, but still coHerent • Scalability – can add DNS servers witHout affecting tHe entire DNS • Reliability • Dynamicity – Modify and update data dynamically 7 DNS Features • DNS is a client-server application • Requests and responses are normally sent in UDP packets, port 53 • Occasionally uses TCP, port 53 – for very large requests, e.g.
    [Show full text]
  • Domain Name Systems-Based Electronic Mail Security
    DRAFT NIST CYBERSECURITY PRACTICE GUIDE DOMAIN NAME SYSTEMS-BASED ELECTRONIC MAIL SECURITY Scott Rose William C. Barker Santos Jha Chinedum Irrechukwu Karen Waltermire NIST SPECIAL PUBLICATION 1800-6 (INCLUDING PARTS A, B, C) ADDITIONAL CONTENT: https://nccoe.nist.gov/projects/building_blocks/ DRAFT NIST Special Publication 1800-6 NIST Cybersecurity Practice Guide DOMAIN NAME SYSTEMS- BASED ELECTRONIC MAIL SECURITY 1800-6A Scott Rose Executive Summary Information Technology Laboratory National Institute of Standards and Technology 1800-6B Approach, Architecture, and William C. Barker Security Characteristics Dakota Consulting For CIOs, CSOs, and Security Managers Silver Spring, MD 1800-6C Santos Jha How-To Guides Chinedum Irrechukwu For Security Engineers The MITRE Corporation McLean, VA Karen Waltermire National Cybersecurity Center of Excellence National Institute of Standards and Technology November 2016 U.S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Willie May, Under Secretary of Commerce for Standards and Technology and Director DRAFT DISCLAIMER Certain commercial entities, equipment, products, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST or NCCoE, nor is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. National Institute of Standards and Technology Special Publication 1800-6 Natl Inst. Stand. Technol. Spec. Publ. 1800-6, 221 pages (November 2016) CODEN: NSPUE2 Organizations are encouraged to review all draft publications during public comment periods and provide feedback. All publications from NIST’s National Cybersecurity Center of Excellence are available at http://nccoe.nist.gov.
    [Show full text]
  • BIND 9 Administrator Reference Manual
    BIND 9 Administrator Reference Manual BIND 9.11.23 (Extended Support Version) Copyright (C) 2000-2020 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/. Internet Systems Consortium, Inc. PO Box 360 Newmarket, NH 03857 USA https://www.isc.org/ Contents 1 Introduction 1 1.1 Scope of Document . .1 1.2 Organization of This Document . .1 1.3 Conventions Used in This Document . .1 1.4 The Domain Name System (DNS) . .2 DNS Fundamentals . .2 Domains and Domain Names . .2 Zones . .3 Authoritative Name Servers . .3 The Primary Server . .3 Secondary Servers . .4 Stealth Servers . .4 Caching Name Servers . .4 Forwarding . .5 Name Servers in Multiple Roles . .5 2 BIND Resource Requirements7 2.1 Hardware requirements . .7 2.2 CPU Requirements . .7 2.3 Memory Requirements . .7 2.4 Name Server-Intensive Environment Issues . .7 2.5 Supported Operating Systems . .8 iii BIND 9.11.23 CONTENTS CONTENTS 3 Name Server Configuration9 3.1 Sample Configurations . .9 A Caching-only Name Server . .9 An Authoritative-only Name Server . .9 3.2 Load Balancing . 10 3.3 Name Server Operations . 11 Tools for Use With the Name Server Daemon . 11 Diagnostic Tools . 11 Administrative Tools . 12 Signals . 13 4 Advanced DNS Features 15 4.1 Notify . 15 4.2 Dynamic Update . 15 The Journal File . 16 4.3 Incremental Zone Transfers (IXFR) . 16 4.4 Split DNS .
    [Show full text]
  • Domain Name Systems-Based Electronic Mail Security
    DRAFT NIST CYBERSECURITY PRACTICE GUIDE DOMAIN NAME SYSTEMS-BASED ELECTRONIC MAIL SECURITY How-To Guides For Security Engineers Scott Rose William Barker Santos Jha Chinedum Irrechukwu Karen Waltermire NIST SPECIAL PUBLICATION 1800-6C DRAFT NIST Special Publication 1800-6C NIST Cybersecurity Practice Guide DOMAIN NAME SYSTEMS- BASED ELECTRONIC MAIL SECURITY 1800-6C Scott Rose How-To Guides Information Technology Laboratory For Security Engineers National Institute of Standards and Technology William C. Barker Dakota Consulting Silver Spring, MD Santos Jha Chinedum Irrechukwu The MITRE Corporation McLean, VA Karen Waltermire National Cybersecurity Center of Excellence National Institute of Standards and Technology November 2016 U.S. Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Willie May, Under Secretary of Commerce for Standards and Technology and Director DRAFT DISCLAIMER Certain commercial entities, equipment, products, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST or NCCoE, nor is it intended to imply that the entities, equipment, products, or materials are necessarily the best available for the purpose. National Institute of Standards and Technology Special Publication 1800-6C Natl Inst. Stand. Technol. Spec. Publ. 1800-6C, 144 pages (November 2016) CODEN: NSPUE2 Organizations are encouraged to review all draft publications during
    [Show full text]
  • BIND 9 Administrator Reference Manual
    BIND 9 Administrator Reference Manual BIND 9.11.31 (Extended Support Version) Copyright (C) 2000-2021 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/. Internet Systems Consortium, Inc. PO Box 360 Newmarket, NH 03857 USA https://www.isc.org/ Contents 1 Introduction 1 1.1 Scope of Document . .1 1.2 Organization of This Document . .1 1.3 Conventions Used in This Document . .1 1.4 The Domain Name System (DNS) . .2 DNS Fundamentals . .2 Domains and Domain Names . .2 Zones . .3 Authoritative Name Servers . .3 The Primary Server . .3 Secondary Servers . .4 Stealth Servers . .4 Caching Name Servers . .4 Forwarding . .5 Name Servers in Multiple Roles . .5 2 BIND Resource Requirements7 2.1 Hardware requirements . .7 2.2 CPU Requirements . .7 2.3 Memory Requirements . .7 2.4 Name Server-Intensive Environment Issues . .7 2.5 Supported Operating Systems . .8 iii BIND 9.11.31 CONTENTS CONTENTS 3 Name Server Configuration9 3.1 Sample Configurations . .9 A Caching-only Name Server . .9 An Authoritative-only Name Server . .9 3.2 Load Balancing . 10 3.3 Name Server Operations . 11 Tools for Use With the Name Server Daemon . 11 Diagnostic Tools . 11 Administrative Tools . 12 Signals . 13 4 Advanced DNS Features 15 4.1 Notify . 15 4.2 Dynamic Update . 15 The Journal File . 16 4.3 Incremental Zone Transfers (IXFR) . 16 4.4 Split DNS .
    [Show full text]
  • Installer Et Utiliser Opendnssec
    Installer et utiliser OpenDNSSEC. Laurent Archambault <[email protected]> Installer et utiliser OpenDNSSEC. par Laurent Archambault Copyright © 2009 Laurent Archambault. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". http://www.gnu.org/licenses/ fdl.html Table des matières Contexte ....................................................................................................................... iv 1. Installer les composants. ................................................................................................. 1 Les composants via une distribution Gnu/Linux. ............................................................. 1 Les autres composants. ........................................................................................... 1 dnsruby ................................................................................................... 1 ldns ........................................................................................................ 1 Botan ...................................................................................................... 1 Les composants « OpenDNSSEC ». ............................................................................ 2 OpenDNSSEC. ....................................................................................................
    [Show full text]
  • Opendnssec.Training.2012.03.Pdf
    OpenDNSSEC training Opening 2 March 2012 Creative Commons Attribution-ShareAlike 3.0 Unported License 1 Agenda Time: Day 1: 10:00 – 17:00, Day 2: 09:00 – 16:00 • Introduction to DNSSEC and the OpenDNSSEC application • Prerequisites for running OpenDNSSEC and description of the lab environment • Hardware Security Modules • SoftHSM installation and initialization • Configuration files for ODS, conf.xml , kasp.xml and zonelist.xml • Running OpenDNSSEC • Testing • Integration • Monitoring • Recovery planning • Operational practices 2 March 2012 Creative Commons Attribution-ShareAlike 3.0 Unported License 2 Introduction • Who am I? 2 March 2012 Creative Commons Attribution-ShareAlike 3.0 Unported License 3 Introduction • Who are you? • Any experience with DNSSEC? • What are your expectations? 2 March 2012 Creative Commons Attribution-ShareAlike 3.0 Unported License 4 Goals • Understanding of DNSSEC • OpenDNSSEC • Install • Configure • Sign zones • Integrate with your environment • Basic troubleshooting 2 March 2012 Creative Commons Attribution-ShareAlike 3.0 Unported License 5 Lab environment • Amazon Elastic Compute Cloud (EC2) • One teacher server running odslab.se • Two servers per group • Resolver – resolverX.odslab.se • Name server – nsX.odslab.se • One domain per group • groupX.odslab.se 2 March 2012 Creative Commons Attribution-ShareAlike 3.0 Unported License 6 The lab • Handouts with lab instructions • Most of the labs are introduced by a presentation • Group numbers and login credentials are handed out by the teacher 2 March 2012 Creative Commons Attribution-ShareAlike 3.0 Unported License 7 OpenDNSSEC training Uploading the DS RR 2 March 2012 Creative Commons Attribution-ShareAlike 3.0 Unported License 8 Head start • We need to create a chain-of-trust to our test domain, odslab.se.
    [Show full text]
  • Diamond-HSM™ Prototype Manual
    Diamond Key Security Diamond-HSM™ Prototype Manual Change Log Date Description 11/28/2018 Initial document. 12/17/2018 Added LED description and detailed information on console commands. 12/19/2018 Terminology fixes and removed ‘DRAFT’ watermark. Page 1 of 36 Contents Change Log ...............................................................................................................................................................1 Contents ...................................................................................................................................................................2 1. Introduction ......................................................................................................................................................5 1.1. Acknowledgements ..................................................................................................................................5 1.2. Scope of Document ..................................................................................................................................5 1.3. Organization of This Document ................................................................................................................5 1.4. Definitions ................................................................................................................................................5 2. Diamond-HSM Description and Functionality ..................................................................................................7 2.1. CrypTech
    [Show full text]
  • Powerdns-Authoritative.Pdf
    PowerDNS Authoritative Server Documentation PowerDNS.COM BV Sep 24, 2021 CONTENTS 1 PowerDNS Authoritative Nameserver1 1.1 Getting Started............................................1 1.2 Getting Support...........................................1 1.2.1 My information is confidential, must I send it to the mailing list, discuss it on IRC, or post it in a GitHub ticket?..................................1 1.2.2 I have a question!......................................2 1.2.3 What details should I supply?................................2 1.2.4 I found a bug!........................................2 1.2.5 I found a security issue!...................................2 1.2.6 I have a good idea for a feature!..............................2 2 Installing PowerDNS 3 2.1 Binary Packages...........................................3 2.1.1 Debian-based Systems...................................3 2.1.2 Redhat-based Systems...................................3 2.1.3 FreeBSD..........................................3 2.1.4 Mac OS X..........................................4 2.2 After installation...........................................4 3 Upgrade Notes 5 3.1 4.4.x to 4.5.0 or master........................................5 3.1.1 Record type changes....................................5 3.1.2 Changed options......................................5 3.2 4.3.x to 4.4.0.............................................6 3.2.1 Latency calculation changes................................6 3.2.2 MySQL character set detection...............................6 3.2.3 Record
    [Show full text]
  • Opendnssec Initial Deployment Guide W
    OpenDNSSEC Initial Deployment Guide W. Matthijs Mekking November 17, 2014 Abstract OpenDNSSEC is a policy-based zone signer that automates the process of keeping track of DNSSEC [1], [3], [2] keys and the signing of zones. The goal of the project is to make DNSSEC easy to deploy. The software has a lot of configuration options that can be tweaked but that requires some knowledge about DNSSEC. Some users might just want to deploy DNSSEC without knowing what is under the hood. If you are that person, this deploy- ment guide will help you set up OpenDNSSEC and provide simple guidelines for adding and removing zones, as well as some other quick guides. Contents 1 Starting OpenDNSSEC for the first time 1 1.1 Dependencies . .2 1.1.1 SoftHSM . .2 1.2 Installation . .2 1.3 Configuration . .3 1.3.1 Key and Signing Policy (KASP) . .3 2 Adding a zone 4 2.1 OpenDNSSEC as a bump-in-the-wire . .5 3 Publish the DS 5 4 Migrate a zone to OpenDNSSEC 6 4.1 Export the keys . .7 4.2 Add the zone to OpenDNSSEC . .7 5 Feedback 8 6 Acknowledgements 8 1 Starting OpenDNSSEC for the first time OpenDNSSEC [4] will run on most Linux, BSD and Solaris operating systems. The community provides binary packages for several platforms which makes installation even more easy. This guide however assumes those packages are not available. 1 STARTING OPENDNSSEC FOR THE FIRST TIME 1.1 Dependencies If you have found a nice system to run OpenDNSSEC on, it is time to install its dependen- cies.
    [Show full text]
  • Combined Product Notices
    Combined Product Notices MarkLogic® Server 10.0‐7 and supporting products Copyright © 2021 MarkLogic Corporation. MarkLogic and the MarkLogic logo are trademarks or registered trademarks of MarkLogic Corporation in the United States and other countries. All other trademarks are the property of their respective owners. MarkLogic technology is protected by one or more U.S. Patent Nos. 7,127,469, 7,171,404, 7,756,858, 7,962,474, 8,935,267, 8,892,599, 9,092,507, 10,108,742, 10,114,975, 10,311,088, 10,325,106, 10,339,337, 10,394,889, 10,503,780, and 10,769,209. To the extent required by the applicable open source license, a complete machine‐readable copy of the source code corresponding to such code is available upon request. This offer is valid to anyone in receipt of this information and shall expire three years following the date of the final distribution of this product version by MarkLogic. To obtain such source code, send an email to [email protected]. Please specify the product and version for which you are requesting source code. The following software may be included in this project (last updated May 23, 2021): @angular-mdl/core 6.0.1 Attribution Statements http://mseemann.io/angular2-mdl/ Copyright Statements Copyright (c) 2014-2016 Google, Inc. http://angular.io License Text (http://spdx.org/licenses/MIT) Made available under the MIT License. See Appendix for full text. Source materials are available for download at: https://github.com/mseemann/angular2-mdl @angular-mdl/popover 6.0.0 Attribution Statements https://www.npmjs.com/package/@angular-mdl/popover Copyright Statements Copyright (c) 2016 Michael Seemann License Text (http://spdx.org/licenses/MIT) Made available under the MIT License.
    [Show full text]
  • BIND 9 Administrator Reference Manual
    BIND 9 Administrator Reference Manual BIND 9.16.0 (Stable Release) Copyright (C) 2000-2020 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/. Internet Systems Consortium 950 Charter Street Redwood City, California USA https://www.isc.org/ Contents 1 Introduction 1 1.1 Scope of Document . .1 1.2 Organization of This Document . .1 1.3 Conventions Used in This Document . .1 1.4 The Domain Name System (DNS) . .2 DNS Fundamentals . .2 Domains and Domain Names . .2 Zones . .3 Authoritative Name Servers . .3 The Primary Master . .3 Slave Servers . .4 Stealth Servers . .4 Caching Name Servers . .4 Forwarding . .5 Name Servers in Multiple Roles . .5 2 BIND Resource Requirements7 2.1 Hardware requirements . .7 2.2 CPU Requirements . .7 2.3 Memory Requirements . .7 2.4 Name Server Intensive Environment Issues . .7 2.5 Supported Operating Systems . .8 iii BIND 9.16.0 CONTENTS CONTENTS 3 Name Server Configuration9 3.1 Sample Configurations . .9 A Caching-only Name Server . .9 An Authoritative-only Name Server . .9 3.2 Load Balancing . 10 3.3 Name Server Operations . 11 Tools for Use With the Name Server Daemon . 11 Diagnostic Tools . 11 Administrative Tools . 12 Signals . 13 3.4 Plugins . 14 Configuring Plugins . 14 Developing Plugins . 14 4 Advanced DNS Features 17 4.1 Notify . 17 4.2 Dynamic Update . 17 The journal file . 18 4.3 Incremental Zone Transfers (IXFR) .
    [Show full text]