1 Frequently Asked Questions about BIND 9
3 Copyright © 2004-2008 Internet Systems Consortium, Inc. ("ISC")
5 Copyright © 2000-2003 Internet Software Consortium.
7 -----------------------------------------------------------------------
9 1. Compilation and Installation Questions
11 Q: I'm trying to compile BIND 9, and "make" is failing due to files not
14 A: Using a parallel or distributed "make" to build BIND 9 is not
15 supported, and doesn't work. If you are using one of these, use normal
16 make or gmake instead.
18 Q: Isn't "make install" supposed to generate a default named.conf?
22 Long Answer: There really isn't a default configuration which fits any
23 site perfectly. There are lots of decisions that need to be made and
24 there is no consensus on what the defaults should be. For example
25 FreeBSD uses /etc/namedb as the location where the configuration files
26 for named are stored. Others use /var/named.
28 What addresses to listen on? For a laptop on the move a lot you may
29 only want to listen on the loop back interfaces.
31 Who do you offer recursive service to? Is there are firewall to
32 consider? If so is it stateless or stateful. Are you directly on the
33 Internet? Are you on a private network? Are you on a NAT'd network? The
34 answers to all these questions change how you configure even a caching
37 2. Configuration and Setup Questions
39 Q: Why does named log the warning message "no TTL specified - using SOA
42 A: Your zone file is illegal according to RFC1035. It must either have a
47 at the beginning, or the first record in it must have a TTL field, like
48 the "84600" in this example:
50 example.com. 86400 IN SOA ns hostmaster ( 1 3600 1800 1814400 3600 )
52 Q: Why do I get errors like "dns_zone_load: zone foo/IN: loading master
53 file bar: ran out of space"?
55 A: This is often caused by TXT records with missing close quotes. Check
56 that all TXT records containing quoted strings have both open and close
59 Q: How do I restrict people from looking up the server version?
61 A: Put a "version" option containing something other than the real version
62 in the "options" section of named.conf. Note doing this will not
63 prevent attacks and may impede people trying to diagnose problems with
64 your server. Also it is possible to "fingerprint" nameservers to
65 determine their version.
67 Q: How do I restrict only remote users from looking up the server version?
69 A: The following view statement will intercept lookups as the internal
70 view that holds the version information will be matched last. The
71 caveats of the previous answer still apply, of course.
74 match-clients { <those to be refused>; };
75 allow-query { none; };
78 file "/dev/null"; // or any empty file
82 Q: What do "no source of entropy found" or "could not open entropy source
85 A: The server requires a source of entropy to perform certain operations,
86 mostly DNSSEC related. These messages indicate that you have no source
87 of entropy. On systems with /dev/random or an equivalent, it is used by
88 default. A source of entropy can also be defined using the
89 random-device option in named.conf.
91 Q: I'm trying to use TSIG to authenticate dynamic updates or zone
92 transfers. I'm sure I have the keys set up correctly, but the server is
93 rejecting the TSIG. Why?
95 A: This may be a clock skew problem. Check that the the clocks on the
96 client and server are properly synchronised (e.g., using ntp).
98 Q: I see a log message like the following. Why?
100 couldn't open pid file '/var/run/named.pid': Permission denied
102 A: You are most likely running named as a non-root user, and that user
103 does not have permission to write in /var/run. The common ways of
104 fixing this are to create a /var/run/named directory owned by the named
105 user and set pid-file to "/var/run/named/named.pid", or set pid-file to
106 "named.pid", which will put the file in the directory specified by the
107 directory option (which, in this case, must be writable by the named
110 Q: I can query the nameserver from the nameserver but not from other
113 A: This is usually the result of the firewall configuration stopping the
114 queries and / or the replies.
116 Q: How can I make a server a slave for both an internal and an external
117 view at the same time? When I tried, both views on the slave were
118 transferred from the same view on the master.
120 A: You will need to give the master and slave multiple IP addresses and
121 use those to make sure you reach the correct view on the other machine.
123 Master: 10.0.1.1 (internal), 10.0.1.2 (external, IP alias)
125 match-clients { !10.0.1.2; !10.0.1.4; 10.0.1/24; };
126 notify-source 10.0.1.1;
127 transfer-source 10.0.1.1;
128 query-source address 10.0.1.1;
130 match-clients { any; };
131 recursion no; // don't offer recursion to the world
132 notify-source 10.0.1.2;
133 transfer-source 10.0.1.2;
134 query-source address 10.0.1.2;
136 Slave: 10.0.1.3 (internal), 10.0.1.4 (external, IP alias)
138 match-clients { !10.0.1.2; !10.0.1.4; 10.0.1/24; };
139 notify-source 10.0.1.3;
140 transfer-source 10.0.1.3;
141 query-source address 10.0.1.3;
143 match-clients { any; };
144 recursion no; // don't offer recursion to the world
145 notify-source 10.0.1.4;
146 transfer-source 10.0.1.4;
147 query-source address 10.0.1.4;
149 You put the external address on the alias so that all the other dns
150 clients on these boxes see the internal view by default.
152 A: BIND 9.3 and later: Use TSIG to select the appropriate view.
160 match-clients { !key external; 10.0.1/24; };
164 match-clients { key external; any; };
165 server 10.0.1.2 { keys external; };
176 match-clients { !key external; 10.0.1/24; };
180 match-clients { key external; any; };
181 server 10.0.1.1 { keys external; };
186 Q: I get error messages like "multiple RRs of singleton type" and "CNAME
187 and other data" when transferring a zone. What does this mean?
189 A: These indicate a malformed master zone. You can identify the exact
190 records involved by transferring the zone using dig then running
191 named-checkzone on it.
193 dig axfr example.com @master-server > tmp
194 named-checkzone example.com tmp
196 A CNAME record cannot exist with the same name as another record except
197 for the DNSSEC records which prove its existence (NSEC).
199 RFC 1034, Section 3.6.2: "If a CNAME RR is present at a node, no other
200 data should be present; this ensures that the data for a canonical name
201 and its aliases cannot be different. This rule also insures that a
202 cached CNAME can be used without checking with an authoritative server
205 Q: I get error messages like "named.conf:99: unexpected end of input"
206 where 99 is the last line of named.conf.
208 A: There are unbalanced quotes in named.conf.
210 A: Some text editors (notepad and wordpad) fail to put a line title
211 indication (e.g. CR/LF) on the last line of a text file. This can be
212 fixed by "adding" a blank line to the end of the file. Named expects to
213 see EOF immediately after EOL and treats text files where this is not
216 Q: How do I share a dynamic zone between multiple views?
218 A: You choose one view to be master and the second a slave and transfer
219 the zone between views.
233 match-clients { !key external; 10.0.1/24; };
235 /* Deliver notify messages to external view. */
240 file "internal/example.db";
241 allow-update { key mykey; };
242 notify-also { 10.0.1.1; };
247 match-clients { key external; any; };
250 file "external/example.db";
251 masters { 10.0.1.1; };
252 transfer-source { 10.0.1.1; };
253 // allow-update-forwarding { any; };
254 // allow-notify { ... };
258 Q: I get a error message like "zone wireless.ietf56.ietf.org/IN: loading
259 master file primaries/wireless.ietf56.ietf.org: no owner".
261 A: This error is produced when a line in the master file contains leading
262 white space (tab/space) but the is no current record owner name to
263 inherit the name from. Usually this is the result of putting white
264 space before a comment, forgetting the "@" for the SOA record, or
265 indenting the master file.
267 Q: Why are my logs in GMT (UTC).
269 A: You are running chrooted (-t) and have not supplied local timezone
270 information in the chroot area.
272 FreeBSD: /etc/localtime
273 Solaris: /etc/TIMEZONE and /usr/share/lib/zoneinfo
274 OSF: /etc/zoneinfo/localtime
276 See also tzset(3) and zic(8).
278 Q: I get "rndc: connect failed: connection refused" when I try to run
281 A: This is usually a configuration error.
283 First ensure that named is running and no errors are being reported at
284 startup (/var/log/messages or equivalent). Running "named -g <usual
285 arguments>" from a title can help at this point.
287 Secondly ensure that named is configured to use rndc either by
288 "rndc-confgen -a", rndc-confgen or manually. The Administrators
289 Reference manual has details on how to do this.
291 Old versions of rndc-confgen used localhost rather than 127.0.0.1 in /
292 etc/rndc.conf for the default server. Update /etc/rndc.conf if
293 necessary so that the default server listed in /etc/rndc.conf matches
294 the addresses used in named.conf. "localhost" has two address
297 If you use "rndc-confgen -a" and named is running with -t or -u ensure
298 that /etc/rndc.conf has the correct ownership and that a copy is in the
299 chroot area. You can do this by re-running "rndc-confgen -a" with
300 appropriate -t and -u arguments.
302 Q: I get "transfer of 'example.net/IN' from 192.168.4.12#53: failed while
303 receiving responses: permission denied" error messages.
305 A: These indicate a filesystem permission error preventing named creating
306 / renaming the temporary file. These will usually also have other
307 associated error messages like
309 "dumping master file: sl/tmp-XXXX5il3sQ: open: permission denied"
311 Named needs write permission on the directory containing the file.
312 Named writes the new cache file to a temporary file then renames it to
313 the name specified in named.conf to ensure that the contents are always
314 complete. This is to prevent named loading a partial zone in the event
315 of power failure or similar interrupting the write of the master file.
317 Note file names are relative to the directory specified in options and
318 any chroot directory ([<chroot dir>/][<options dir>]).
320 If named is invoked as "named -t /chroot/DNS" with the following
321 named.conf then "/chroot/DNS/var/named/sl" needs to be writable by the
322 user named is running as.
325 directory "/var/named";
330 file "sl/example.net";
331 masters { 192.168.4.12; };
334 Q: I want to forward all DNS queries from my caching nameserver to another
335 server. But there are some domains which have to be served locally, via
338 How do I achieve this ?
342 forwarders { <ip.of.primary.nameserver>; };
345 zone "sbl-xbl.spamhaus.org" {
346 type forward; forward only;
347 forwarders { <ip.of.rbldns.server> port 530; };
350 zone "list.dsbl.org" {
351 type forward; forward only;
352 forwarders { <ip.of.rbldns.server> port 530; };
356 Q: Can you help me understand how BIND 9 uses memory to store DNS zones?
358 Some times it seems to take several times the amount of memory it needs
361 A: When reloading a zone named my have multiple copies of the zone in
362 memory at one time. The zone it is serving and the one it is loading.
363 If reloads are ultra fast it can have more still.
365 e.g. Ones that are transferring out, the one that it is serving and the
368 BIND 8 destroyed the zone before loading and also killed off outgoing
369 transfers of the zone.
371 The new strategy allows slaves to get copies of the new zone regardless
372 of how often the master is loaded compared to the transfer time. The
373 slave might skip some intermediate versions but the transfers will
374 complete and it will keep reasonably in sync with the master.
376 The new strategy also allows the master to recover from syntax and
377 other errors in the master file as it still has an in-core copy of the
380 Q: I want to use IPv6 locally but I don't have a external IPv6 connection.
381 External lookups are slow.
383 A: You can use server clauses to stop named making external lookups over
386 server fd81:ec6c:bd62::/48 { bogus no; }; // site ULA prefix
387 server ::/0 { bogus yes; };
389 3. Operations Questions
391 Q: How to change the nameservers for a zone?
393 A: Step 1: Ensure all nameservers, new and old, are serving the same zone
396 Step 2: Work out the maximum TTL of the NS RRset in the parent and
397 child zones. This is the time it will take caches to be clear of a
398 particular version of the NS RRset. If you are just removing
399 nameservers you can skip to Step 6.
401 Step 3: Add new nameservers to the NS RRset for the zone and wait until
402 all the servers for the zone are answering with this new NS RRset.
404 Step 4: Inform the parent zone of the new NS RRset then wait for all
405 the parent servers to be answering with the new NS RRset.
407 Step 5: Wait for cache to be clear of the old NS RRset. See Step 2 for
408 how long. If you are just adding nameservers you are done.
410 Step 6: Remove any old nameservers from the zones NS RRset and wait for
411 all the servers for the zone to be serving the new NS RRset.
413 Step 7: Inform the parent zone of the new NS RRset then wait for all
414 the parent servers to be answering with the new NS RRset.
416 Step 8: Wait for cache to be clear of the old NS RRset. See Step 2 for
419 Step 9: Turn off the old nameservers or remove the zone entry from the
420 configuration of the old nameservers.
422 Step 10: Increment the serial number and wait for the change to be
423 visible in all nameservers for the zone. This ensures that zone
424 transfers are still working after the old servers are decommissioned.
426 Note: the above procedure is designed to be transparent to dns clients.
427 Decommissioning the old servers too early will result in some clients
428 not being able to look up answers in the zone.
430 Note: while it is possible to run the addition and removal stages
431 together it is not recommended.
435 Q: I keep getting log messages like the following. Why?
437 Dec 4 23:47:59 client 10.0.0.1#1355: updating zone 'example.com/IN':
438 update failed: 'RRset exists (value dependent)' prerequisite not
441 A: DNS updates allow the update request to test to see if certain
442 conditions are met prior to proceeding with the update. The message
443 above is saying that conditions were not met and the update is not
444 proceeding. See doc/rfc/rfc2136.txt for more details on prerequisites.
446 Q: I keep getting log messages like the following. Why?
448 Jun 21 12:00:00.000 client 10.0.0.1#1234: update denied
450 A: Someone is trying to update your DNS data using the RFC2136 Dynamic
451 Update protocol. Windows 2000 machines have a habit of sending dynamic
452 update requests to DNS servers without being specifically configured to
453 do so. If the update requests are coming from a Windows 2000 machine,
454 see <http://support.microsoft.com/support/kb/articles/q246/8/04.asp>
455 for information about how to turn them off.
457 Q: When I do a "dig . ns", many of the A records for the root servers are
460 A: This is normal and harmless. It is a somewhat confusing side effect of
461 the way BIND 9 does RFC2181 trust ranking and of the efforts BIND 9
462 makes to avoid promoting glue into answers.
464 When BIND 9 first starts up and primes its cache, it receives the root
465 server addresses as additional data in an authoritative response from a
466 root server, and these records are eligible for inclusion as additional
467 data in responses. Subsequently it receives a subset of the root server
468 addresses as additional data in a non-authoritative (referral) response
469 from a root server. This causes the addresses to now be considered
470 non-authoritative (glue) data, which is not eligible for inclusion in
473 The server does have a complete set of root server addresses cached at
474 all times, it just may not include all of them as additional data,
475 depending on whether they were last received as answers or as glue. You
476 can always look up the addresses with explicit queries like "dig
477 a.root-servers.net A".
479 Q: Why don't my zones reload when I do an "rndc reload" or SIGHUP?
481 A: A zone can be updated either by editing zone files and reloading the
482 server or by dynamic update, but not both. If you have enabled dynamic
483 update for a zone using the "allow-update" option, you are not supposed
484 to edit the zone file by hand, and the server will not attempt to
487 Q: Why is named listening on UDP port other than 53?
489 A: Named uses a system selected port to make queries of other nameservers.
490 This behaviour can be overridden by using query-source to lock down the
491 port and/or address. See also notify-source and transfer-source.
493 Q: I get warning messages like "zone example.com/IN: refresh: failure
494 trying master 1.2.3.4#53: timed out".
496 A: Check that you can make UDP queries from the slave to the master
498 dig +norec example.com soa @1.2.3.4
500 You could be generating queries faster than the slave can cope with.
501 Lower the serial query rate.
503 serial-query-rate 5; // default 20
505 Q: I don't get RRSIG's returned when I use "dig +dnssec".
507 A: You need to ensure DNSSEC is enabled (dnssec-enable yes;).
509 Q: Can a NS record refer to a CNAME.
511 A: No. The rules for glue (copies of the *address* records in the parent
512 zones) and additional section processing do not allow it to work.
514 You would have to add both the CNAME and address records (A/AAAA) as
515 glue to the parent zone and have CNAMEs be followed when doing
516 additional section processing to make it work. No nameserver
517 implementation supports either of these requirements.
519 Q: What does "RFC 1918 response from Internet for 0.0.0.10.IN-ADDR.ARPA"
522 A: If the IN-ADDR.ARPA name covered refers to a internal address space you
523 are using then you have failed to follow RFC 1918 usage rules and are
524 leaking queries to the Internet. You should establish your own zones
525 for these addresses to prevent you querying the Internet's name servers
526 for these addresses. Please see <http://as112.net/> for details of the
527 problems you are causing and the counter measures that have had to be
530 If you are not using these private addresses then a client has queried
531 for them. You can just ignore the messages, get the offending client to
532 stop sending you these messages as they are most probably leaking them
533 or setup your own zones empty zones to serve answers to these queries.
535 zone "10.IN-ADDR.ARPA" {
540 zone "16.172.IN-ADDR.ARPA" {
547 zone "31.172.IN-ADDR.ARPA" {
552 zone "168.192.IN-ADDR.ARPA" {
558 @ 10800 IN SOA <name-of-server>. <contact-email>. (
559 1 3600 1200 604800 10800 )
560 @ 10800 IN NS <name-of-server>.
564 Future versions of named are likely to do this automatically.
566 Q: Will named be affected by the 2007 changes to daylight savings rules in
569 A: No, so long as the machines internal clock (as reported by "date -u")
570 remains at UTC. The only visible change if you fail to upgrade your OS,
571 if you are in a affected area, will be that log messages will be a hour
572 out during the period where the old rules do not match the new rules.
574 For most OS's this change just means that you need to update the
575 conversion rules from UTC to local time. Normally this involves
576 updating a file in /etc (which sets the default timezone for the
577 machine) and possibly a directory which has all the conversion rules
578 for the world (e.g. /usr/share/zoneinfo). When updating the OS do not
579 forget to update any chroot areas as well. See your OS's documentation
582 The local timezone conversion rules can also be done on a individual
583 basis by setting the TZ environment variable appropriately. See your
584 OS's documentation for more details.
586 Q: Is there a bugzilla (or other tool) database that mere mortals can have
587 (read-only) access to for bind?
589 A: No. The BIND 9 bug database is kept closed for a number of reasons.
590 These include, but are not limited to, that the database contains
591 proprietory information from people reporting bugs. The database has in
592 the past and may in future contain unfixed bugs which are capable of
593 bringing down most of the Internet's DNS infrastructure.
595 The release pages for each version contain up to date lists of bugs
596 that have been fixed post release. That is as close as we can get to
597 providing a bug database.
599 Q: Why do queries for NSEC3 records fail to return the NSEC3 record?
601 A: NSEC3 records are strictly meta data and can only be returned in the
602 authority section. This is done so that signing the zone using NSEC3
603 records does not bring names into existance that do not exist in the
604 unsigned version of the zone.
606 5. Operating-System Specific Questions
610 Q: I get the following error trying to configure BIND:
612 checking if unistd.h or sys/types.h defines fd_set... no
613 configure: error: need either working unistd.h or sys/select.h
615 A: You have attempted to configure BIND with the bundled C compiler. This
616 compiler does not meet the minimum compiler requirements to for
617 building BIND. You need to install a ANSI C compiler and / or teach
618 configure how to find the ANSI C compiler. The later can be done by
619 adjusting the PATH environment variable and / or specifying the
622 ./configure CC=<compiler> ...
626 Q: Why do I get the following errors:
628 general: errno2result.c:109: unexpected error:
629 general: unable to convert errno to isc_result: 14: Bad address
630 client: UDP client handler shutting down due to fatal receive error: unexpected error
632 A: This is the result of a Linux kernel bug.
634 See: <http://marc.theaimsgroup.com/?l=linux-netdev&m=113081708031466&w=
637 Q: Why does named lock up when it attempts to connect over IPSEC tunnels?
639 A: This is due to a kernel bug where the fact that a socket is marked
640 non-blocking is ignored. It is reported that setting xfrm_larval_drop
641 to 1 helps but this may have negative side effects. See: <https://
642 bugzilla.redhat.com/show_bug.cgi?id=427629> and <http://lkml.org/lkml/
645 xfrm_larval_drop can be set to 1 by the following procedure:
647 echo "1" > proc/sys/net/core/xfrm_larval_drop
649 Q: Why do I see 5 (or more) copies of named on Linux?
651 A: Linux threads each show up as a process under ps. The approximate
652 number of threads running is n+4, where n is the number of CPUs. Note
653 that the amount of memory used is not cumulative; if each process is
654 using 10M of memory, only a total of 10M is used.
656 Newer versions of Linux's ps command hide the individual threads and
657 require -L to display them.
659 Q: Why does BIND 9 log "permission denied" errors accessing its
660 configuration files or zones on my Linux system even though it is
663 A: On Linux, BIND 9 drops most of its root privileges on startup. This
664 including the privilege to open files owned by other users. Therefore,
665 if the server is running as root, the configuration files and zone
666 files should also be owned by root.
668 Q: I get the error message "named: capset failed: Operation not permitted"
671 A: The capability module, part of "Linux Security Modules/LSM", has not
672 been loaded into the kernel. See insmod(8), modprobe(8).
674 The relevant modules can be loaded by running:
679 Q: I'm running BIND on Red Hat Enterprise Linux or Fedora Core -
681 Why can't named update slave zone database files?
683 Why can't named create DDNS journal files or update the master zones
686 Why can't named create custom log files?
688 A: Red Hat Security Enhanced Linux (SELinux) policy security protections :
690 Red Hat have adopted the National Security Agency's SELinux security
691 policy (see <http://www.nsa.gov/selinux>) and recommendations for BIND
692 security , which are more secure than running named in a chroot and
693 make use of the bind-chroot environment unnecessary .
695 By default, named is not allowed by the SELinux policy to write, create
696 or delete any files EXCEPT in these directories:
698 $ROOTDIR/var/named/slaves
699 $ROOTDIR/var/named/data
703 where $ROOTDIR may be set in /etc/sysconfig/named if bind-chroot is
706 The SELinux policy particularly does NOT allow named to modify the
707 $ROOTDIR/var/named directory, the default location for master zone
710 SELinux policy overrules file access permissions - so even if all the
711 files under /var/named have ownership named:named and mode rw-rw-r--,
712 named will still not be able to write or create files except in the
713 directories above, with SELinux in Enforcing mode.
715 So, to allow named to update slave or DDNS zone files, it is best to
716 locate them in $ROOTDIR/var/named/slaves, with named.conf zone
719 zone "slave.zone." IN {
721 file "slaves/slave.zone.db";
724 zone "ddns.zone." IN {
727 file "slaves/ddns.zone.db";
731 To allow named to create its cache dump and statistics files, for
732 example, you could use named.conf options statements such as:
736 dump-file "/var/named/data/cache_dump.db";
737 statistics-file "/var/named/data/named_stats.txt";
742 You can also tell SELinux to allow named to update any zone database
743 files, by setting the SELinux tunable boolean parameter
744 'named_write_master_zones=1', using the system-config-securitylevel
745 GUI, using the 'setsebool' command, or in /etc/selinux/targeted/
748 You can disable SELinux protection for named entirely by setting the
749 'named_disable_trans=1' SELinux tunable boolean parameter.
751 The SELinux named policy defines these SELinux contexts for named:
753 named_zone_t : for zone database files - $ROOTDIR/var/named/*
754 named_conf_t : for named configuration files - $ROOTDIR/etc/{named,rndc}.*
755 named_cache_t: for files modifiable by named - $ROOTDIR/var/{tmp,named/{slaves,data}}
758 If you want to retain use of the SELinux policy for named, and put
759 named files in different locations, you can do so by changing the
760 context of the custom file locations .
762 To create a custom configuration file location, e.g. '/root/
763 named.conf', to use with the 'named -c' option, do:
765 # chcon system_u:object_r:named_conf_t /root/named.conf
768 To create a custom modifiable named data location, e.g. '/var/log/
769 named' for a log file, do:
771 # chcon system_u:object_r:named_cache_t /var/log/named
774 To create a custom zone file location, e.g. /root/zones/, do:
776 # chcon system_u:object_r:named_zone_t /root/zones/{.,*}
779 See these man-pages for more information : selinux(8), named_selinux
780 (8), chcon(1), setsebool(8)
782 Q: Listening on individual IPv6 interfaces does not work.
784 A: This is usually due to "/proc/net/if_inet6" not being available in the
785 chroot file system. Mount another instance of "proc" in the chroot file
788 This can be be made permanent by adding a second instance to /etc/
791 proc /proc proc defaults 0 0
792 proc /var/named/proc proc defaults 0 0
796 Q: Zone transfers from my BIND 9 master to my Windows 2000 slave fail.
799 A: This may be caused by a bug in the Windows 2000 DNS server where DNS
800 messages larger than 16K are not handled properly. This can be worked
801 around by setting the option "transfer-format one-answer;". Also check
802 whether your zone contains domain names with embedded spaces or other
803 special characters, like "John\032Doe\213s\032Computer", since such
804 names have been known to cause Windows 2000 slaves to incorrectly
807 Q: I get "Error 1067" when starting named under Windows.
809 A: This is the service manager saying that named exited. You need to
810 examine the Application log in the EventViewer to find out why.
812 Common causes are that you failed to create "named.conf" (usually "C:\
813 windows\dns\etc\named.conf") or failed to specify the directory in
817 Directory "C:\windows\dns\etc";
822 Q: I have FreeBSD 4.x and "rndc-confgen -a" just sits there.
824 A: /dev/random is not configured. Use rndcontrol(8) to tell the kernel to
825 use certain interrupts as a source of random events. You can make this
826 permanent by setting rand_irqs in /etc/rc.conf.
831 See also <http://people.freebsd.org/~dougb/randomness.html>.
835 Q: How do I integrate BIND 9 and Solaris SMF
837 A: Sun has a blog entry describing how to do this.
839 <http://blogs.sun.com/roller/page/anay/Weblog?catname=%2FSolaris>
843 Q: How do I run BIND 9 on Apple Mac OS X?
845 A: If you run Tiger(Mac OS 10.4) or later then this is all you need to do:
847 % sudo rndc-confgen > /etc/rndc.conf
849 Copy the key statement from /etc/rndc.conf into /etc/rndc.key, e.g.:
853 secret "uvceheVuqf17ZwIcTydddw==";
856 Then start the relevant service:
858 % sudo service org.isc.named start
860 This is persistent upon a reboot, so you will have to do it only once.
862 A: Alternatively you can just generate /etc/rndc.key by running:
864 % sudo rndc-confgen -a
866 Then start the relevant service:
868 % sudo service org.isc.named start
870 Named will look for /etc/rndc.key when it starts if it doesn't have a
871 controls section or the existing controls are missing keys sub-clauses.
872 This is persistent upon a reboot, so you will have to do it only once.