Book Image

CentOS 7 Server Deployment Cookbook

By : Timothy Boronczyk, IRAKLI NADAREISHVILI
Book Image

CentOS 7 Server Deployment Cookbook

By: Timothy Boronczyk, IRAKLI NADAREISHVILI

Overview of this book

CentOS is derived from Red Hat Enterprise Linux (RHEL) sources and is widely used as a Linux server. This book will help you to better configure and manage Linux servers in varying scenarios and business requirements. Starting with installing CentOS, this book will walk you through the networking aspects of CentOS. You will then learn how to manage users and their permissions, software installs, disks, filesystems, and so on. You’ll then see how to secure connection to remotely access a desktop and work with databases. Toward the end, you will find out how to manage DNS, e-mails, web servers, and more. You will also learn to detect threats by monitoring network intrusion. Finally, the book will cover virtualization techniques that will help you make the most of CentOS.
Table of Contents (18 chapters)
CentOS 7 Server Deployment Cookbook
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Configuring rndc to control BIND


rndc is the client utility for managing BIND servers. However, before you can use it, both rndc and BIND need to be configured. This recipe shows you how to configure them and then shows you a few commands for managing the server's cache.

Getting ready

This recipe requires a CentOS system with BIND installed and configured as described in the previous recipes. Administrative privileges are also required, either by logging in with the root account or through the use of sudo.

How to do it...

Follow these steps to configure rndc:

  1. Use the rndc-confgen utility to generate the necessary key file:

    rndc-confgen -a -c /etc/rndc.key
    
  2. Create the /etc/rndc.conf file with the following content:

           include "/etc/rndc.key";
           options {
               default-key "rndc-key";
               default-server 127.0.0.1;
               default-port 953;
           };
    
  3. Ensure the correct ownership and access permissions for rndc.key and rndc.conf:

    chown root.named...