Bv9ARM.ch03.html 20.2 KB
Newer Older
1
2
3
4
5
6
<HTML
><HEAD
><TITLE
>Nameserver Configuration</TITLE
><META
NAME="GENERATOR"
Andreas Gustafsson's avatar
Andreas Gustafsson committed
7
CONTENT="Modular DocBook HTML Stylesheet Version 1.41"><LINK
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
REL="HOME"
HREF="Bv9ARM.html"><LINK
REL="PREVIOUS"
TITLE="BIND Resource Requirements"
HREF="Bv9ARM.ch02.html"><LINK
REL="NEXT"
TITLE="Advanced Concepts"
HREF="Bv9ARM.ch04.html"></HEAD
><BODY
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
></TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="Bv9ARM.ch02.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="Bv9ARM.ch04.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="chapter"
><H1
><A
NAME="ch03"
>Chapter 3. Nameserver Configuration</A
></H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>3.1. <A
HREF="Bv9ARM.ch03.html#sample_configuration"
>Sample Configurations</A
></DT
><DT
>3.2. <A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
83
HREF="Bv9ARM.ch03.html#AEN285"
84
85
86
87
88
89
90
91
92
>Load Balancing</A
></DT
><DT
>3.3. <A
HREF="Bv9ARM.ch03.html#notify"
>Notify</A
></DT
><DT
>3.4. <A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
93
HREF="Bv9ARM.ch03.html#AEN373"
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
>Nameserver Operations</A
></DT
></DL
></DIV
><P
>In this section we provide some suggested configurations along
with guidelines for their use. We also address the topic of reasonable
option setting.</P
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="sample_configuration"
>3.1. Sample Configurations</A
></H1
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
115
NAME="AEN275"
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
>3.1.1. A Caching-only Nameserver</A
></H2
><P
>The following sample configuration is appropriate for a caching-only
name server for use by clients internal to a corporation.  All queries
from outside clients are refused.</P
><PRE
CLASS="programlisting"
>&#13;// Two corporate subnets we wish to allow queries from.
acl "corpnets" { 192.168.4.0/24; 192.168.7.0/24; };
options {
     directory "/etc/namedb";		// Working directory
     pid-file "named.pid";		// Put pid file in working dir
     allow-query { "corpnets"; };
};
// Root server hints
zone "." { type hint; file "root.hint"; };
// Provide a reverse mapping for the loopback address 127.0.0.1
zone "0.0.127.in-addr.arpa" {
     type master;
     file "localhost.rev";
     notify no;
};
</PRE
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
146
NAME="AEN279"
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
>3.1.2. An Authoritative-only Nameserver</A
></H2
><P
>This sample configuration is for an authoritative-only server
that is the master server for "<TT
CLASS="filename"
>example.com</TT
>"
and a slave for the subdomain "<TT
CLASS="filename"
>eng.example.com</TT
>".</P
><PRE
CLASS="programlisting"
>&#13;options {
     directory "/etc/namedb";		// Working directory
     pid-file "named.pid";		// Put pid file in working dir
     allow-query { any; };		// This is the default
     recursion no;			// Do not provide recursive service
};
// Root server hints
zone "." { type hint; file "root.hint"; };

