Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
The ONE Campaign to make poverty history

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 144 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

rndc.conf



SYNOPSIS

       rndc.conf


DESCRIPTION

       rndc.conf  is  the configuration file for rndc, the BIND 9
       name server control  utility.  This  file  has  a  similar
       structure   and   syntax  to  named.conf.  Statements  are
       enclosed in  braces  and  terminated  with  a  semi-colon.
       Clauses  in the statements are also semi-colon terminated.
       The usual comment styles are supported:

       C style: /* */

       C++ style: // to end of line

       Unix style: # to end of line

       rndc.conf is much simpler than named.conf. The  file  uses
       three statements: an options statement, a server statement
       and a key statement.

       The  options  statement  contains  three   clauses.    The
       default-server  clause  is followed by the name or address
       of a name server. This host will  be  used  when  no  name
       server  is  given  as an argument to rndc. The default-key
       clause is followed by the name of a key which  is  identi­
       fied  by  a  key statement. If no keyid is provided on the
       rndc command line, and no key clause is found in a  match­
       ing  server  statement,  this  default key will be used to
       authenticate the  server's  commands  and  responses.  The
       default-port  clause is followed by the port to connect to
       on the remote name server. If no port option  is  provided
       on the rndc command line, and no port clause is found in a
       matching server statement, this default port will be  used
       to connect.

       After  the server keyword, the server statement includes a
       string which is the hostname or address for a name server.
       The  statement has two possible clauses: key and port. The
       key name must match the name of a  key  statement  in  the
       file. The port number specifies the port to connect to.

       The  key  statement begins with an identifying string, the
       name of the key. The statement has two clauses.  algorithm
       identifies  the encryption algorithm for rndc to use; cur­
       rently only HMAC-MD5 is supported. This is followed  by  a
       secret  clause  which contains the base-64 encoding of the
       algorithm's encryption key. The base-64 string is enclosed
       in double quotes.

       There  are  two common ways to generate the base-64 string
       for the secret. The BIND 9  program  rndc-confgen  can  be
             };

             key samplekey {
               algorithm       hmac-md5;
               secret          "c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";
             };

       In  the above example, rndc will by default use the server
       at localhost (127.0.0.1) and  the  key  called  samplekey.
       Commands  to  the  localhost server will use the samplekey
       key, which must also be defined in the server's configura­
       tion file with the same name and secret. The key statement
       indicates that samplekey uses the HMAC-MD5  algorithm  and
       its  secret  clause  contains  the base-64 encoding of the
       HMAC-MD5 secret enclosed in double quotes.

       To generate a random secret with rndc-confgen:

       rndc-confgen

       A complete rndc.conf file, including the  randomly  gener­
       ated  key,  will  be  written to the standard output. Com­
       mented out key and controls statements for named.conf  are
       also printed.

       To generate a base-64 secret with mmencode:

       echo "known plaintext for a secret" | mmencode


NAME SERVER CONFIGURATION

       The  name server must be configured to accept rndc connec­
       tions and to recognize the key specified in the  rndc.conf
       file, using the controls statement in named.conf.  See the
       sections on the controls statement in the BIND 9  Adminis­
       trator Reference Manual for details.


SEE ALSO

       rndc(8),  rndc-confgen(8), mmencode(1), BIND 9 Administra­
       tor Reference Manual.


AUTHOR

       Internet Software Consortium

BIND9                     June 30, 2000              RNDC.CONF(5)
  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can get all the latest Site and Linux news by checking out our news page.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.04 Seconds