// Provide a reverse mapping for the loopback address 127.0.0.1
zone "0.0.127.in-addr.arpa" {
     type master;
     file "localhost.rev";
     notify no;
};
// We are the master server for example.com
zone "example.com" {
     type master;
     file "example.com.db";
     // IP addresses of slave servers allowed to transfer example.com
     allow-transfer {
          192.168.4.14;
          192.168.5.53;
     };
};
// We are a slave server for eng.example.com
zone "eng.example.com" {
     type slave;
     file "eng.example.com.bk";
     // IP address of eng.example.com master server
     masters { 192.168.4.12; };
};
</PRE
></DIV
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
201
NAME="AEN285"
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
>3.2. Load Balancing</A
></H1
><P
>Primitive load balancing can be achieved in <SPAN
CLASS="acronym"
>DNS</SPAN
> using multiple
A records for one name.</P
><P
>For example, if you have three WWW servers with network addresses
of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the
following means that clients will connect to each machine one third
of the time:</P
><DIV
CLASS="informaltable"
><P
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><TR
><TD
WIDTH="84"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Name</P
></TD
><TD
WIDTH="48"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>TTL</P
></TD
><TD
WIDTH="72"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>CLASS</P
></TD
><TD
WIDTH="72"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>TYPE</P
></TD
><TD
WIDTH="195"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Resource Record (RR) Data</P
></TD
></TR
><TR
><TD
WIDTH="84"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>www</TT
></P
></TD
><TD
WIDTH="48"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>600</TT
></P
></TD
><TD
WIDTH="72"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>IN</TT
></P
></TD
><TD
WIDTH="72"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>A</TT
></P
></TD
><TD
WIDTH="195"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>10.0.0.1</TT
></P
></TD
></TR
><TR
><TD
WIDTH="84"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
></P
></TD
><TD
WIDTH="48"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>600</TT
></P
></TD
><TD
WIDTH="72"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>IN</TT
></P
></TD
><TD
WIDTH="72"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>A</TT
></P
></TD
><TD
WIDTH="195"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>10.0.0.2</TT
></P
></TD
></TR
><TR
><TD
WIDTH="84"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
></P
></TD
><TD
WIDTH="48"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>600</TT
></P
></TD
><TD
WIDTH="72"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>IN</TT
></P
></TD
><TD
WIDTH="72"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>A</TT
></P
></TD
><TD
WIDTH="195"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="literal"
>10.0.0.3</TT
></P
></TD
></TR
></TABLE
><P
></P
></DIV
><P
>When a resolver queries for these records, <SPAN
CLASS="acronym"
>BIND</SPAN
> will rotate
    them and respond to the query with the records in a different
    order.  In the example above, clients will randomly receive
    records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients
    will use the first record returned and discard the rest.</P
><P
>For more detail on ordering responses, check the
    <B
CLASS="command"
>rrset-order</B
> substatement in the
    <B
CLASS="command"
>options</B
431
432
> statement, see
    <A
433
434
435
436
HREF="Bv9ARM.ch06.html#rrset_ordering"
><I
>RRset Ordering</I
></A
437
438
>.
    This substatement is not supported in
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
    <SPAN
CLASS="acronym"
>BIND</SPAN
> 9, and only the ordering scheme described above is
    available.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="notify"
>3.3. Notify</A
></H1
><P
><SPAN
CLASS="acronym"
>DNS</SPAN
> Notify is a mechanism that allows master nameservers to
    notify their slave servers of changes to a zone's data. In
    response to a <B
CLASS="command"
>NOTIFY</B
> from a master server, the
    slave will check to see that its version of the zone is the
    current version and, if not, initiate a transfer.</P
><P
><SPAN
CLASS="acronym"
>DNS</SPAN
>
    Notify is fully documented in RFC 1996. See also the description
    of the zone option <B
CLASS="command"
>also-notify</B
474
>, see <A
475
HREF="Bv9ARM.ch06.html#zone_transfers"
Andreas Gustafsson's avatar
Andreas Gustafsson committed
476
>Section 6.2.14.7</A
477
478
479
480
>. For more information about
    <B
CLASS="command"
>notify</B
481
>, see <A
482
HREF="Bv9ARM.ch06.html#boolean_options"
Andreas Gustafsson's avatar
Andreas Gustafsson committed
483
>Section 6.2.14.1</A
484
485
486
487
488
489
490
>.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
491
NAME="AEN373"
492
493
494
495
496
497
498
>3.4. Nameserver Operations</A
></H1
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
499
NAME="AEN375"
500
501
502
503
504
505
506
507
508
509
510
511
>3.4.1. Tools for Use With the Nameserver Daemon</A
></H2
><P
>There are several indispensable diagnostic, administrative
and monitoring tools available to the system administrator for controlling
and debugging the nameserver daemon. We describe several in this
section </P
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
512
NAME="AEN378"
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
>3.4.1.1. Diagnostic Tools</A
></H3
><P
></P
><DL
><DT
><B
CLASS="command"
>dig</B
></DT
><DD
><P
>The domain information groper (<B
CLASS="command"
>dig</B
>) is
a command line tool that can be used to gather information from
the Domain Name System servers. Dig has two modes: simple interactive
mode for a single query, and batch mode which executes a query for
each in a list of several query lines. All query options are accessible
from the command line.</P
><P
><B
CLASS="command"
>dig</B
>  [@<TT
CLASS="replaceable"
><I
>server</I
></TT
>]  <TT
CLASS="replaceable"
><I
>domain</I
></TT
>  [<TT
CLASS="replaceable"
><I
>query-type</I
></TT
>] [<TT
CLASS="replaceable"
><I
>query-class</I
></TT
>] [+<TT
CLASS="replaceable"
><I
>query-option</I
></TT
>] [-<TT
CLASS="replaceable"
><I
>dig-option</I
></TT
>] [%<TT
CLASS="replaceable"
><I
>comment</I
></TT
>]</P
><P
>The usual simple use of dig will take the form</P
><P
><B
CLASS="command"
>dig @server domain query-type query-class</B
></P
><P
>For more information and a list of available commands and
options, see the <B
CLASS="command"
>dig</B
> man page.</P
></DD
><DT
><B
CLASS="command"
>host</B
></DT
><DD
><P
>The <B
CLASS="command"
>host</B
> utility
provides a simple <SPAN
CLASS="acronym"
>DNS</SPAN
> lookup using a command-line interface for
looking up Internet hostnames. By default, the utility converts
between host names and Internet addresses, but its functionality
can be extended with the use of options.</P
><P
><B
CLASS="command"
>host</B
>  [-aCdlrTwv] [-c <TT
CLASS="replaceable"
><I
>class</I
></TT
>] [-N <TT
CLASS="replaceable"
><I
>ndots</I
></TT
>] [-t <TT
CLASS="replaceable"
><I
>type</I
></TT
>] [-W <TT
CLASS="replaceable"
><I
>timeout</I
></TT
>] [-R <TT
CLASS="replaceable"
><I
>retries</I
></TT
>]  <TT
CLASS="replaceable"
><I
>hostname</I
></TT
>  [<TT
CLASS="replaceable"
><I
>server</I
></TT
>]</P
><P
>For more information and a list of available commands and
options, see the <B
CLASS="command"
>host</B
> man page.</P
></DD
><DT
><B
CLASS="command"
>nslookup</B
></DT
><DD
><P
><B
CLASS="command"
>nslookup</B
> is a program used to query Internet
domain nameservers. <B
CLASS="command"
>nslookup</B
> has two modes: interactive
and non-interactive. Interactive mode allows the user to query nameservers
for information about various hosts and domains or to print a list
of hosts in a domain. Non-interactive mode is used to print just
the name and requested information for a host or domain.</P
><P
><B
CLASS="command"
>nslookup</B
>  [-option...] [<TT
CLASS="replaceable"
><I
>host-to-find</I
></TT
> | -  [server]]</P
><P
>Interactive mode is entered when no arguments are given (the
default nameserver will be used) or when the first argument is a
hyphen (`-') and the second argument is the host name or Internet address
of a nameserver.</P
><P
>Non-interactive mode is used when the name or Internet address
of the host to be looked up is given as the first argument. The
optional second argument specifies the host name or address of a nameserver.</P
><P
>Due to its arcane user interface and frequently inconsistent
behavior, we do not recommend the use of <B
CLASS="command"
>nslookup</B
>.
Use <B
CLASS="command"
>dig</B
> instead.</P
></DD
></DL
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
709
NAME="admin_tools"
710
711
712
713
714
715
716
717
718
>3.4.1.2. Administrative Tools</A
></H3
><P
>Administrative tools play an integral part in the management
of a server.</P
><P
></P
><DL
><DT
719
720
><A
NAME="rndc"
721
722
723
><B
CLASS="command"
>rndc</B
724
></A
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
></DT
><DD
><P
>The remote name daemon control
              (<B
CLASS="command"
>rndc</B
>) program allows the system
              administrator to control the operation of a nameserver.
              If you run <B
CLASS="command"
>rndc</B
> without any options
              it will display a usage message as follows:</P
><P
><B
CLASS="command"
>rndc</B
>  [-c <TT
CLASS="replaceable"
><I
>config</I
></TT
>] [-s <TT
CLASS="replaceable"
><I
>server</I
></TT
>] [-p <TT
CLASS="replaceable"
><I
>port</I
></TT
758
759
760
761
762
>] [-v <TT
CLASS="replaceable"
><I
>view</I
></TT
763
764
765
766
767
>] [-y <TT
CLASS="replaceable"
><I
>key</I
></TT
768
769
770
771
772
>] [-z <TT
CLASS="replaceable"
><I
>zone</I
></TT
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
>]  <TT
CLASS="replaceable"
><I
>command</I
></TT
>  [<TT
CLASS="replaceable"
><I
>command</I
></TT
>...]</P
><P
><B
CLASS="command"
>command</B
> is one of the following
              for <B
CLASS="command"
>named</B
>:</P
><DIV
CLASS="informaltable"
><P
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13;<P
><TT
CLASS="userinput"
><B
>status</B
></TT
><SUP
>a</SUP
></P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Display ps(1) status of named.</P
></TD
></TR
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="userinput"
><B
>dumpdb</B
></TT
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
835
HREF="#FTN.nyi1"
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
>[a]</A
></P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Dump database and cache to /var/tmp/named_dump.db.</P
></TD
></TR
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="userinput"
><B
856
857
858
859
860
861
862
863
864
>refresh</B
></TT
></P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
865
>Force a refresh of specified zone.</P
866
867
868
869
870
871
872
873
874
875
876
></TD
></TR
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="userinput"
><B
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
>reload</B
></TT
></P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Reload configuration file and zones.</P
></TD
></TR
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="userinput"
><B
>stats</B
></TT
></P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Dump statistics to /var/tmp/named.stats.</P
></TD
></TR
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="userinput"
><B
>trace</B
></TT
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
922
HREF="#FTN.nyi1"
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
>[a]</A
></P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Increment debugging level by one.</P
></TD
></TR
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13;<P
><TT
CLASS="userinput"
><B
>notrace</B
></TT
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
946
HREF="#FTN.nyi1"
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
>[a]</A
>
</P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Set debugging level to 0.</P
></TD
></TR
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="userinput"
><B
>querylog</B
></TT
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
971
HREF="#FTN.nyi1"
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
>[a]</A
></P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Toggle query logging.</P
></TD
></TR
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="userinput"
><B
>stop</B
></TT
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
995
HREF="#FTN.nyi1"
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
>[a]</A
></P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Stop the server.</P
></TD
></TR
><TR
><TD
WIDTH="144"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><TT
CLASS="userinput"
><B
>restart</B
></TT
><A
Andreas Gustafsson's avatar
Andreas Gustafsson committed
1019
HREF="#FTN.nyi1"
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
>[a]</A
></P
></TD
><TD
WIDTH="288"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Restart the server.</P
></TD
></TR
><TR
><TD
COLSPAN="2"
>Notes:<BR><A
NAME="FTN.nyi1"
Andreas Gustafsson's avatar
Andreas Gustafsson committed
1036
>a</A
1037
1038
1039
1040
1041
1042
1043
>not yet implemented<BR></TD
></TR
></TABLE
><P
></P
></DIV
><P
1044
>As noted above, only a limited number of commands are
1045
              available in <SPAN
1046
1047
CLASS="acronym"
>BIND</SPAN
1048
> 9.1. The other
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
              commands, and more, are planned to be implemented for
              future releases.</P
><P
>A configuration file is required, since all
              communication with the server is authenticated with
              digital signatures that rely on a shared secret, and
              there is no way to provide that secret other than with a
              configuration file.  The default location for the
              <B
CLASS="command"
>rndc</B
> configuration file is
              <TT
CLASS="filename"
>/etc/rndc.conf</TT
>, but an alternate
              location can be specified with the <TT
CLASS="option"
>-c</TT
>
              option.</P
><P
>The format of the configuration file is similar to
              that of <TT
CLASS="filename"
>named.conf</TT
>, but limited to
              only three statements, the <B
CLASS="command"
>options{}</B
>,
              <B
CLASS="command"
>key{}</B
> and <B
CLASS="command"
>server{}</B
>
              statements.  These statements are what associate the
              secret keys to the servers with which they are meant to
              be shared.  The order of statements is not
              significant.</P
><P
>The <B
CLASS="command"
>options{}</B
> statement has two clauses: <B
CLASS="command"
>default-server</B
> and <B
CLASS="command"
>default-key</B
>. <B
CLASS="command"
>default-server</B
> takes a
host name or address argument  and represents the server that will
be contacted if no <TT
CLASS="option"
>-s</TT
>
option is provided on the command line.  <B
CLASS="command"
>default-key</B
> takes
the name of key as its argument, as defined by a <B
CLASS="command"
>key{}</B
> statement.
 In the future a <B
CLASS="command"
>default-port</B
> clause will be
added to specify the port to which <B
CLASS="command"
>rndc</B
> should
connect.</P
><P
>The <B
CLASS="command"
>key{}</B
> statement names a key with its
string argument. The string is required by the server to be a valid
domain name, though it need not actually be hierarchical; thus,
a string like "<TT
CLASS="userinput"
><B
>rndc_key</B
></TT
>" is a valid name.
The <B
CLASS="command"
>key{}</B
> statement has two clauses: <B
CLASS="command"
>algorithm</B
> and <B
CLASS="command"
>secret</B
>.
 While the configuration parser will accept any string as the argument
to algorithm, currently only the string "<TT
CLASS="userinput"
><B
>hmac-md5</B
></TT
>"
has any meaning.  The secret is a base-64 encoded string, typically
generated with either <B
CLASS="command"
>dnssec-keygen</B
> or <B
CLASS="command"
>mmencode</B
>.</P
><P
>The <B
CLASS="command"
>server{}</B
> statement uses the key clause
to associate a <B
CLASS="command"
>key{}</B
>-defined key with a server.
 The argument to the <B
CLASS="command"
>server{}</B
> statement is a
host name or address (addresses must be double quoted).  The argument
to the key clause is the name of the key as defined by the <B
CLASS="command"
>key{}</B
> statement.
 A <B
CLASS="command"
>port</B
> clause will be added to a future release
to specify the port to which <B
CLASS="command"
>rndc</B
> should connect
on the given server.</P
><P
>A sample minimal configuration file is as follows:</P
><PRE
CLASS="programlisting"
>&#13;key rndc_key {
     algorithm "hmac-md5";
     secret "c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";
};
options {
     default-server localhost;
     default-key    rndc_key;
};
</PRE
><P
>This file, if installed as <TT
CLASS="filename"
>/etc/rndc.conf</TT
>,
would allow the command:</P
><P
><TT
CLASS="prompt"
>$ </TT
><TT
CLASS="userinput"
><B
>rndc reload</B
></TT
></P
><P
>to connect to 127.0.0.1 port 953 and cause the nameserver
to reload, if a nameserver on the local machine were running with
following controls statements:</P
><PRE
CLASS="programlisting"
>&#13;controls {
		inet 127.0.0.1 allow { localhost; } keys { rndc_key; };
};
</PRE
><P
>and it had an identical key statement for
<TT
CLASS="literal"
>rndc_key</TT
>.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
1246
NAME="AEN607"
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
>3.4.2. Signals</A
></H2
><P
>Certain UNIX signals cause the name server to take specific
actions, as described in the following table.  These signals can
be sent using the <B
CLASS="command"
>kill</B
> command.</P
><DIV
CLASS="informaltable"
><P
></P
><TABLE
BORDER="1"
CLASS="CALSTABLE"
><TR
><TD
WIDTH="108"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><B
CLASS="command"
>SIGHUP</B
></P
></TD
><TD
WIDTH="384"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Causes the server to read <TT
CLASS="filename"
>named.conf</TT
> and
reload the database. </P
></TD
></TR
><TR
><TD
WIDTH="108"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
><B
CLASS="command"
>SIGTERM</B
></P
></TD
><TD
WIDTH="384"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Causes the server to clean up and exit.</P
></TD
></TR
><TR
><TD
WIDTH="108"
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13;<P
><B
CLASS="command"
>SIGINT</B
></P
>
</TD
><TD
WIDTH="384"
ALIGN="LEFT"
VALIGN="MIDDLE"
><P
>Causes the server to clean up and exit.</P
></TD
></TR
></TABLE
><P
></P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="Bv9ARM.ch02.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Bv9ARM.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="Bv9ARM.ch04.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><SPAN
CLASS="acronym"
>BIND</SPAN
> Resource Requirements</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Advanced Concepts</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>