From: Evan Hunt Date: Fri, 21 Apr 2017 02:21:54 +0000 (-0700) Subject: [master] update README, remove FAQ X-Git-Tag: v9.12.0a1~370 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=95f7e98da0d0abc6c2889c48456caf8f870d8157;p=thirdparty%2Fbind9.git [master] update README, remove FAQ 4593. [doc] Update README using markdown, remove outdated FAQ file in favor of the knowledge base. --- diff --git a/CHANGES b/CHANGES index 5804f7e4c1d..90718d53d2e 100644 --- a/CHANGES +++ b/CHANGES @@ -1,3 +1,6 @@ +4593. [doc] Update README using markdown, remove outdated FAQ + file in favor of the knowledge base. + 4592. [bug] A race condition on shutdown could trigger an assertion failure in dispatch.c. [RT #43822] @@ -13057,7 +13060,7 @@ 586. [bug] multiple views with the same name were fatal. [RT #516] - 585. [func] dns_db_addrdataset() and and dns_rdataslab_merge() + 585. [func] dns_db_addrdataset() and dns_rdataslab_merge() now support 'exact' additions in a similar manner to dns_db_subtractrdataset() and dns_rdataslab_subtract(). diff --git a/FAQ b/FAQ deleted file mode 100644 index 6a75e8af81a..00000000000 --- a/FAQ +++ /dev/null @@ -1,890 +0,0 @@ -Copyright ? 2000-2010, 2013-2016 Internet Systems Consortium, Inc. -("ISC") - ------------------------------------------------------------------------ - -1. Compilation and Installation Questions - -Q: I'm trying to compile BIND 9, and "make" is failing due to files not - being found. Why? - -A: Using a parallel or distributed "make" to build BIND 9 is not - supported, and doesn't work. If you are using one of these, use normal - make or gmake instead. - -Q: Isn't "make install" supposed to generate a default named.conf? - -A: Short Answer: No. - - Long Answer: There really isn't a default configuration which fits any - site perfectly. There are lots of decisions that need to be made and - there is no consensus on what the defaults should be. For example - FreeBSD uses /etc/namedb as the location where the configuration files - for named are stored. Others use /var/named. - - What addresses to listen on? For a laptop on the move a lot you may - only want to listen on the loop back interfaces. - - To whom do you offer recursive service? Is there a firewall to - consider? If so, is it stateless or stateful? Are you directly on the - Internet? Are you on a private network? Are you on a NAT'd network? The - answers to all these questions change how you configure even a caching - name server. - -2. Configuration and Setup Questions - -Q: Why does named log the warning message "no TTL specified - using SOA - MINTTL instead"? - -A: Your zone file is illegal according to RFC1035. It must either have a - line like: - - $TTL 86400 - - at the beginning, or the first record in it must have a TTL field, like - the "84600" in this example: - - example.com. 86400 IN SOA ns hostmaster ( 1 3600 1800 1814400 3600 ) - -Q: Why do I get errors like "dns_zone_load: zone foo/IN: loading master - file bar: ran out of space"? - -A: This is often caused by TXT records with missing close quotes. Check - that all TXT records containing quoted strings have both open and close - quotes. - -Q: How do I restrict people from looking up the server version? - -A: Put a "version" option containing something other than the real version - in the "options" section of named.conf. Note doing this will not - prevent attacks and may impede people trying to diagnose problems with - your server. Also it is possible to "fingerprint" nameservers to - determine their version. - -Q: How do I restrict only remote users from looking up the server version? - -A: The following view statement will intercept lookups as the internal - view that holds the version information will be matched last. The - caveats of the previous answer still apply, of course. - - view "chaos" chaos { - match-clients { ; }; - allow-query { none; }; - zone "." { - type hint; - file "/dev/null"; // or any empty file - }; - }; - -Q: What do "no source of entropy found" or "could not open entropy source - foo" mean? - -A: The server requires a source of entropy to perform certain operations, - mostly DNSSEC related. These messages indicate that you have no source - of entropy. On systems with /dev/random or an equivalent, it is used by - default. A source of entropy can also be defined using the - random-device option in named.conf. - -Q: I'm trying to use TSIG to authenticate dynamic updates or zone - transfers. I'm sure I have the keys set up correctly, but the server is - rejecting the TSIG. Why? - -A: This may be a clock skew problem. Check that the the clocks on the - client and server are properly synchronized (e.g., using ntp). - -Q: I see a log message like the following. Why? - - couldn't open pid file '/var/run/named.pid': Permission denied - -A: You are most likely running named as a non-root user, and that user - does not have permission to write in /var/run. The common ways of - fixing this are to create a /var/run/named directory owned by the named - user and set pid-file to "/var/run/named/named.pid", or set pid-file to - "named.pid", which will put the file in the directory specified by the - directory option (which, in this case, must be writable by the user - named is running as). - -Q: I can query the nameserver from the nameserver but not from other - machines. Why? - -A: This is usually the result of the firewall configuration stopping the - queries and / or the replies. - -Q: How can I make a server a slave for both an internal and an external - view at the same time? When I tried, both views on the slave were - transferred from the same view on the master. - -A: You will need to give the master and slave multiple IP addresses and - use those to make sure you reach the correct view on the other machine. - - Master: 10.0.1.1 (internal), 10.0.1.2 (external, IP alias) - internal: - match-clients { !10.0.1.2; !10.0.1.4; 10.0.1/24; }; - notify-source 10.0.1.1; - transfer-source 10.0.1.1; - query-source address 10.0.1.1; - external: - match-clients { any; }; - recursion no; // don't offer recursion to the world - notify-source 10.0.1.2; - transfer-source 10.0.1.2; - query-source address 10.0.1.2; - - Slave: 10.0.1.3 (internal), 10.0.1.4 (external, IP alias) - internal: - match-clients { !10.0.1.2; !10.0.1.4; 10.0.1/24; }; - notify-source 10.0.1.3; - transfer-source 10.0.1.3; - query-source address 10.0.1.3; - external: - match-clients { any; }; - recursion no; // don't offer recursion to the world - notify-source 10.0.1.4; - transfer-source 10.0.1.4; - query-source address 10.0.1.4; - - You put the external address on the alias so that all the other dns - clients on these boxes see the internal view by default. - -A: BIND 9.3 and later: Use TSIG to select the appropriate view. - - Master 10.0.1.1: - key "external" { - algorithm hmac-sha256; - secret "xxxxxxxxxxxxxxxxxxxxxxxx"; - }; - view "internal" { - match-clients { !key external; // reject message ment for the - // external view. - 10.0.1/24; }; // accept from these addresses. - ... - }; - view "external" { - match-clients { key external; any; }; - server 10.0.1.2 { keys external; }; // tag messages from the - // external view to the - // other servers for the - // view. - recursion no; - ... - }; - - Slave 10.0.1.2: - key "external" { - algorithm hmac-sha256; - secret "xxxxxxxxxxxxxxxxxxxxxxxx"; - }; - view "internal" { - match-clients { !key external; 10.0.1/24; }; - ... - }; - view "external" { - match-clients { key external; any; }; - server 10.0.1.1 { keys external; }; - recursion no; - ... - }; - -Q: I get error messages like "multiple RRs of singleton type" and "CNAME - and other data" when transferring a zone. What does this mean? - -A: These indicate a malformed master zone. You can identify the exact - records involved by transferring the zone using dig then running - named-checkzone on it. - - dig axfr example.com @master-server > tmp - named-checkzone example.com tmp - - A CNAME record cannot exist with the same name as another record except - for the DNSSEC records which prove its existence (NSEC). - - RFC 1034, Section 3.6.2: "If a CNAME RR is present at a node, no other - data should be present; this ensures that the data for a canonical name - and its aliases cannot be different. This rule also insures that a - cached CNAME can be used without checking with an authoritative server - for other RR types." - -Q: I get error messages like "named.conf:99: unexpected end of input" - where 99 is the last line of named.conf. - -A: There are unbalanced quotes in named.conf. - -A: Some text editors (notepad and wordpad) fail to put a line title - indication (e.g. CR/LF) on the last line of a text file. This can be - fixed by "adding" a blank line to the end of the file. Named expects to - see EOF immediately after EOL and treats text files where this is not - met as truncated. - -Q: How do I share a dynamic zone between multiple views? - -A: You choose one view to be master and the second a slave and transfer - the zone between views. - - Master 10.0.1.1: - key "external" { - algorithm hmac-sha256; - secret "xxxxxxxxxxxxxxxxxxxxxxxx"; - }; - - key "mykey" { - algorithm hmac-sha256; - secret "yyyyyyyyyyyyyyyyyyyyyyyy"; - }; - - view "internal" { - match-clients { !key external; 10.0.1/24; }; - server 10.0.1.1 { - /* Deliver notify messages to external view. */ - keys { external; }; - }; - zone "example.com" { - type master; - file "internal/example.db"; - allow-update { key mykey; }; - also-notify { 10.0.1.1; }; - }; - }; - - view "external" { - match-clients { key external; any; }; - zone "example.com" { - type slave; - file "external/example.db"; - masters { 10.0.1.1; }; - transfer-source 10.0.1.1; - // allow-update-forwarding { any; }; - // allow-notify { ... }; - }; - }; - -Q: I get a error message like "zone wireless.ietf56.ietf.org/IN: loading - master file primaries/wireless.ietf56.ietf.org: no owner". - -A: This error is produced when a line in the master file contains leading - white space (tab/space) but there is no current record owner name to - inherit the name from. Usually this is the result of putting white - space before a comment, forgetting the "@" for the SOA record, or - indenting the master file. - -Q: Why are my logs in GMT (UTC). - -A: You are running chrooted (-t) and have not supplied local timezone - information in the chroot area. - - FreeBSD: /etc/localtime - Solaris: /etc/TIMEZONE and /usr/share/lib/zoneinfo - OSF: /etc/zoneinfo/localtime - - See also tzset(3) and zic(8). - -Q: I get "rndc: connect failed: connection refused" when I try to run - rndc. - -A: This is usually a configuration error. - - First ensure that named is running and no errors are being reported at - startup (/var/log/messages or equivalent). Running "named -g " from a title can help at this point. - - Secondly ensure that named is configured to use rndc either by - "rndc-confgen -a", rndc-confgen or manually. The Administrators - Reference manual has details on how to do this. - - Old versions of rndc-confgen used localhost rather than 127.0.0.1 in / - etc/rndc.conf for the default server. Update /etc/rndc.conf if - necessary so that the default server listed in /etc/rndc.conf matches - the addresses used in named.conf. "localhost" has two address - (127.0.0.1 and ::1). - - If you use "rndc-confgen -a" and named is running with -t or -u ensure - that /etc/rndc.conf has the correct ownership and that a copy is in the - chroot area. You can do this by re-running "rndc-confgen -a" with - appropriate -t and -u arguments. - -Q: I get "transfer of 'example.net/IN' from 192.168.4.12#53: failed while - receiving responses: permission denied" error messages. - -A: These indicate a filesystem permission error preventing named creating - / renaming the temporary file. These will usually also have other - associated error messages like - - "dumping master file: sl/tmp-XXXX5il3sQ: open: permission denied" - - Named needs write permission on the directory containing the file. - Named writes the new cache file to a temporary file then renames it to - the name specified in named.conf to ensure that the contents are always - complete. This is to prevent named loading a partial zone in the event - of power failure or similar interrupting the write of the master file. - - Note file names are relative to the directory specified in options and - any chroot directory ([/][]). - - If named is invoked as "named -t /chroot/DNS" with the following - named.conf then "/chroot/DNS/var/named/sl" needs to be writable by the - user named is running as. - - options { - directory "/var/named"; - }; - - zone "example.net" { - type slave; - file "sl/example.net"; - masters { 192.168.4.12; }; - }; - -Q: I want to forward all DNS queries from my caching nameserver to another - server. But there are some domains which have to be served locally, via - rbldnsd. - - How do I achieve this ? - -A: options { - forward only; - forwarders { ; }; - }; - - zone "sbl-xbl.spamhaus.org" { - type forward; forward only; - forwarders { port 530; }; - }; - - zone "list.dsbl.org" { - type forward; forward only; - forwarders { port 530; }; - }; - - -Q: Can you help me understand how BIND 9 uses memory to store DNS zones? - - Some times it seems to take several times the amount of memory it needs - to store the zone. - -A: When reloading a zone named my have multiple copies of the zone in - memory at one time. The zone it is serving and the one it is loading. - If reloads are ultra fast it can have more still. - - e.g. Ones that are transferring out, the one that it is serving and the - one that is loading. - - BIND 8 destroyed the zone before loading and also killed off outgoing - transfers of the zone. - - The new strategy allows slaves to get copies of the new zone regardless - of how often the master is loaded compared to the transfer time. The - slave might skip some intermediate versions but the transfers will - complete and it will keep reasonably in sync with the master. - - The new strategy also allows the master to recover from syntax and - other errors in the master file as it still has an in-core copy of the - old contents. - -Q: I want to use IPv6 locally but I don't have a external IPv6 connection. - External lookups are slow. - -A: You can use server clauses to stop named making external lookups over - IPv6. - - server fd81:ec6c:bd62::/48 { bogus no; }; // site ULA prefix - server ::/0 { bogus yes; }; - -3. Operations Questions - -Q: How to change the nameservers for a zone? - -A: Step 1: Ensure all nameservers, new and old, are serving the same zone - content. - - Step 2: Work out the maximum TTL of the NS RRset in the parent and - child zones. This is the time it will take caches to be clear of a - particular version of the NS RRset. If you are just removing - nameservers you can skip to Step 6. - - Step 3: Add new nameservers to the NS RRset for the zone and wait until - all the servers for the zone are answering with this new NS RRset. - - Step 4: Inform the parent zone of the new NS RRset then wait for all - the parent servers to be answering with the new NS RRset. - - Step 5: Wait for cache to be clear of the old NS RRset. See Step 2 for - how long. If you are just adding nameservers you are done. - - Step 6: Remove any old nameservers from the zones NS RRset and wait for - all the servers for the zone to be serving the new NS RRset. - - Step 7: Inform the parent zone of the new NS RRset then wait for all - the parent servers to be answering with the new NS RRset. - - Step 8: Wait for cache to be clear of the old NS RRset. See Step 2 for - how long. - - Step 9: Turn off the old nameservers or remove the zone entry from the - configuration of the old nameservers. - - Step 10: Increment the serial number and wait for the change to be - visible in all nameservers for the zone. This ensures that zone - transfers are still working after the old servers are decommissioned. - - Note: the above procedure is designed to be transparent to dns clients. - Decommissioning the old servers too early will result in some clients - not being able to look up answers in the zone. - - Note: while it is possible to run the addition and removal stages - together it is not recommended. - -4. General Questions - -Q: I keep getting log messages like the following. Why? - - Dec 4 23:47:59 client 10.0.0.1#1355: updating zone 'example.com/IN': - update failed: 'RRset exists (value dependent)' prerequisite not - satisfied (NXRRSET) - -A: DNS updates allow the update request to test to see if certain - conditions are met prior to proceeding with the update. The message - above is saying that conditions were not met and the update is not - proceeding. See doc/rfc/rfc2136.txt for more details on prerequisites. - -Q: I keep getting log messages like the following. Why? - - Jun 21 12:00:00.000 client 10.0.0.1#1234: update denied - -A: Someone is trying to update your DNS data using the RFC2136 Dynamic - Update protocol. Windows 2000 machines have a habit of sending dynamic - update requests to DNS servers without being specifically configured to - do so. If the update requests are coming from a Windows 2000 machine, - see - for information about how to turn them off. - -Q: When I do a "dig . ns", many of the A records for the root servers are - missing. Why? - -A: This is normal and harmless. It is a somewhat confusing side effect of - the way BIND 9 does RFC2181 trust ranking and of the efforts BIND 9 - makes to avoid promoting glue into answers. - - When BIND 9 first starts up and primes its cache, it receives the root - server addresses as additional data in an authoritative response from a - root server, and these records are eligible for inclusion as additional - data in responses. Subsequently it receives a subset of the root server - addresses as additional data in a non-authoritative (referral) response - from a root server. This causes the addresses to now be considered - non-authoritative (glue) data, which is not eligible for inclusion in - responses. - - The server does have a complete set of root server addresses cached at - all times, it just may not include all of them as additional data, - depending on whether they were last received as answers or as glue. You - can always look up the addresses with explicit queries like "dig - a.root-servers.net A". - -Q: Why don't my zones reload when I do an "rndc reload" or SIGHUP? - -A: A zone can be updated either by editing zone files and reloading the - server or by dynamic update, but not both. If you have enabled dynamic - update for a zone using the "allow-update" option, you are not supposed - to edit the zone file by hand, and the server will not attempt to - reload it. - -Q: Why is named listening on UDP port other than 53? - -A: Named uses a system selected port to make queries of other nameservers. - This behaviour can be overridden by using query-source to lock down the - port and/or address. See also notify-source and transfer-source. - -Q: I get warning messages like "zone example.com/IN: refresh: failure - trying master 1.2.3.4#53: timed out". - -A: Check that you can make UDP queries from the slave to the master - - dig +norec example.com soa @1.2.3.4 - - You could be generating queries faster than the slave can cope with. - Lower the serial query rate. - - serial-query-rate 5; // default 20 - -Q: I don't get RRSIG's returned when I use "dig +dnssec". - -A: You need to ensure DNSSEC is enabled (dnssec-enable yes;). - -Q: Can a NS record refer to a CNAME. - -A: No. The rules for glue (copies of the *address* records in the parent - zones) and additional section processing do not allow it to work. - - You would have to add both the CNAME and address records (A/AAAA) as - glue to the parent zone and have CNAMEs be followed when doing - additional section processing to make it work. No nameserver - implementation supports either of these requirements. - -Q: What does "RFC 1918 response from Internet for 0.0.0.10.IN-ADDR.ARPA" - mean? - -A: If the IN-ADDR.ARPA name covered refers to a internal address space you - are using then you have failed to follow RFC 1918 usage rules and are - leaking queries to the Internet. You should establish your own zones - for these addresses to prevent you querying the Internet's name servers - for these addresses. Please see for details of the - problems you are causing and the counter measures that have had to be - deployed. - - If you are not using these private addresses then a client has queried - for them. You can just ignore the messages, get the offending client to - stop sending you these messages as they are most probably leaking them - or setup your own zones empty zones to serve answers to these queries. - - zone "10.IN-ADDR.ARPA" { - type master; - file "empty"; - }; - - zone "16.172.IN-ADDR.ARPA" { - type master; - file "empty"; - }; - - ... - - zone "31.172.IN-ADDR.ARPA" { - type master; - file "empty"; - }; - - zone "168.192.IN-ADDR.ARPA" { - type master; - file "empty"; - }; - - empty: - @ 10800 IN SOA . . ( - 1 3600 1200 604800 10800 ) - @ 10800 IN NS . - - Note - - Future versions of named are likely to do this automatically. - -Q: Will named be affected by the 2007 changes to daylight savings rules in - the US. - -A: No, so long as the machines internal clock (as reported by "date -u") - remains at UTC. The only visible change if you fail to upgrade your OS, - if you are in a affected area, will be that log messages will be a hour - out during the period where the old rules do not match the new rules. - - For most OS's this change just means that you need to update the - conversion rules from UTC to local time. Normally this involves - updating a file in /etc (which sets the default timezone for the - machine) and possibly a directory which has all the conversion rules - for the world (e.g. /usr/share/zoneinfo). When updating the OS do not - forget to update any chroot areas as well. See your OS's documentation - for more details. - - The local timezone conversion rules can also be done on a individual - basis by setting the TZ environment variable appropriately. See your - OS's documentation for more details. - -Q: Is there a bugzilla (or other tool) database that mere mortals can have - (read-only) access to for bind? - -A: No. The BIND 9 bug database is kept closed for a number of reasons. - These include, but are not limited to, that the database contains - proprietory information from people reporting bugs. The database has in - the past and may in future contain unfixed bugs which are capable of - bringing down most of the Internet's DNS infrastructure. - - The release pages for each version contain up to date lists of bugs - that have been fixed post release. That is as close as we can get to - providing a bug database. - -Q: Why do queries for NSEC3 records fail to return the NSEC3 record? - -A: NSEC3 records are strictly meta data and can only be returned in the - authority section. This is done so that signing the zone using NSEC3 - records does not bring names into existence that do not exist in the - unsigned version of the zone. - -5. Operating-System Specific Questions - -5.1. HPUX - -Q: I get the following error trying to configure BIND: - - checking if unistd.h or sys/types.h defines fd_set... no - configure: error: need either working unistd.h or sys/select.h - -A: You have attempted to configure BIND with the bundled C compiler. This - compiler does not meet the minimum compiler requirements to for - building BIND. You need to install a ANSI C compiler and / or teach - configure how to find the ANSI C compiler. The later can be done by - adjusting the PATH environment variable and / or specifying the - compiler via CC. - - ./configure CC= ... - -5.2. Linux - -Q: Why do I get the following errors: - - general: errno2result.c:109: unexpected error: - general: unable to convert errno to isc_result: 14: Bad address - client: UDP client handler shutting down due to fatal receive error: unexpected error - -A: This is the result of a Linux kernel bug. - - See: - -Q: Why does named lock up when it attempts to connect over IPSEC tunnels? - -A: This is due to a kernel bug where the fact that a socket is marked - non-blocking is ignored. It is reported that setting xfrm_larval_drop - to 1 helps but this may have negative side effects. See: and . - - xfrm_larval_drop can be set to 1 by the following procedure: - - echo "1" > proc/sys/net/core/xfrm_larval_drop - -Q: Why do I see 5 (or more) copies of named on Linux? - -A: Linux threads each show up as a process under ps. The approximate - number of threads running is n+4, where n is the number of CPUs. Note - that the amount of memory used is not cumulative; if each process is - using 10M of memory, only a total of 10M is used. - - Newer versions of Linux's ps command hide the individual threads and - require -L to display them. - -Q: Why does BIND 9 log "permission denied" errors accessing its - configuration files or zones on my Linux system even though it is - running as root? - -A: On Linux, BIND 9 drops most of its root privileges on startup. This - including the privilege to open files owned by other users. Therefore, - if the server is running as root, the configuration files and zone - files should also be owned by root. - -Q: I get the error message "named: capset failed: Operation not permitted" - when starting named. - -A: The capability module, part of "Linux Security Modules/LSM", has not - been loaded into the kernel. See insmod(8), modprobe(8). - - The relevant modules can be loaded by running: - - modprobe commoncap - modprobe capability - -Q: I'm running BIND on Red Hat Enterprise Linux or Fedora Core - - - Why can't named update slave zone database files? - - Why can't named create DDNS journal files or update the master zones - from journals? - - Why can't named create custom log files? - -A: Red Hat Security Enhanced Linux (SELinux) policy security protections : - - Red Hat have adopted the National Security Agency's SELinux security - policy (see ) and recommendations for BIND - security , which are more secure than running named in a chroot and - make use of the bind-chroot environment unnecessary . - - By default, named is not allowed by the SELinux policy to write, create - or delete any files EXCEPT in these directories: - - $ROOTDIR/var/named/slaves - $ROOTDIR/var/named/data - $ROOTDIR/var/tmp - - - where $ROOTDIR may be set in /etc/sysconfig/named if bind-chroot is - installed. - - The SELinux policy particularly does NOT allow named to modify the - $ROOTDIR/var/named directory, the default location for master zone - database files. - - SELinux policy overrules file access permissions - so even if all the - files under /var/named have ownership named:named and mode rw-rw-r--, - named will still not be able to write or create files except in the - directories above, with SELinux in Enforcing mode. - - So, to allow named to update slave or DDNS zone files, it is best to - locate them in $ROOTDIR/var/named/slaves, with named.conf zone - statements such as: - - zone "slave.zone." IN { - type slave; - file "slaves/slave.zone.db"; - ... - }; - zone "ddns.zone." IN { - type master; - allow-updates {...}; - file "slaves/ddns.zone.db"; - }; - - - To allow named to create its cache dump and statistics files, for - example, you could use named.conf options statements such as: - - options { - ... - dump-file "/var/named/data/cache_dump.db"; - statistics-file "/var/named/data/named_stats.txt"; - ... - }; - - - You can also tell SELinux to allow named to update any zone database - files, by setting the SELinux tunable boolean parameter - 'named_write_master_zones=1', using the system-config-securitylevel - GUI, using the 'setsebool' command, or in /etc/selinux/targeted/ - booleans. - - You can disable SELinux protection for named entirely by setting the - 'named_disable_trans=1' SELinux tunable boolean parameter. - - The SELinux named policy defines these SELinux contexts for named: - - named_zone_t : for zone database files - $ROOTDIR/var/named/* - named_conf_t : for named configuration files - $ROOTDIR/etc/{named,rndc}.* - named_cache_t: for files modifiable by named - $ROOTDIR/var/{tmp,named/{slaves,data}} - - - If you want to retain use of the SELinux policy for named, and put - named files in different locations, you can do so by changing the - context of the custom file locations . - - To create a custom configuration file location, e.g. '/root/ - named.conf', to use with the 'named -c' option, do: - - # chcon system_u:object_r:named_conf_t /root/named.conf - - - To create a custom modifiable named data location, e.g. '/var/log/ - named' for a log file, do: - - # chcon system_u:object_r:named_cache_t /var/log/named - - - To create a custom zone file location, e.g. /root/zones/, do: - - # chcon system_u:object_r:named_zone_t /root/zones/{.,*} - - - See these man-pages for more information : selinux(8), named_selinux - (8), chcon(1), setsebool(8) - -Q: I'm running BIND on Ubuntu - - - Why can't named update slave zone database files? - - Why can't named create DDNS journal files or update the master zones - from journals? - - Why can't named create custom log files? - -A: Ubuntu uses AppArmor in - addition to normal file system permissions to protect the system. - - Adjust the paths to use those specified in /etc/apparmor.d/ - usr.sbin.named or adjust /etc/apparmor.d/usr.sbin.named to allow named - to write at the location specified in named.conf. - -Q: Listening on individual IPv6 interfaces does not work. - -A: This is usually due to "/proc/net/if_inet6" not being available in the - chroot file system. Mount another instance of "proc" in the chroot file - system. - - This can be be made permanent by adding a second instance to /etc/ - fstab. - - proc /proc proc defaults 0 0 - proc /var/named/proc proc defaults 0 0 - -5.3. Windows - -Q: Zone transfers from my BIND 9 master to my Windows 2000 slave fail. - Why? - -A: This may be caused by a bug in the Windows 2000 DNS server where DNS - messages larger than 16K are not handled properly. This can be worked - around by setting the option "transfer-format one-answer;". Also check - whether your zone contains domain names with embedded spaces or other - special characters, like "John\032Doe\213s\032Computer", since such - names have been known to cause Windows 2000 slaves to incorrectly - reject the zone. - -Q: I get "Error 1067" when starting named under Windows. - -A: This is the service manager saying that named exited. You need to - examine the Application log in the EventViewer to find out why. - - Common causes are that you failed to create "named.conf" (usually "C:\ - windows\dns\etc\named.conf") or failed to specify the directory in - named.conf. - - options { - Directory "C:\windows\dns\etc"; - }; - -5.4. FreeBSD - -Q: I have FreeBSD 4.x and "rndc-confgen -a" just sits there. - -A: /dev/random is not configured. Use rndcontrol(8) to tell the kernel to - use certain interrupts as a source of random events. You can make this - permanent by setting rand_irqs in /etc/rc.conf. - - rand_irqs="3 14 15" - - See also . - -5.5. Solaris - -Q: How do I integrate BIND 9 and Solaris SMF - -A: Sun has a blog entry describing how to do this. - - - -5.6. Apple Mac OS X - -Q: How do I run BIND 9 on Apple Mac OS X? - -A: If you run Tiger(Mac OS 10.4) or later then this is all you need to do: - - % sudo rndc-confgen > /etc/rndc.conf - - Copy the key statement from /etc/rndc.conf into /etc/rndc.key, e.g.: - - key "rndc-key" { - algorithm hmac-sha256; - secret "uvceheVuqf17ZwIcTydddw=="; - }; - - Then start the relevant service: - - % sudo service org.isc.named start - - This is persistent upon a reboot, so you will have to do it only once. - -A: Alternatively you can just generate /etc/rndc.key by running: - - % sudo rndc-confgen -a - - Then start the relevant service: - - % sudo service org.isc.named start - - Named will look for /etc/rndc.key when it starts if it doesn't have a - controls section or the existing controls are missing keys sub-clauses. - This is persistent upon a reboot, so you will have to do it only once. - diff --git a/FAQ.xml b/FAQ.xml deleted file mode 100644 index 484c40fc74b..00000000000 --- a/FAQ.xml +++ /dev/null @@ -1,1598 +0,0 @@ - - - -
- - - - 2000 - 2001 - 2002 - 2003 - 2004 - 2005 - 2006 - 2007 - 2008 - 2009 - 2010 - 2013 - 2014 - 2015 - 2016 - Internet Systems Consortium, Inc. ("ISC") - - - - - Compilation and Installation Questions - - - - - I'm trying to compile BIND 9, and "make" is failing due to - files not being found. Why? - - - - - Using a parallel or distributed "make" to build BIND 9 is - not supported, and doesn't work. If you are using one of - these, use normal make or gmake instead. - - - - - - - - Isn't "make install" supposed to generate a default named.conf? - - - - - Short Answer: No. - - - Long Answer: There really isn't a default configuration which fits - any site perfectly. There are lots of decisions that need to - be made and there is no consensus on what the defaults should be. - For example FreeBSD uses /etc/namedb as the location where the - configuration files for named are stored. Others use /var/named. - - - What addresses to listen on? For a laptop on the move a lot - you may only want to listen on the loop back interfaces. - - - To whom do you offer recursive service? Is there a firewall - to consider? If so, is it stateless or stateful? Are you - directly on the Internet? Are you on a private network? Are - you on a NAT'd network? The answers - to all these questions change how you configure even a - caching name server. - - - - - - - Configuration and Setup Questions - - - - - - Why does named log the warning message no TTL specified - - using SOA MINTTL instead? - - - - - Your zone file is illegal according to RFC1035. It must either - have a line like: - - - -$TTL 86400 - - - at the beginning, or the first record in it must have a TTL field, - like the "84600" in this example: - - - -example.com. 86400 IN SOA ns hostmaster ( 1 3600 1800 1814400 3600 ) - - - - - - - - - Why do I get errors like dns_zone_load: zone foo/IN: loading - master file bar: ran out of space? - - - - - This is often caused by TXT records with missing close - quotes. Check that all TXT records containing quoted strings - have both open and close quotes. - - - - - - - - - How do I restrict people from looking up the server version? - - - - - Put a "version" option containing something other than the - real version in the "options" section of named.conf. Note - doing this will not prevent attacks and may impede people - trying to diagnose problems with your server. Also it is - possible to "fingerprint" nameservers to determine their - version. - - - - - - - - - How do I restrict only remote users from looking up the - server version? - - - - - The following view statement will intercept lookups as the - internal view that holds the version information will be - matched last. The caveats of the previous answer still - apply, of course. - - - -view "chaos" chaos { - match-clients { <those to be refused>; }; - allow-query { none; }; - zone "." { - type hint; - file "/dev/null"; // or any empty file - }; -}; - - - - - - - - - What do no source of entropy found or could not - open entropy source foo mean? - - - - - The server requires a source of entropy to perform certain - operations, mostly DNSSEC related. These messages indicate - that you have no source of entropy. On systems with - /dev/random or an equivalent, it is used by default. A - source of entropy can also be defined using the random-device - option in named.conf. - - - - - - - - - I'm trying to use TSIG to authenticate dynamic updates or - zone transfers. I'm sure I have the keys set up correctly, - but the server is rejecting the TSIG. Why? - - - - - This may be a clock skew problem. Check that the the clocks - on the client and server are properly synchronized (e.g., - using ntp). - - - - - - - - I see a log message like the following. Why? - - - couldn't open pid file '/var/run/named.pid': Permission denied - - - - - You are most likely running named as a non-root user, and - that user does not have permission to write in /var/run. - The common ways of fixing this are to create a /var/run/named - directory owned by the named user and set pid-file to - "/var/run/named/named.pid", or set pid-file to "named.pid", - which will put the file in the directory specified by the - directory option (which, in this case, must be writable by - the user named is running as). - - - - - - - - I can query the nameserver from the nameserver but not from other - machines. Why? - - - - - This is usually the result of the firewall configuration stopping - the queries and / or the replies. - - - - - - - - How can I make a server a slave for both an internal and - an external view at the same time? When I tried, both views - on the slave were transferred from the same view on the master. - - - - - You will need to give the master and slave multiple IP - addresses and use those to make sure you reach the correct - view on the other machine. - - - -Master: 10.0.1.1 (internal), 10.0.1.2 (external, IP alias) - internal: - match-clients { !10.0.1.2; !10.0.1.4; 10.0.1/24; }; - notify-source 10.0.1.1; - transfer-source 10.0.1.1; - query-source address 10.0.1.1; - external: - match-clients { any; }; - recursion no; // don't offer recursion to the world - notify-source 10.0.1.2; - transfer-source 10.0.1.2; - query-source address 10.0.1.2; - -Slave: 10.0.1.3 (internal), 10.0.1.4 (external, IP alias) - internal: - match-clients { !10.0.1.2; !10.0.1.4; 10.0.1/24; }; - notify-source 10.0.1.3; - transfer-source 10.0.1.3; - query-source address 10.0.1.3; - external: - match-clients { any; }; - recursion no; // don't offer recursion to the world - notify-source 10.0.1.4; - transfer-source 10.0.1.4; - query-source address 10.0.1.4; - - - You put the external address on the alias so that all the other - dns clients on these boxes see the internal view by default. - - - - - BIND 9.3 and later: Use TSIG to select the appropriate view. - - - -Master 10.0.1.1: - key "external" { - algorithm hmac-sha256; - secret "xxxxxxxxxxxxxxxxxxxxxxxx"; - }; - view "internal" { - match-clients { !key external; // reject message ment for the - // external view. - 10.0.1/24; }; // accept from these addresses. - ... - }; - view "external" { - match-clients { key external; any; }; - server 10.0.1.2 { keys external; }; // tag messages from the - // external view to the - // other servers for the - // view. - recursion no; - ... - }; - -Slave 10.0.1.2: - key "external" { - algorithm hmac-sha256; - secret "xxxxxxxxxxxxxxxxxxxxxxxx"; - }; - view "internal" { - match-clients { !key external; 10.0.1/24; }; - ... - }; - view "external" { - match-clients { key external; any; }; - server 10.0.1.1 { keys external; }; - recursion no; - ... - }; - - - - - - - - I get error messages like multiple RRs of singleton type - and CNAME and other data when transferring a zone. What - does this mean? - - - - - These indicate a malformed master zone. You can identify - the exact records involved by transferring the zone using - dig then running named-checkzone on it. - - - -dig axfr example.com @master-server > tmp -named-checkzone example.com tmp - - - A CNAME record cannot exist with the same name as another record - except for the DNSSEC records which prove its existence (NSEC). - - - RFC 1034, Section 3.6.2: If a CNAME RR is present at a node, - no other data should be present; this ensures that the data for a - canonical name and its aliases cannot be different. This rule also - insures that a cached CNAME can be used without checking with an - authoritative server for other RR types. - - - - - - - - I get error messages like named.conf:99: unexpected end - of input where 99 is the last line of named.conf. - - - - - There are unbalanced quotes in named.conf. - - - - - Some text editors (notepad and wordpad) fail to put a line - title indication (e.g. CR/LF) on the last line of a - text file. This can be fixed by "adding" a blank line to - the end of the file. Named expects to see EOF immediately - after EOL and treats text files where this is not met as - truncated. - - - - - - - - How do I share a dynamic zone between multiple views? - - - - - You choose one view to be master and the second a slave and - transfer the zone between views. - - - -Master 10.0.1.1: - key "external" { - algorithm hmac-sha256; - secret "xxxxxxxxxxxxxxxxxxxxxxxx"; - }; - - key "mykey" { - algorithm hmac-sha256; - secret "yyyyyyyyyyyyyyyyyyyyyyyy"; - }; - - view "internal" { - match-clients { !key external; 10.0.1/24; }; - server 10.0.1.1 { - /* Deliver notify messages to external view. */ - keys { external; }; - }; - zone "example.com" { - type master; - file "internal/example.db"; - allow-update { key mykey; }; - also-notify { 10.0.1.1; }; - }; - }; - - view "external" { - match-clients { key external; any; }; - zone "example.com" { - type slave; - file "external/example.db"; - masters { 10.0.1.1; }; - transfer-source 10.0.1.1; - // allow-update-forwarding { any; }; - // allow-notify { ... }; - }; - }; - - - - - - - - I get a error message like zone wireless.ietf56.ietf.org/IN: - loading master file primaries/wireless.ietf56.ietf.org: no - owner. - - - - - This error is produced when a line in the master file - contains leading white space (tab/space) but there is no - current record owner name to inherit the name from. Usually - this is the result of putting white space before a comment, - forgetting the "@" for the SOA record, or indenting the master - file. - - - - - - - - Why are my logs in GMT (UTC). - - - - - You are running chrooted (-t) and have not supplied local timezone - information in the chroot area. - - - FreeBSD: /etc/localtime - Solaris: /etc/TIMEZONE and /usr/share/lib/zoneinfo - OSF: /etc/zoneinfo/localtime - - - See also tzset(3) and zic(8). - - - - - - - - I get rndc: connect failed: connection refused when - I try to run rndc. - - - - - This is usually a configuration error. - - - First ensure that named is running and no errors are being - reported at startup (/var/log/messages or equivalent). - Running "named -g <usual arguments>" from a title - can help at this point. - - - Secondly ensure that named is configured to use rndc either - by "rndc-confgen -a", rndc-confgen or manually. The - Administrators Reference manual has details on how to do - this. - - - Old versions of rndc-confgen used localhost rather than - 127.0.0.1 in /etc/rndc.conf for the default server. Update - /etc/rndc.conf if necessary so that the default server - listed in /etc/rndc.conf matches the addresses used in - named.conf. "localhost" has two address (127.0.0.1 and - ::1). - - - If you use "rndc-confgen -a" and named is running with -t or -u - ensure that /etc/rndc.conf has the correct ownership and that - a copy is in the chroot area. You can do this by re-running - "rndc-confgen -a" with appropriate -t and -u arguments. - - - - - - - - I get transfer of 'example.net/IN' from 192.168.4.12#53: - failed while receiving responses: permission denied error - messages. - - - - - These indicate a filesystem permission error preventing - named creating / renaming the temporary file. These will - usually also have other associated error messages like - - - -"dumping master file: sl/tmp-XXXX5il3sQ: open: permission denied" - - - Named needs write permission on the directory containing - the file. Named writes the new cache file to a temporary - file then renames it to the name specified in named.conf - to ensure that the contents are always complete. This is - to prevent named loading a partial zone in the event of - power failure or similar interrupting the write of the - master file. - - - Note file names are relative to the directory specified in - options and any chroot directory ([<chroot - dir>/][<options dir>]). - - - - If named is invoked as "named -t /chroot/DNS" with - the following named.conf then "/chroot/DNS/var/named/sl" - needs to be writable by the user named is running as. - - -options { - directory "/var/named"; -}; - -zone "example.net" { - type slave; - file "sl/example.net"; - masters { 192.168.4.12; }; -}; - - - - - - - - I want to forward all DNS queries from my caching nameserver to - another server. But there are some domains which have to be - served locally, via rbldnsd. - - - How do I achieve this ? - - - - -options { - forward only; - forwarders { <ip.of.primary.nameserver>; }; -}; - -zone "sbl-xbl.spamhaus.org" { - type forward; forward only; - forwarders { <ip.of.rbldns.server> port 530; }; -}; - -zone "list.dsbl.org" { - type forward; forward only; - forwarders { <ip.of.rbldns.server> port 530; }; -}; - - - - - - - - Can you help me understand how BIND 9 uses memory to store - DNS zones? - - - Some times it seems to take several times the amount of - memory it needs to store the zone. - - - - - When reloading a zone named my have multiple copies of - the zone in memory at one time. The zone it is serving - and the one it is loading. If reloads are ultra fast it - can have more still. - - - e.g. Ones that are transferring out, the one that it is - serving and the one that is loading. - - - BIND 8 destroyed the zone before loading and also killed - off outgoing transfers of the zone. - - - The new strategy allows slaves to get copies of the new - zone regardless of how often the master is loaded compared - to the transfer time. The slave might skip some intermediate - versions but the transfers will complete and it will keep - reasonably in sync with the master. - - - The new strategy also allows the master to recover from - syntax and other errors in the master file as it still - has an in-core copy of the old contents. - - - - - - - - I want to use IPv6 locally but I don't have a external IPv6 - connection. External lookups are slow. - - - - - You can use server clauses to stop named making external lookups - over IPv6. - - -server fd81:ec6c:bd62::/48 { bogus no; }; // site ULA prefix -server ::/0 { bogus yes; }; - - - - - - - Operations Questions - - - - - How to change the nameservers for a zone? - - - - - Step 1: Ensure all nameservers, new and old, are serving the - same zone content. - - - Step 2: Work out the maximum TTL of the NS RRset in the parent and child - zones. This is the time it will take caches to be clear of a - particular version of the NS RRset. - If you are just removing nameservers you can skip to Step 6. - - - Step 3: Add new nameservers to the NS RRset for the zone and - wait until all the servers for the zone are answering with this - new NS RRset. - - - Step 4: Inform the parent zone of the new NS RRset then wait for all the - parent servers to be answering with the new NS RRset. - - - Step 5: Wait for cache to be clear of the old NS RRset. - See Step 2 for how long. - If you are just adding nameservers you are done. - - - Step 6: Remove any old nameservers from the zones NS RRset and - wait for all the servers for the zone to be serving the new NS RRset. - - - Step 7: Inform the parent zone of the new NS RRset then wait for all the - parent servers to be answering with the new NS RRset. - - - Step 8: Wait for cache to be clear of the old NS RRset. - See Step 2 for how long. - - - Step 9: Turn off the old nameservers or remove the zone entry from - the configuration of the old nameservers. - - - Step 10: Increment the serial number and wait for the change to - be visible in all nameservers for the zone. This ensures that - zone transfers are still working after the old servers are - decommissioned. - - - Note: the above procedure is designed to be transparent - to dns clients. Decommissioning the old servers too early - will result in some clients not being able to look up - answers in the zone. - - - Note: while it is possible to run the addition and removal - stages together it is not recommended. - - - - - - - General Questions - - - - - I keep getting log messages like the following. Why? - - - Dec 4 23:47:59 client 10.0.0.1#1355: updating zone - 'example.com/IN': update failed: 'RRset exists (value - dependent)' prerequisite not satisfied (NXRRSET) - - - - - DNS updates allow the update request to test to see if - certain conditions are met prior to proceeding with the - update. The message above is saying that conditions were - not met and the update is not proceeding. See doc/rfc/rfc2136.txt - for more details on prerequisites. - - - - - - - - I keep getting log messages like the following. Why? - - - Jun 21 12:00:00.000 client 10.0.0.1#1234: update denied - - - - - Someone is trying to update your DNS data using the RFC2136 - Dynamic Update protocol. Windows 2000 machines have a habit - of sending dynamic update requests to DNS servers without - being specifically configured to do so. If the update - requests are coming from a Windows 2000 machine, see - - <http://support.microsoft.com/support/kb/articles/q246/8/04.asp> - for information about how to turn them off. - - - - - - - - When I do a "dig . ns", many of the A records for the root - servers are missing. Why? - - - - - This is normal and harmless. It is a somewhat confusing - side effect of the way BIND 9 does RFC2181 trust ranking - and of the efforts BIND 9 makes to avoid promoting glue - into answers. - - - When BIND 9 first starts up and primes its cache, it receives - the root server addresses as additional data in an authoritative - response from a root server, and these records are eligible - for inclusion as additional data in responses. Subsequently - it receives a subset of the root server addresses as - additional data in a non-authoritative (referral) response - from a root server. This causes the addresses to now be - considered non-authoritative (glue) data, which is not - eligible for inclusion in responses. - - - The server does have a complete set of root server addresses - cached at all times, it just may not include all of them - as additional data, depending on whether they were last - received as answers or as glue. You can always look up the - addresses with explicit queries like "dig a.root-servers.net A". - - - - - - - - Why don't my zones reload when I do an "rndc reload" or SIGHUP? - - - - - A zone can be updated either by editing zone files and - reloading the server or by dynamic update, but not both. - If you have enabled dynamic update for a zone using the - "allow-update" option, you are not supposed to edit the - zone file by hand, and the server will not attempt to reload - it. - - - - - - - - Why is named listening on UDP port other than 53? - - - - - Named uses a system selected port to make queries of other - nameservers. This behaviour can be overridden by using - query-source to lock down the port and/or address. See - also notify-source and transfer-source. - - - - - - - - I get warning messages like zone example.com/IN: refresh: - failure trying master 1.2.3.4#53: timed out. - - - - - Check that you can make UDP queries from the slave to the master - - - -dig +norec example.com soa @1.2.3.4 - - - You could be generating queries faster than the slave can - cope with. Lower the serial query rate. - - - -serial-query-rate 5; // default 20 - - - - - - - - I don't get RRSIG's returned when I use "dig +dnssec". - - - - - You need to ensure DNSSEC is enabled (dnssec-enable yes;). - - - - - - - - Can a NS record refer to a CNAME. - - - - - No. The rules for glue (copies of the *address* records - in the parent zones) and additional section processing do - not allow it to work. - - - You would have to add both the CNAME and address records - (A/AAAA) as glue to the parent zone and have CNAMEs be - followed when doing additional section processing to make - it work. No nameserver implementation supports either of - these requirements. - - - - - - - - What does RFC 1918 response from Internet for - 0.0.0.10.IN-ADDR.ARPA mean? - - - - - If the IN-ADDR.ARPA name covered refers to a internal address - space you are using then you have failed to follow RFC 1918 - usage rules and are leaking queries to the Internet. You - should establish your own zones for these addresses to prevent - you querying the Internet's name servers for these addresses. - Please see <http://as112.net/> - for details of the problems you are causing and the counter - measures that have had to be deployed. - - - If you are not using these private addresses then a client - has queried for them. You can just ignore the messages, - get the offending client to stop sending you these messages - as they are most probably leaking them or setup your own zones - empty zones to serve answers to these queries. - - - -zone "10.IN-ADDR.ARPA" { - type master; - file "empty"; -}; - -zone "16.172.IN-ADDR.ARPA" { - type master; - file "empty"; -}; - -... - -zone "31.172.IN-ADDR.ARPA" { - type master; - file "empty"; -}; - -zone "168.192.IN-ADDR.ARPA" { - type master; - file "empty"; -}; - -empty: -@ 10800 IN SOA <name-of-server>. <contact-email>. ( - 1 3600 1200 604800 10800 ) -@ 10800 IN NS <name-of-server>. - - - - Future versions of named are likely to do this automatically. - - - - - - - - - Will named be affected by the 2007 changes to daylight savings - rules in the US. - - - - - No, so long as the machines internal clock (as reported - by "date -u") remains at UTC. The only visible change - if you fail to upgrade your OS, if you are in a affected - area, will be that log messages will be a hour out during - the period where the old rules do not match the new rules. - - - For most OS's this change just means that you need to - update the conversion rules from UTC to local time. - Normally this involves updating a file in /etc (which - sets the default timezone for the machine) and possibly - a directory which has all the conversion rules for the - world (e.g. /usr/share/zoneinfo). When updating the OS - do not forget to update any chroot areas as well. - See your OS's documentation for more details. - - - The local timezone conversion rules can also be done on - a individual basis by setting the TZ environment variable - appropriately. See your OS's documentation for more - details. - - - - - - - - Is there a bugzilla (or other tool) database that mere - mortals can have (read-only) access to for bind? - - - - - No. The BIND 9 bug database is kept closed for a number - of reasons. These include, but are not limited to, that - the database contains proprietory information from people - reporting bugs. The database has in the past and may in - future contain unfixed bugs which are capable of bringing - down most of the Internet's DNS infrastructure. - - - The release pages for each version contain up to date - lists of bugs that have been fixed post release. That - is as close as we can get to providing a bug database. - - - - - - - - Why do queries for NSEC3 records fail to return the NSEC3 record? - - - - - NSEC3 records are strictly meta data and can only be - returned in the authority section. This is done so that - signing the zone using NSEC3 records does not bring names - into existence that do not exist in the unsigned version - of the zone. - - - - - - - Operating-System Specific Questions - - HPUX - - - - I get the following error trying to configure BIND: -checking if unistd.h or sys/types.h defines fd_set... no -configure: error: need either working unistd.h or sys/select.h - - - - - You have attempted to configure BIND with the bundled C compiler. - This compiler does not meet the minimum compiler requirements to - for building BIND. You need to install a ANSI C compiler and / or - teach configure how to find the ANSI C compiler. The later can - be done by adjusting the PATH environment variable and / or - specifying the compiler via CC. - - - ./configure CC=<compiler> ... - - - - - - - Linux - - - - - Why do I get the following errors: -general: errno2result.c:109: unexpected error: -general: unable to convert errno to isc_result: 14: Bad address -client: UDP client handler shutting down due to fatal receive error: unexpected error - - - - - This is the result of a Linux kernel bug. - - - See: - <http://marc.theaimsgroup.com/?l=linux-netdev&m=113081708031466&w=2> - - - - - - - - Why does named lock up when it attempts to connect over IPSEC tunnels? - - - - - This is due to a kernel bug where the fact that a socket is marked - non-blocking is ignored. It is reported that setting - xfrm_larval_drop to 1 helps but this may have negative side effects. - See: -<https://bugzilla.redhat.com/show_bug.cgi?id=427629> - and -<http://lkml.org/lkml/2007/12/4/260>. - - - xfrm_larval_drop can be set to 1 by the following procedure: - -echo "1" > proc/sys/net/core/xfrm_larval_drop - - - - - - - - Why do I see 5 (or more) copies of named on Linux? - - - - - Linux threads each show up as a process under ps. The - approximate number of threads running is n+4, where n is - the number of CPUs. Note that the amount of memory used - is not cumulative; if each process is using 10M of memory, - only a total of 10M is used. - - - Newer versions of Linux's ps command hide the individual threads - and require -L to display them. - - - - - - - - Why does BIND 9 log permission denied errors accessing - its configuration files or zones on my Linux system even - though it is running as root? - - - - - On Linux, BIND 9 drops most of its root privileges on - startup. This including the privilege to open files owned - by other users. Therefore, if the server is running as - root, the configuration files and zone files should also - be owned by root. - - - - - - - - I get the error message named: capset failed: Operation - not permitted when starting named. - - - - - The capability module, part of "Linux Security Modules/LSM", - has not been loaded into the kernel. See insmod(8), modprobe(8). - - - The relevant modules can be loaded by running: - -modprobe commoncap -modprobe capability - - - - - - - - I'm running BIND on Red Hat Enterprise Linux or Fedora Core - - - - Why can't named update slave zone database files? - - - Why can't named create DDNS journal files or update - the master zones from journals? - - - Why can't named create custom log files? - - - - - - Red Hat Security Enhanced Linux (SELinux) policy security - protections : - - - - Red Hat have adopted the National Security Agency's - SELinux security policy (see <http://www.nsa.gov/selinux>) - and recommendations for BIND security , which are more - secure than running named in a chroot and make use of - the bind-chroot environment unnecessary . - - - - By default, named is not allowed by the SELinux policy - to write, create or delete any files EXCEPT in these - directories: - - -$ROOTDIR/var/named/slaves -$ROOTDIR/var/named/data -$ROOTDIR/var/tmp - - - where $ROOTDIR may be set in /etc/sysconfig/named if - bind-chroot is installed. - - - - The SELinux policy particularly does NOT allow named to modify - the $ROOTDIR/var/named directory, the default location for master - zone database files. - - - - SELinux policy overrules file access permissions - so - even if all the files under /var/named have ownership - named:named and mode rw-rw-r--, named will still not be - able to write or create files except in the directories - above, with SELinux in Enforcing mode. - - - - So, to allow named to update slave or DDNS zone files, - it is best to locate them in $ROOTDIR/var/named/slaves, - with named.conf zone statements such as: - - -zone "slave.zone." IN { - type slave; - file "slaves/slave.zone.db"; - ... -}; -zone "ddns.zone." IN { - type master; - allow-updates {...}; - file "slaves/ddns.zone.db"; -}; - - - - - - To allow named to create its cache dump and statistics - files, for example, you could use named.conf options - statements such as: - - -options { - ... - dump-file "/var/named/data/cache_dump.db"; - statistics-file "/var/named/data/named_stats.txt"; - ... -}; - - - - - - You can also tell SELinux to allow named to update any - zone database files, by setting the SELinux tunable boolean - parameter 'named_write_master_zones=1', using the - system-config-securitylevel GUI, using the 'setsebool' - command, or in /etc/selinux/targeted/booleans. - - - - You can disable SELinux protection for named entirely by - setting the 'named_disable_trans=1' SELinux tunable boolean - parameter. - - - - The SELinux named policy defines these SELinux contexts for named: - - -named_zone_t : for zone database files - $ROOTDIR/var/named/* -named_conf_t : for named configuration files - $ROOTDIR/etc/{named,rndc}.* -named_cache_t: for files modifiable by named - $ROOTDIR/var/{tmp,named/{slaves,data}} - - - - - - If you want to retain use of the SELinux policy for named, - and put named files in different locations, you can do - so by changing the context of the custom file locations - . - - - - To create a custom configuration file location, e.g. - '/root/named.conf', to use with the 'named -c' option, - do: - - -# chcon system_u:object_r:named_conf_t /root/named.conf - - - - - - To create a custom modifiable named data location, e.g. - '/var/log/named' for a log file, do: - - -# chcon system_u:object_r:named_cache_t /var/log/named - - - - - - To create a custom zone file location, e.g. /root/zones/, do: - - -# chcon system_u:object_r:named_zone_t /root/zones/{.,*} - - - - - - See these man-pages for more information : selinux(8), - named_selinux(8), chcon(1), setsebool(8) - - - - - - - - I'm running BIND on Ubuntu - - - - Why can't named update slave zone database files? - - - Why can't named create DDNS journal files or update - the master zones from journals? - - - Why can't named create custom log files? - - - - - Ubuntu uses AppArmor - <http://en.wikipedia.org/wiki/AppArmor> in - addition to normal file system permissions to protect the system. - - - Adjust the paths to use those specified in /etc/apparmor.d/usr.sbin.named - or adjust /etc/apparmor.d/usr.sbin.named to allow named to write at the - location specified in named.conf. - - - - - - - - Listening on individual IPv6 interfaces does not work. - - - - - This is usually due to "/proc/net/if_inet6" not being available - in the chroot file system. Mount another instance of "proc" - in the chroot file system. - - - This can be be made permanent by adding a second instance to - /etc/fstab. - - -proc /proc proc defaults 0 0 -proc /var/named/proc proc defaults 0 0 - - - - - - - - Windows - - - - - Zone transfers from my BIND 9 master to my Windows 2000 - slave fail. Why? - - - - - This may be caused by a bug in the Windows 2000 DNS server - where DNS messages larger than 16K are not handled properly. - This can be worked around by setting the option "transfer-format - one-answer;". Also check whether your zone contains domain - names with embedded spaces or other special characters, - like "John\032Doe\213s\032Computer", since such names have - been known to cause Windows 2000 slaves to incorrectly - reject the zone. - - - - - - - - I get Error 1067 when starting named under Windows. - - - - - This is the service manager saying that named exited. You - need to examine the Application log in the EventViewer to - find out why. - - - Common causes are that you failed to create "named.conf" - (usually "C:\windows\dns\etc\named.conf") or failed to - specify the directory in named.conf. - - - -options { - Directory "C:\windows\dns\etc"; -}; - - - - - - - FreeBSD - - - - - I have FreeBSD 4.x and "rndc-confgen -a" just sits there. - - - - - /dev/random is not configured. Use rndcontrol(8) to tell - the kernel to use certain interrupts as a source of random - events. You can make this permanent by setting rand_irqs - in /etc/rc.conf. - - - -rand_irqs="3 14 15" - - - See also - - <http://people.freebsd.org/~dougb/randomness.html>. - - - - - - - Solaris - - - - - How do I integrate BIND 9 and Solaris SMF - - - - - Sun has a blog entry describing how to do this. - - - - <http://blogs.sun.com/roller/page/anay/Weblog?catname=%2FSolaris> - - - - - - - - Apple Mac OS X - - - - - How do I run BIND 9 on Apple Mac OS X? - - - - - If you run Tiger(Mac OS 10.4) or later then this is all you need to do: - - - -% sudo rndc-confgen > /etc/rndc.conf - - - Copy the key statement from /etc/rndc.conf into /etc/rndc.key, e.g.: - - - -key "rndc-key" { - algorithm hmac-sha256; - secret "uvceheVuqf17ZwIcTydddw=="; -}; - - - Then start the relevant service: - - - -% sudo service org.isc.named start - - - This is persistent upon a reboot, so you will have to do it only once. - - - - - - Alternatively you can just generate /etc/rndc.key by running: - - - -% sudo rndc-confgen -a - - - Then start the relevant service: - - - -% sudo service org.isc.named start - - - Named will look for /etc/rndc.key when it starts if it - doesn't have a controls section or the existing controls are - missing keys sub-clauses. This is persistent upon a - reboot, so you will have to do it only once. - - - - - - - - - -
diff --git a/HISTORY b/HISTORY index d306a978ad8..238e2634155 100644 --- a/HISTORY +++ b/HISTORY @@ -1,540 +1,525 @@ -Summary of functional enhancements from prior major releases of BIND 9: +Functional enhancements from prior major releases of BIND 9 + +BIND 9.11 + +BIND 9.11.0 includes a number of changes from BIND 9.10 and earlier +releases. New features include: + + * Added support for Catalog Zones, a new method for provisioning + servers: a list of zones to be served is stored in a DNS zone, along + with their configuration parameters. Changes to the catalog zone are + propagated to slaves via normal AXFR/IXFR, whereupon the zones that + are listed in it are automatically added, deleted or reconfigured. + * Added support for "dnstap", a fast and flexible method of capturing + and logging DNS traffic. + * Added support for "dyndb", a new API for loading zone data from an + external database, developed by Red Hat for the FreeIPA project. + * "fetchlimit" quotas are now compiled in by default. These are for the + use of recursive resolvers that are are under high query load for + domains whose authoritative servers are nonresponsive or are + experiencing a denial of service attack: + + "fetches-per-server" limits the number of simultaneous queries + that can be sent to any single authoritative server. The + configured value is a starting point; it is automatically adjusted + downward if the server is partially or completely non-responsive. + The algorithm used to adjust the quota can be configured via the + "fetch-quota-params" option. + + "fetches-per-zone" limits the number of simultaneous queries that + can be sent for names within a single domain. (Note: Unlike + "fetches-per-server", this value is not self-tuning.) + + New stats counters have been added to count queries spilled due to + these quotas. + * Added a new "dnssec-keymgr" key mainenance utility, which can generate + or update keys as needed to ensure that a zone's keys match a defined + DNSSEC policy. + * The experimental "SIT" feature in BIND 9.10 has been renamed "COOKIE" + and is no longer optional. EDNS COOKIE is a mechanism enabling clients + to detect off-path spoofed responses, and servers to detect + spoofed-source queries. Clients that identify themselves using COOKIE + options are not subject to response rate limiting (RRL) and can + receive larger UDP responses. + * SERVFAIL responses can now be cached for a limited time (defaulting to + 1 second, with an upper limit of 30). This can reduce the frequency of + retries when a query is persistently failing. + * Added an "nsip-wait-recurse" switch to RPZ. This causes NSIP rules to + be skipped if a name server IP address isn't in the cache yet; the + address will be looked up and the rule will be applied on future + queries. + * Added a Python RNDC module. This allows multiple commands to sent over + a persistent RNDC channel, which saves time. + * The "controls" block in named.conf can now grant read-only "rndc" + access to specified clients or keys. Read-only clients could, for + example, check "rndc status" but could not reconfigure or shut down + the server. + * "rndc" commands can now return arbitrarily large amounts of text to + the caller. + * The zone serial number of a dynamically updatable zone can now be set + via "rndc signing -serial ". This allows inline-signing zones to be + set to a specific serial number. + * The new "rndc nta" command can be used to set a Negative Trust Anchor + (NTA), disabling DNSSEC validation for a specific domain; this can be + used when responses from a domain are known to be failing validation + due to administrative error rather than because of a spoofing attack. + Negative trust anchors are strictly temporary; by default they expire + after one hour, but can be configured to last up to one week. + * "rndc delzone" can now be used on zones that were not originally + created by "rndc addzone". + * "rndc modzone" reconfigures a single zone, without requiring the + entire server to be reconfigured. + * "rndc showzone" displays the current configuration of a zone. + * "rndc managed-keys" can be used to check the status of RFC 5001 + managed trust anchors, or to force trust anchors to be refreshed. + * "max-cache-size" can now be set to a percentage of available memory. + The default is 90%. + * Update forwarding performance has been improved by allowing a single + TCP connection to be shared by multiple updates. + * The EDNS Client Subnet (ECS) option is now supported for authoritative + servers; if a query contains an ECS option then ACLs containing + "geoip" or "ecs" elements can match against the the address encoded in + the option. This can be used to select a view for a query, so that + different answers can be provided depending on the client network. + * The EDNS EXPIRE option has been implemented on the client side, + allowing a slave server to set the expiration timer correctly when + transferring zone data from another slave server. + * The key generation and manipulation tools (dnssec-keygen, + dnssec-settime, dnssec-importkey, dnssec-keyfromlabel) now take + "-Psync" and "-Dsync" options to set the publication and deletion + times of CDS and CDNSKEY parent-synchronization records. Both named + and dnssec-signzone can now publish and remove these records at the + scheduled times. + * A new "minimal-any" option reduces the size of UDP responses for query + type ANY by returning a single arbitrarily selected RRset instead of + all RRsets. + * A new "masterfile-style" zone option controls the formatting of text + zone files: When set to "full", a zone file is dumped in + single-line-per-record format. + * "serial-update-method" can now be set to "date". On update, the serial + number will be set to the current date in YYYYMMDDNN format. + * "dnssec-signzone -N date" sets the serial number to YYYYMMDDNN. + * "named -L " causes named to send log messages to the specified file by + default instead of to the system log. + * "dig +ttlunits" prints TTL values with time-unit suffixes: w, d, h, m, + s for weeks, days, hours, minutes, and seconds. + * "dig +unknownformat" prints dig output in RFC 3597 "unknown record" + presentation format. + * "dig +ednsopt" allows dig to set arbitrary EDNS options on requests. + * "dig +ednsflags" allows dig to set yet-to-be-defined EDNS flags on + requests. + * "mdig" is an alternate version of dig which sends multiple pipelined + TCP queries to a server. Instead of waiting for a response after + sending a query, it sends all queries immediately and displays + responses in the order received. + * "serial-query-rate" no longer controls NOTIFY messages. These are + separately controlled by "notify-rate" and "startup-notify-rate". + * "nsupdate" now performs "check-names" processing by default on records + to be added. This can be disabled with "check-names no". + * The statistics channel now supports DEFLATE compression, reducing the + size of the data sent over the network when querying statistics. + * New counters have been added to the statistics channel to track the + sizes of incoming queries and outgoing responses in histogram buckets, + as specified in RSSAC002. + * A new NXDOMAIN redirect method (option "nxdomain-redirect") has been + added, allowing redirection to a specified DNS namespace instead of a + single redirect zone. + * When starting up, named now ensures that no other named process is + already running. + * Files created by named to store information, including "mkeys" and + "nzf" files, are now named after their corresponding views unless the + view name contains characters incompatible with use as a filename. Old + style filenames (based on the hash of the view name) will still work. BIND 9.10.0 - BIND 9.10.0 includes a number of changes from BIND 9.9 and earlier - releases. New features include: - - - DNS Response-rate limiting (DNS RRL), which blunts the - impact of reflection and amplification attacks, is always - compiled in and no longer requires a compile-time option - to enable it. - - An experimental "Source Identity Token" (SIT) EDNS option - is now available. Similar to DNS Cookies as invented by - Donald Eastlake 3rd, these are designed to enable clients - to detect off-path spoofed responses, and to enable servers - to detect spoofed-source queries. Servers can be configured - to send smaller responses to clients that have not identified - themselves using a SIT option, reducing the effectiveness of - amplification attacks. RRL processing has also been updated; - clients proven to be legitimate via SIT are not subject to - rate limiting. Use "configure --enable-sit" to enable this - feature in BIND. - - A new zone file format, "map", stores zone data in a - format that can be mapped directly into memory, allowing - significantly faster zone loading. - - "delv" (domain entity lookup and validation) is a new tool - with dig-like semantics for looking up DNS data and performing - internal DNSSEC validation. This allows easy validation in - environments where the resolver may not be trustworthy, and - assists with troubleshooting of DNSSEC problems. (NOTE: - In previous development releases of BIND 9.10, this utility - was called "delve". The spelling has been changed to avoid - confusion with the "delve" utility included with the Xapian - search engine.) - - Improved EDNS(0) processing for better resolver performance - and reliability over slow or lossy connections. - - A new "configure --with-tuning=large" option tunes certain - compiled-in constants and default settings to values better - suited to large servers with abundant memory. This can - improve performance on such servers, but will consume more - memory and may degrade performance on smaller systems. - - Substantial improvement in response-policy zone (RPZ) - performance. Up to 32 response-policy zones can be - configured with minimal performance loss. - - To improve recursive resolver performance, cache records - which are still being requested by clients can now be - automatically refreshed from the authoritative server - before they expire, reducing or eliminating the time - window in which no answer is available in the cache. - - New "rpz-client-ip" triggers and drop policies allowing - response policies based on the IP address of the client. - - ACLs can now be specified based on geographic location - using the MaxMind GeoIP databases. Use "configure - --with-geoip" to enable. - - Zone data can now be shared between views, allowing - multiple views to serve the same zones authoritatively - without storing multiple copies in memory. - - New XML schema (version 3) for the statistics channel - includes many new statistics and uses a flattened XML tree - for faster parsing. The older schema is now deprecated. - - A new stylesheet, based on the Google Charts API, displays - XML statistics in charts and graphs on javascript-enabled - browsers. - - The statistics channel can now provide data in JSON - format as well as XML. - - New stats counters track TCP and UDP queries received - per zone, and EDNS options received in total. - - The internal and export versions of the BIND libraries - (libisc, libdns, etc) have been unified so that external - library clients can use the same libraries as BIND itself. - - A new compile-time option, "configure --enable-native-pkcs11", - allows BIND 9 cryptography functions to use the PKCS#11 API - natively, so that BIND can drive a cryptographic hardware - service module (HSM) directly instead of using a modified - OpenSSL as an intermediary. (Note: This feature requires an - HSM to have a full implementation of the PKCS#11 API; many - current HSMs only have partial implementations. The new - "pkcs11-tokens" command can be used to check API completeness. - Native PKCS#11 is known to work with the Thales nShield HSM - and with SoftHSM version 2 from the Open DNSSEC project.) - - The new "max-zone-ttl" option enforces maximum TTLs for - zones. This can simplify the process of rolling DNSSEC keys - by guaranteeing that cached signatures will have expired - within the specified amount of time. - - "dig +subnet" sends an EDNS CLIENT-SUBNET option when - querying. - - "dig +expire" sends an EDNS EXPIRE option when querying. - When this option is sent with an SOA query to a server - that supports it, it will report the expiry time of - a slave zone. - - New "dnssec-coverage" tool to check DNSSEC key coverage - for a zone and report if a lapse in signing coverage has - been inadvertently scheduled. - - Signing algorithm flexibility and other improvements - for the "rndc" control channel. - - "named-checkzone" and "named-compilezone" can now read - journal files, allowing them to process dynamic zones. - - Multiple DLZ databases can now be configured. Individual - zones can be configured to be served from a specific DLZ - database. DLZ databases now serve zones of type "master" - and "redirect". - - "rndc zonestatus" reports information about a specified zone. - - "named" now listens on IPv6 as well as IPv4 interfaces - by default. - - "named" now preserves the capitalization of names - when responding to queries: for instance, a query for - "example.com" may be answered with "example.COM" if the - name was configured that way in the zone file. Some - clients have a bug causing them to depend on the older - behavior, in which the case of the answer always matched - the case of the query, rather than the case of the name - configured in the DNS. Such clients can now be specified - in the new "no-case-compress" ACL; this will restore the - older behavior of "named" for those clients only. - - new "dnssec-importkey" command allows the use of offline - DNSSEC keys with automatic DNSKEY management. - - New "named-rrchecker" tool to verify the syntactic - correctness of individual resource records. - - When re-signing a zone, the new "dnssec-signzone -Q" option - drops signatures from keys that are still published but are - no longer active. - - "named-checkconf -px" will print the contents of configuration - files with the shared secrets obscured, making it easier to - share configuration (e.g. when submitting a bug report) - without revealing private information. - - "rndc scan" causes named to re-scan network interfaces for - changes in local addresses. - - On operating systems with support for routing sockets, - network interfaces are re-scanned automatically whenever - they change. - - "tsig-keygen" is now available as an alternate command - name to use for "ddns-confgen". +BIND 9.10.0 includes a number of changes from BIND 9.9 and earlier +releases. New features include: + + * DNS Response-rate limiting (DNS RRL), which blunts the impact of + reflection and amplification attacks, is always compiled in and no + longer requires a compile-time option to enable it. + * An experimental "Source Identity Token" (SIT) EDNS option is now + available. Similar to DNS Cookies as invented by Donald Eastlake 3rd, + these are designed to enable clients to detect off-path spoofed + responses, and to enable servers to detect spoofed-source queries. + Servers can be configured to send smaller responses to clients that + have not identified themselves using a SIT option, reducing the + effectiveness of amplification attacks. RRL processing has also been + updated; clients proven to be legitimate via SIT are not subject to + rate limiting. Use "configure --enable-sit" to enable this feature in + BIND. + * A new zone file format, "map", stores zone data in a format that can + be mapped directly into memory, allowing significantly faster zone + loading. + * "delv" (domain entity lookup and validation) is a new tool with + dig-like semantics for looking up DNS data and performing internal + DNSSEC validation. This allows easy validation in environments where + the resolver may not be trustworthy, and assists with troubleshooting + of DNSSEC problems. (NOTE: In previous development releases of BIND + 9.10, this utility was called "delve". The spelling has been changed + to avoid confusion with the "delve" utility included with the Xapian + search engine.) + * Improved EDNS(0) processing for better resolver performance and + reliability over slow or lossy connections. + * A new "configure --with-tuning=large" option tunes certain compiled-in + constants and default settings to values better suited to large + servers with abundant memory. This can improve performance on such + servers, but will consume more memory and may degrade performance on + smaller systems. + * Substantial improvement in response-policy zone (RPZ) performance. Up + to 32 response-policy zones can be configured with minimal performance + loss. + * To improve recursive resolver performance, cache records which are + still being requested by clients can now be automatically refreshed + from the authoritative server before they expire, reducing or + eliminating the time window in which no answer is available in the + cache. + * New "rpz-client-ip" triggers and drop policies allowing response + policies based on the IP address of the client. + * ACLs can now be specified based on geographic location using the + MaxMind GeoIP databases. Use "configure --with-geoip" to enable. + * Zone data can now be shared between views, allowing multiple views to + serve the same zones authoritatively without storing multiple copies + in memory. + * New XML schema (version 3) for the statistics channel includes many + new statistics and uses a flattened XML tree for faster parsing. The + older schema is now deprecated. + * A new stylesheet, based on the Google Charts API, displays XML + statistics in charts and graphs on javascript-enabled browsers. + * The statistics channel can now provide data in JSON format as well as + XML. + * New stats counters track TCP and UDP queries received per zone, and + EDNS options received in total. + * The internal and export versions of the BIND libraries (libisc, + libdns, etc) have been unified so that external library clients can + use the same libraries as BIND itself. + * A new compile-time option, "configure --enable-native-pkcs11", allows + BIND 9 cryptography functions to use the PKCS#11 API natively, so that + BIND can drive a cryptographic hardware service module (HSM) directly + instead of using a modified OpenSSL as an intermediary. (Note: This + feature requires an HSM to have a full implementation of the PKCS#11 + API; many current HSMs only have partial implementations. The new + "pkcs11-tokens" command can be used to check API completeness. Native + PKCS#11 is known to work with the Thales nShield HSM and with SoftHSM + version 2 from the Open DNSSEC project.) + * The new "max-zone-ttl" option enforces maximum TTLs for zones. This + can simplify the process of rolling DNSSEC keys by guaranteeing that + cached signatures will have expired within the specified amount of + time. + * "dig +subnet" sends an EDNS CLIENT-SUBNET option when querying. + * "dig +expire" sends an EDNS EXPIRE option when querying. When this + option is sent with an SOA query to a server that supports it, it will + report the expiry time of a slave zone. + * New "dnssec-coverage" tool to check DNSSEC key coverage for a zone and + report if a lapse in signing coverage has been inadvertently + scheduled. + * Signing algorithm flexibility and other improvements for the "rndc" + control channel. + * "named-checkzone" and "named-compilezone" can now read journal files, + allowing them to process dynamic zones. + * Multiple DLZ databases can now be configured. Individual zones can be + configured to be served from a specific DLZ database. DLZ databases + now serve zones of type "master" and "redirect". + * "rndc zonestatus" reports information about a specified zone. + * "named" now listens on IPv6 as well as IPv4 interfaces by default. + * "named" now preserves the capitalization of names when responding to + queries: for instance, a query for "example.com" may be answered with + "example.COM" if the name was configured that way in the zone file. + Some clients have a bug causing them to depend on the older behavior, + in which the case of the answer always matched the case of the query, + rather than the case of the name configured in the DNS. Such clients + can now be specified in the new "no-case-compress" ACL; this will + restore the older behavior of "named" for those clients only. + * new "dnssec-importkey" command allows the use of offline DNSSEC keys + with automatic DNSKEY management. + * New "named-rrchecker" tool to verify the syntactic correctness of + individual resource records. + * When re-signing a zone, the new "dnssec-signzone -Q" option drops + signatures from keys that are still published but are no longer + active. + * "named-checkconf -px" will print the contents of configuration files + with the shared secrets obscured, making it easier to share + configuration (e.g. when submitting a bug report) without revealing + private information. + * "rndc scan" causes named to re-scan network interfaces for changes in + local addresses. + * On operating systems with support for routing sockets, network + interfaces are re-scanned automatically whenever they change. + * "tsig-keygen" is now available as an alternate command name to use for + "ddns-confgen". BIND 9.9.0 - BIND 9.9.0 includes a number of changes from BIND 9.8 and earlier - releases. New features include: - - - Inline signing, allowing automatic DNSSEC signing of - master zones without modification of the zonefile, or - "bump in the wire" signing in slaves. - - NXDOMAIN redirection. - - New 'rndc flushtree' command clears all data under a given - name from the DNS cache. - - New 'rndc sync' command dumps pending changes in a dynamic - zone to disk without a freeze/thaw cycle. - - New 'rndc signing' command displays or clears signing status - records in 'auto-dnssec' zones. - - NSEC3 parameters for 'auto-dnssec' zones can now be set prior - to signing, eliminating the need to initially sign with NSEC. - - Startup time improvements on large authoritative servers. - - Slave zones are now saved in raw format by default. - - Several improvements to response policy zones (RPZ). - - Improved hardware scalability by using multiple threads - to listen for queries and using finer-grained client locking - - The 'also-notify' option now takes the same syntax as - 'masters', so it can used named masterlists and TSIG keys. - - 'dnssec-signzone -D' writes an output file containing only DNSSEC - data, which can be included by the primary zone file. - - 'dnssec-signzone -R' forces removal of signatures that are - not expired but were created by a key which no longer exists. - - 'dnssec-signzone -X' allows a separate expiration date to - be specified for DNSKEY signatures from other signatures. - - New '-L' option to dnssec-keygen, dnssec-settime, and - dnssec-keyfromlabel sets the default TTL for the key. - - dnssec-dsfromkey now supports reading from standard input, - to make it easier to convert DNSKEY to DS. - - RFC 1918 reverse zones have been added to the empty-zones - table per RFC 6303. - - Dynamic updates can now optionally set the zone's SOA serial - number to the current UNIX time. - - DLZ modules can now retrieve the source IP address of - the querying client. - - 'request-ixfr' option can now be set at the per-zone level. - - 'dig +rrcomments' turns on comments about DNSKEY records, - indicating their key ID, algorithm and function - - Simplified nsupdate syntax and added readline support +BIND 9.9.0 includes a number of changes from BIND 9.8 and earlier +releases. New features include: + + * Inline signing, allowing automatic DNSSEC signing of master zones + without modification of the zonefile, or "bump in the wire" signing in + slaves. + * NXDOMAIN redirection. + * New 'rndc flushtree' command clears all data under a given name from + the DNS cache. + * New 'rndc sync' command dumps pending changes in a dynamic zone to + disk without a freeze/thaw cycle. + * New 'rndc signing' command displays or clears signing status records + in 'auto-dnssec' zones. + * NSEC3 parameters for 'auto-dnssec' zones can now be set prior to + signing, eliminating the need to initially sign with NSEC. + * Startup time improvements on large authoritative servers. + * Slave zones are now saved in raw format by default. + * Several improvements to response policy zones (RPZ). + * Improved hardware scalability by using multiple threads to listen for + queries and using finer-grained client locking + * The 'also-notify' option now takes the same syntax as 'masters', so it + can used named masterlists and TSIG keys. + * 'dnssec-signzone -D' writes an output file containing only DNSSEC + data, which can be included by the primary zone file. + * 'dnssec-signzone -R' forces removal of signatures that are not expired + but were created by a key which no longer exists. + * 'dnssec-signzone -X' allows a separate expiration date to be specified + for DNSKEY signatures from other signatures. + * New '-L' option to dnssec-keygen, dnssec-settime, and + dnssec-keyfromlabel sets the default TTL for the key. + * dnssec-dsfromkey now supports reading from standard input, to make it + easier to convert DNSKEY to DS. + * RFC 1918 reverse zones have been added to the empty-zones table per + RFC 6303. + * Dynamic updates can now optionally set the zone's SOA serial number to + the current UNIX time. + * DLZ modules can now retrieve the source IP address of the querying + client. + * 'request-ixfr' option can now be set at the per-zone level. + * 'dig +rrcomments' turns on comments about DNSKEY records, indicating + their key ID, algorithm and function + * Simplified nsupdate syntax and added readline support BIND 9.8.0 - BIND 9.8.0 includes a number of changes from BIND 9.7 and earlier - releases. New features include: - - - Built-in trust anchor for the root zone, which can be - switched on via "dnssec-validation auto;" - - Support for DNS64. - - Support for response policy zones (RPZ). - - Support for writable DLZ zones. - - Improved ease of configuration of GSS/TSIG for - interoperability with Active Directory - - Support for GOST signing algorithm for DNSSEC. - - Removed RTT Banding from server selection algorithm. - - New "static-stub" zone type. - - Allow configuration of resolver timeouts via - "resolver-query-timeout" option. - - The DLZ "dlopen" driver is now built by default. - - Added a new include file with function typedefs - for the DLZ "dlopen" driver. - - Made "--with-gssapi" default. - - More verbose error reporting from DLZ LDAP. +BIND 9.8.0 includes a number of changes from BIND 9.7 and earlier +releases. New features include: + + * Built-in trust anchor for the root zone, which can be switched on via + "dnssec-validation auto;" + * Support for DNS64. + * Support for response policy zones (RPZ). + * Support for writable DLZ zones. + * Improved ease of configuration of GSS/TSIG for interoperability with + Active Directory + * Support for GOST signing algorithm for DNSSEC. + * Removed RTT Banding from server selection algorithm. + * New "static-stub" zone type. + * Allow configuration of resolver timeouts via "resolver-query-timeout" + option. + * The DLZ "dlopen" driver is now built by default. + * Added a new include file with function typedefs for the DLZ "dlopen" + driver. + * Made "--with-gssapi" default. + * More verbose error reporting from DLZ LDAP. BIND 9.7.0 - BIND 9.7.0 includes a number of changes from BIND 9.6 and earlier - releases. Most are intended to simplify DNSSEC configuration. - New features include: - - - Fully automatic signing of zones by "named". - - Simplified configuration of DNSSEC Lookaside Validation (DLV). - - Simplified configuration of Dynamic DNS, using the "ddns-confgen" - command line tool or the "local" update-policy option. (As a side - effect, this also makes it easier to configure automatic zone - re-signing.) - - New named option "attach-cache" that allows multiple views to - share a single cache. - - DNS rebinding attack prevention. - - New default values for dnssec-keygen parameters. - - Support for RFC 5011 automated trust anchor maintenance - - Smart signing: simplified tools for zone signing and key - maintenance. - - The "statistics-channels" option is now available on Windows. - - A new DNSSEC-aware libdns API for use by non-BIND9 applications - - On some platforms, named and other binaries can now print out - a stack backtrace on assertion failure, to aid in debugging. - - A "tools only" installation mode on Windows, which only installs - dig, host, nslookup and nsupdate. - - Improved PKCS#11 support, including Keyper support and explicit - OpenSSL engine selection. +BIND 9.7.0 includes a number of changes from BIND 9.6 and earlier +releases. Most are intended to simplify DNSSEC configuration. New features +include: + + * Fully automatic signing of zones by "named". + * Simplified configuration of DNSSEC Lookaside Validation (DLV). + * Simplified configuration of Dynamic DNS, using the "ddns-confgen" + command line tool or the "local" update-policy option. (As a side + effect, this also makes it easier to configure automatic zone + re-signing.) + * New named option "attach-cache" that allows multiple views to share a + single cache. + * DNS rebinding attack prevention. + * New default values for dnssec-keygen parameters. + * Support for RFC 5011 automated trust anchor maintenance + * Smart signing: simplified tools for zone signing and key maintenance. + * The "statistics-channels" option is now available on Windows. + * A new DNSSEC-aware libdns API for use by non-BIND9 applications + * On some platforms, named and other binaries can now print out a stack + backtrace on assertion failure, to aid in debugging. + * A "tools only" installation mode on Windows, which only installs dig, + host, nslookup and nsupdate. + * Improved PKCS#11 support, including Keyper support and explicit + OpenSSL engine selection. BIND 9.6.0 - Full NSEC3 support - - Automatic zone re-signing - - New update-policy methods tcp-self and 6to4-self - - The BIND 8 resolver library, libbind, has been removed from the - BIND 9 distribution and is now available as a separate download. - - Change the default pid file location from /var/run to - /var/run/{named,lwresd} for improved chroot/setuid support. + * Full NSEC3 support + * Automatic zone re-signing + * New update-policy methods tcp-self and 6to4-self + * The BIND 8 resolver library, libbind, has been removed from the BIND 9 + distribution and is now available as a separate download. + * Change the default pid file location from /var/run to /var/run/ + {named,lwresd} for improved chroot/setuid support. BIND 9.5.0 - GSS-TSIG support (RFC 3645). - - DHCID support. - - Experimental http server and statistics support for named via xml. - - More detailed statistics counters including those supported in BIND 8. - - Faster ACL processing. - - Use Doxygen to generate internal documentation. - - Efficient LRU cache-cleaning mechanism. - - NSID support. + * GSS-TSIG support (RFC 3645). + * DHCID support. + * Experimental http server and statistics support for named via xml. + * More detailed statistics counters including those supported in BIND 8. + * Faster ACL processing. + * Use Doxygen to generate internal documentation. + * Efficient LRU cache-cleaning mechanism. + * NSID support. BIND 9.4.0 - Implemented "additional section caching (or acache)", an - internal cache framework for additional section content to - improve response performance. Several configuration options - were provided to control the behavior. - - New notify type 'master-only'. Enable notify for master - zones only. - - Accept 'notify-source' style syntax for query-source. - - rndc now allows addresses to be set in the server clauses. - - New option "allow-query-cache". This lets "allow-query" - be used to specify the default zone access level rather - than having to have every zone override the global value. - "allow-query-cache" can be set at both the options and view - levels. If "allow-query-cache" is not set then "allow-recursion" - is used if set, otherwise "allow-query" is used if set - unless "recursion no;" is set in which case "none;" is used, - otherwise the default (localhost; localnets;) is used. - - rndc: the source address can now be specified. - - ixfr-from-differences now takes master and slave in addition - to yes and no at the options and view levels. - - Allow the journal's name to be changed via named.conf. - - 'rndc notify zone [class [view]]' resend the NOTIFY messages - for the specified zone. - - 'dig +trace' now randomly selects the next servers to try. - Report if there is a bad delegation. - - Improve check-names error messages. - - Make public the function to read a key file, dst_key_read_public(). - - dig now returns the byte count for axfr/ixfr. - - allow-update is now settable at the options / view level. - - named-checkconf now checks the logging configuration. - - host now can turn on memory debugging flags with '-m'. - - Don't send notify messages to self. - - Perform sanity checks on NS records which refer to 'in zone' names. - - New zone option "notify-delay". Specify a minimum delay - between sets of NOTIFY messages. - - Extend adjusting TTL warning messages. - - Named and named-checkzone can now both check for non-terminal - wildcard records. - - "rndc freeze/thaw" now freezes/thaws all zones. - - named-checkconf now check acls to verify that they only - refer to existing acls. - - The server syntax has been extended to support a range of - servers. - - Report differences between hints and real NS rrset and - associated address records. - - Preserve the case of domain names in rdata during zone - transfers. - - Restructured the data locking framework using architecture - dependent atomic operations (when available), improving - response performance on multi-processor machines significantly. - x86, x86_64, alpha, powerpc, and mips are currently supported. - - UNIX domain controls are now supported. - - Add support for additional zone file formats for improving - loading performance. The masterfile-format option in - named.conf can be used to specify a non-default format. A - separate command named-compilezone was provided to generate - zone files in the new format. Additionally, the -I and -O - options for dnssec-signzone specify the input and output - formats. - - dnssec-signzone can now randomize signature end times - (dnssec-signzone -j jitter). - - Add support for CH A record. - - Add additional zone data constancy checks. named-checkzone - has extended checking of NS, MX and SRV record and the hosts - they reference. named has extended post zone load checks. - New zone options: check-mx and integrity-check. - - - edns-udp-size can now be overridden on a per server basis. - - dig can now specify the EDNS version when making a query. - - Added framework for handling multiple EDNS versions. - - Additional memory debugging support to track size and mctx - arguments. - - Detect duplicates of UDP queries we are recursing on and - drop them. New stats category "duplicates". - - "USE INTERNAL MALLOC" is now runtime selectable. - - The lame cache is now done on a basis - as some servers only appear to be lame for certain query - types. - - Limit the number of recursive clients that can be waiting - for a single query () to resolve. New - options clients-per-query and max-clients-per-query. - - dig: report the number of extra bytes still left in the - packet after processing all the records. - - Support for IPSECKEY rdata type. - - Raise the UDP recieve buffer size to 32k if it is less than 32k. - - x86 and x86_64 now have seperate atomic locking implementations. - - named-checkconf now validates update-policy entries. - - Attempt to make the amount of work performed in a iteration - self tuning. The covers nodes clean from the cache per - iteration, nodes written to disk when rewriting a master - file and nodes destroyed per iteration when destroying a - zone or a cache. - - ISC string copy API. - - Automatic empty zone creation for D.F.IP6.ARPA and friends. - Note: RFC 1918 zones are not yet covered by this but are - likely to be in a future release. - - New options: empty-server, empty-contact, empty-zones-enable - and disable-empty-zone. - - dig now has a '-q queryname' and '+showsearch' options. - - host/nslookup now continue (default)/fail on SERVFAIL. - - dig now warns if 'RA' is not set in the answer when 'RD' - was set in the query. host/nslookup skip servers that fail - to set 'RA' when 'RD' is set unless a server is explicitly - set. - - Integrate contibuted DLZ code into named. - - Integrate contibuted IDN code from JPNIC. - - libbind: corresponds to that from BIND 8.4.7. + * Implemented "additional section caching (or acache)", an internal + cache framework for additional section content to improve response + performance. Several configuration options were provided to control + the behavior. + * New notify type 'master-only'. Enable notify for master zones only. + * Accept 'notify-source' style syntax for query-source. + * rndc now allows addresses to be set in the server clauses. + * New option "allow-query-cache". This lets "allow-query" be used to + specify the default zone access level rather than having to have every + zone override the global value. "allow-query-cache" can be set at both + the options and view levels. If "allow-query-cache" is not set then + "allow-recursion" is used if set, otherwise "allow-query" is used if + set unless "recursion no;" is set in which case "none;" is used, + otherwise the default (localhost; localnets;) is used. + * rndc: the source address can now be specified. + * ixfr-from-differences now takes master and slave in addition to yes + and no at the options and view levels. + * Allow the journal's name to be changed via named.conf. + * 'rndc notify zone [class [view]]' resend the NOTIFY messages for the + specified zone. + * 'dig +trace' now randomly selects the next servers to try. Report if + there is a bad delegation. + * Improve check-names error messages. + * Make public the function to read a key file, dst_key_read_public(). + * dig now returns the byte count for axfr/ixfr. + * allow-update is now settable at the options / view level. + * named-checkconf now checks the logging configuration. + * host now can turn on memory debugging flags with '-m'. + * Don't send notify messages to self. + * Perform sanity checks on NS records which refer to 'in zone' names. + * New zone option "notify-delay". Specify a minimum delay between sets + of NOTIFY messages. + * Extend adjusting TTL warning messages. + * Named and named-checkzone can now both check for non-terminal wildcard + records. + * "rndc freeze/thaw" now freezes/thaws all zones. + * named-checkconf now check acls to verify that they only refer to + existing acls. + * The server syntax has been extended to support a range of servers. + * Report differences between hints and real NS rrset and associated + address records. + * Preserve the case of domain names in rdata during zone transfers. + * Restructured the data locking framework using architecture dependent + atomic operations (when available), improving response performance on + multi-processor machines significantly. x86, x86_64, alpha, powerpc, + and mips are currently supported. + * UNIX domain controls are now supported. + * Add support for additional zone file formats for improving loading + performance. The masterfile-format option in named.conf can be used to + specify a non-default format. A separate command named-compilezone was + provided to generate zone files in the new format. Additionally, the + -I and -O options for dnssec-signzone specify the input and output + formats. + * dnssec-signzone can now randomize signature end times (dnssec-signzone + -j jitter). + * Add support for CH A record. + * Add additional zone data constancy checks. named-checkzone has + extended checking of NS, MX and SRV record and the hosts they + reference. named has extended post zone load checks. New zone options: + check-mx and integrity-check. + * edns-udp-size can now be overridden on a per server basis. + * dig can now specify the EDNS version when making a query. + * Added framework for handling multiple EDNS versions. + * Additional memory debugging support to track size and mctx arguments. + * Detect duplicates of UDP queries we are recursing on and drop them. + New stats category "duplicates". + * "USE INTERNAL MALLOC" is now runtime selectable. + * The lame cache is now done on a basis as some servers only appear to + be lame for certain query types. + * Limit the number of recursive clients that can be waiting for a single + query () to resolve. New options clients-per-query and + max-clients-per-query. + * dig: report the number of extra bytes still left in the packet after + processing all the records. + * Support for IPSECKEY rdata type. + * Raise the UDP recieve buffer size to 32k if it is less than 32k. + * x86 and x86_64 now have seperate atomic locking implementations. + * named-checkconf now validates update-policy entries. + * Attempt to make the amount of work performed in a iteration self + tuning. The covers nodes clean from the cache per iteration, nodes + written to disk when rewriting a master file and nodes destroyed per + iteration when destroying a zone or a cache. + * ISC string copy API. + * Automatic empty zone creation for D.F.IP6.ARPA and friends. Note: RFC + 1918 zones are not yet covered by this but are likely to be in a + future release. + * New options: empty-server, empty-contact, empty-zones-enable and + disable-empty-zone. + * dig now has a '-q queryname' and '+showsearch' options. + * host/nslookup now continue (default)/fail on SERVFAIL. + * dig now warns if 'RA' is not set in the answer when 'RD' was set in + the query. host/nslookup skip servers that fail to set 'RA' when 'RD' + is set unless a server is explicitly set. + * Integrate contibuted DLZ code into named. + * Integrate contibuted IDN code from JPNIC. + * libbind: corresponds to that from BIND 8.4.7. BIND 9.3.0 - DNSSEC is now DS based (RFC 3658). - See also RFC 3845, doc/draft/draft-ietf-dnsext-dnssec-*. - - DNSSEC lookaside validation. - - check-names is now implemented. - rrset-order in more complete. - - IPv4/IPv6 transition support, dual-stack-servers. - - IXFR deltas can now be generated when loading master files, - ixfr-from-differences. - - It is now possible to specify the size of a journal, max-journal-size. - - It is now possible to define a named set of master servers to be - used in masters clause, masters. - - The advertised EDNS UDP size can now be set, edns-udp-size. - - allow-v6-synthesis has been obsoleted. - - NOTE: - * Zones containing MD and MF will now be rejected. - * dig, nslookup name. now report "Not Implemented" as - NOTIMP rather than NOTIMPL. This will have impact on scripts - that are looking for NOTIMPL. - - libbind: corresponds to that from BIND 8.4.5. + * DNSSEC is now DS based (RFC 3658). + * DNSSEC lookaside validation. + * check-names is now implemented. + * rrset-order is more complete. + * IPv4/IPv6 transition support, dual-stack-servers. + * IXFR deltas can now be generated when loading master files, + ixfr-from-differences. + * It is now possible to specify the size of a journal, max-journal-size. + * It is now possible to define a named set of master servers to be used + in masters clause, masters. + * The advertised EDNS UDP size can now be set, edns-udp-size. + * allow-v6-synthesis has been obsoleted. + * Zones containing MD and MF will now be rejected. + * dig, nslookup name. now report "Not Implemented" as NOTIMP rather than + NOTIMPL. This will have impact on scripts that are looking for + NOTIMPL. + * libbind: corresponds to that from BIND 8.4.5. BIND 9.2.0 - The size of the cache can now be limited using the - "max-cache-size" option. - - The server can now automatically convert RFC1886-style recursive - lookup requests into RFC2874-style lookups, when enabled using the - new option "allow-v6-synthesis". This allows stub resolvers that - support AAAA records but not A6 record chains or binary labels to - perform lookups in domains that make use of these IPv6 DNS - features. - - Performance has been improved. - - The man pages now use the more portable "man" macros rather than - the "mandoc" macros, and are installed by "make install". - - The named.conf parser has been completely rewritten. It now - supports "include" directives in more places such as inside "view" - statements, and it no longer has any reserved words. - - The "rndc status" command is now implemented. - - rndc can now be configured automatically. - - A BIND 8 compatible stub resolver library is now included in - lib/bind. - - OpenSSL has been removed from the distribution. This means that to - use DNSSEC, OpenSSL must be installed and the --with-openssl option - must be supplied to configure. This does not apply to the use of - TSIG, which does not require OpenSSL. - - The source distribution now builds on Windows. See - win32utils/readme1.txt and win32utils/win32-build.txt for details. - - This distribution also includes a new lightweight stub - resolver library and associated resolver daemon that fully - support forward and reverse lookups of both IPv4 and IPv6 - addresses. This library is considered experimental and - is not a complete replacement for the BIND 8 resolver library. - Applications that use the BIND 8 res_* functions to perform - DNS lookups or dynamic updates still need to be linked against - the BIND 8 libraries. For DNS lookups, they can also use the - new "getrrsetbyname()" API. - - BIND 9.2 is capable of acting as an authoritative server - for DNSSEC secured zones. This functionality is believed to - be stable and complete except for lacking support for - verifications involving wildcard records in secure zones. - - When acting as a caching server, BIND 9.2 can be configured - to perform DNSSEC secure resolution on behalf of its clients. - This part of the DNSSEC implementation is still considered - experimental. For detailed information about the state of the - DNSSEC implementation, see the file doc/misc/dnssec. - - There are a few known bugs: - - On some systems, IPv6 and IPv4 sockets interact in - unexpected ways. For details, see doc/misc/ipv6. - To reduce the impact of these problems, the server - no longer listens for requests on IPv6 addresses - by default. If you need to accept DNS queries over - IPv6, you must specify "listen-on-v6 { any; };" - in the named.conf options statement. - - FreeBSD prior to 4.2 (and 4.2 if running as non-root) - and OpenBSD prior to 2.8 log messages like - "fcntl(8, F_SETFL, 4): Inappropriate ioctl for device". - This is due to a bug in "/dev/random" and impacts the - server's DNSSEC support. - - OS X 10.1.4 (Darwin 5.4), OS X 10.1.5 (Darwin 5.5) and - OS X 10.2 (Darwin 6.0) reports errors like - "fcntl(3, F_SETFL, 4): Operation not supported by device". - This is due to a bug in "/dev/random" and impacts the - server's DNSSEC support. - - --with-libtool does not work on AIX. + * The size of the cache can now be limited using the "max-cache-size" + option. + * The server can now automatically convert RFC1886-style recursive + lookup requests into RFC2874-style lookups, when enabled using the new + option "allow-v6-synthesis". This allows stub resolvers that support + AAAA records but not A6 record chains or binary labels to perform + lookups in domains that make use of these IPv6 DNS features. + * Performance has been improved. + * The man pages now use the more portable "man" macros rather than the + "mandoc" macros, and are installed by "make install". + * The named.conf parser has been completely rewritten. It now supports + "include" directives in more places such as inside "view" statements, + and it no longer has any reserved words. + * The "rndc status" command is now implemented. + * rndc can now be configured automatically. + * A BIND 8 compatible stub resolver library is now included in lib/bind. + * OpenSSL has been removed from the distribution. This means that to use + DNSSEC, OpenSSL must be installed and the --with-openssl option must + be supplied to configure. This does not apply to the use of TSIG, + which does not require OpenSSL. + * The source distribution now builds on Windows. See win32utils/ + readme1.txt and win32utils/win32-build.txt for details. + * This distribution also includes a new lightweight stub resolver + library and associated resolver daemon that fully support forward and + reverse lookups of both IPv4 and IPv6 addresses. This library is + considered experimental and is not a complete replacement for the BIND + 8 resolver library. Applications that use the BIND 8 res_* functions + to perform DNS lookups or dynamic updates still need to be linked + against the BIND 8 libraries. For DNS lookups, they can also use the + new "getrrsetbyname()" API. + * BIND 9.2 is capable of acting as an authoritative server for DNSSEC + secured zones. This functionality is believed to be stable and + complete except for lacking support for verifications involving + wildcard records in secure zones. + * When acting as a caching server, BIND 9.2 can be configured to perform + DNSSEC secure resolution on behalf of its clients. This part of the + DNSSEC implementation is still considered experimental. For detailed + information about the state of the DNSSEC implementation, see the file + doc/misc/dnssec. - A bug in some versions of the Microsoft DNS server can cause zone - transfers from a BIND 9 server to a W2K server to fail. For details, - see the "Zone Transfers" section in doc/misc/migration. diff --git a/HISTORY.md b/HISTORY.md new file mode 100644 index 00000000000..4ea313ae858 --- /dev/null +++ b/HISTORY.md @@ -0,0 +1,532 @@ +### Functional enhancements from prior major releases of BIND 9 + +#### BIND 9.11 + +BIND 9.11.0 includes a number of changes from BIND 9.10 and earlier +releases. New features include: + +- Added support for Catalog Zones, a new method for provisioning servers: a + list of zones to be served is stored in a DNS zone, along with their + configuration parameters. Changes to the catalog zone are propagated to + slaves via normal AXFR/IXFR, whereupon the zones that are listed in it + are automatically added, deleted or reconfigured. +- Added support for "dnstap", a fast and flexible method of capturing and + logging DNS traffic. +- Added support for "dyndb", a new API for loading zone data from an + external database, developed by Red Hat for the FreeIPA project. +- "fetchlimit" quotas are now compiled in by default. These are for the + use of recursive resolvers that are are under high query load for domains + whose authoritative servers are nonresponsive or are experiencing a + denial of service attack: + - "fetches-per-server" limits the number of simultaneous queries that + can be sent to any single authoritative server. The configured value + is a starting point; it is automatically adjusted downward if the + server is partially or completely non-responsive. The algorithm used + to adjust the quota can be configured via the "fetch-quota-params" + option. + - "fetches-per-zone" limits the number of simultaneous queries that can + be sent for names within a single domain. (Note: Unlike + "fetches-per-server", this value is not self-tuning.) + - New stats counters have been added to count queries spilled due to + these quotas. +- Added a new "dnssec-keymgr" key mainenance utility, which can generate or + update keys as needed to ensure that a zone's keys match a defined DNSSEC + policy. +- The experimental "SIT" feature in BIND 9.10 has been renamed "COOKIE" and + is no longer optional. EDNS COOKIE is a mechanism enabling clients to + detect off-path spoofed responses, and servers to detect spoofed-source + queries. Clients that identify themselves using COOKIE options are not + subject to response rate limiting (RRL) and can receive larger UDP + responses. +- SERVFAIL responses can now be cached for a limited time (defaulting to 1 + second, with an upper limit of 30). This can reduce the frequency of + retries when a query is persistently failing. +- Added an "nsip-wait-recurse" switch to RPZ. This causes NSIP rules to be + skipped if a name server IP address isn't in the cache yet; the address + will be looked up and the rule will be applied on future queries. +- Added a Python RNDC module. This allows multiple commands to sent over a + persistent RNDC channel, which saves time. +- The "controls" block in named.conf can now grant read-only "rndc" access + to specified clients or keys. Read-only clients could, for example, check + "rndc status" but could not reconfigure or shut down the server. +- "rndc" commands can now return arbitrarily large amounts of text to the + caller. +- The zone serial number of a dynamically updatable zone can now be set via + "rndc signing -serial ". This allows inline-signing + zones to be set to a specific serial number. +- The new "rndc nta" command can be used to set a Negative Trust Anchor + (NTA), disabling DNSSEC validation for a specific domain; this can be + used when responses from a domain are known to be failing validation due + to administrative error rather than because of a spoofing attack. + Negative trust anchors are strictly temporary; by default they expire + after one hour, but can be configured to last up to one week. +- "rndc delzone" can now be used on zones that were not originally created + by "rndc addzone". +- "rndc modzone" reconfigures a single zone, without requiring the entire + server to be reconfigured. +- "rndc showzone" displays the current configuration of a zone. +- "rndc managed-keys" can be used to check the status of RFC 5001 managed + trust anchors, or to force trust anchors to be refreshed. +- "max-cache-size" can now be set to a percentage of available memory. The + default is 90%. +- Update forwarding performance has been improved by allowing a single TCP + connection to be shared by multiple updates. +- The EDNS Client Subnet (ECS) option is now supported for authoritative + servers; if a query contains an ECS option then ACLs containing "geoip" + or "ecs" elements can match against the the address encoded in the + option. This can be used to select a view for a query, so that different + answers can be provided depending on the client network. +- The EDNS EXPIRE option has been implemented on the client side, allowing + a slave server to set the expiration timer correctly when transferring + zone data from another slave server. +- The key generation and manipulation tools (dnssec-keygen, dnssec-settime, + dnssec-importkey, dnssec-keyfromlabel) now take "-Psync" and "-Dsync" + options to set the publication and deletion times of CDS and CDNSKEY + parent-synchronization records. Both named and dnssec-signzone can now + publish and remove these records at the scheduled times. +- A new "minimal-any" option reduces the size of UDP responses for query + type ANY by returning a single arbitrarily selected RRset instead of all + RRsets. +- A new "masterfile-style" zone option controls the formatting of text zone + files: When set to "full", a zone file is dumped in + single-line-per-record format. +- "serial-update-method" can now be set to "date". On update, the serial + number will be set to the current date in YYYYMMDDNN format. +- "dnssec-signzone -N date" sets the serial number to YYYYMMDDNN. +- "named -L " causes named to send log messages to the specified + file by default instead of to the system log. +- "dig +ttlunits" prints TTL values with time-unit suffixes: w, d, h, m, s + for weeks, days, hours, minutes, and seconds. +- "dig +unknownformat" prints dig output in RFC 3597 "unknown record" + presentation format. +- "dig +ednsopt" allows dig to set arbitrary EDNS options on requests. +- "dig +ednsflags" allows dig to set yet-to-be-defined EDNS flags on + requests. +- "mdig" is an alternate version of dig which sends multiple pipelined TCP + queries to a server. Instead of waiting for a response after sending a + query, it sends all queries immediately and displays responses in the + order received. +- "serial-query-rate" no longer controls NOTIFY messages. These are + separately controlled by "notify-rate" and "startup-notify-rate". +- "nsupdate" now performs "check-names" processing by default on records to + be added. This can be disabled with "check-names no". +- The statistics channel now supports DEFLATE compression, reducing the + size of the data sent over the network when querying statistics. +- New counters have been added to the statistics channel to track the sizes + of incoming queries and outgoing responses in histogram buckets, as + specified in RSSAC002. +- A new NXDOMAIN redirect method (option "nxdomain-redirect") has been + added, allowing redirection to a specified DNS namespace instead of a + single redirect zone. +- When starting up, named now ensures that no other named process is + already running. +- Files created by named to store information, including "mkeys" and "nzf" + files, are now named after their corresponding views unless the view name + contains characters incompatible with use as a filename. Old style + filenames (based on the hash of the view name) will still work. + +#### BIND 9.10.0 + +BIND 9.10.0 includes a number of changes from BIND 9.9 and earlier +releases. New features include: + + - DNS Response-rate limiting (DNS RRL), which blunts the + impact of reflection and amplification attacks, is always + compiled in and no longer requires a compile-time option + to enable it. + - An experimental "Source Identity Token" (SIT) EDNS option + is now available. Similar to DNS Cookies as invented by + Donald Eastlake 3rd, these are designed to enable clients + to detect off-path spoofed responses, and to enable servers + to detect spoofed-source queries. Servers can be configured + to send smaller responses to clients that have not identified + themselves using a SIT option, reducing the effectiveness of + amplification attacks. RRL processing has also been updated; + clients proven to be legitimate via SIT are not subject to + rate limiting. Use "configure --enable-sit" to enable this + feature in BIND. + - A new zone file format, "map", stores zone data in a + format that can be mapped directly into memory, allowing + significantly faster zone loading. + - "delv" (domain entity lookup and validation) is a new tool + with dig-like semantics for looking up DNS data and performing + internal DNSSEC validation. This allows easy validation in + environments where the resolver may not be trustworthy, and + assists with troubleshooting of DNSSEC problems. (NOTE: + In previous development releases of BIND 9.10, this utility + was called "delve". The spelling has been changed to avoid + confusion with the "delve" utility included with the Xapian + search engine.) + - Improved EDNS(0) processing for better resolver performance + and reliability over slow or lossy connections. + - A new "configure --with-tuning=large" option tunes certain + compiled-in constants and default settings to values better + suited to large servers with abundant memory. This can + improve performance on such servers, but will consume more + memory and may degrade performance on smaller systems. + - Substantial improvement in response-policy zone (RPZ) + performance. Up to 32 response-policy zones can be + configured with minimal performance loss. + - To improve recursive resolver performance, cache records + which are still being requested by clients can now be + automatically refreshed from the authoritative server + before they expire, reducing or eliminating the time + window in which no answer is available in the cache. + - New "rpz-client-ip" triggers and drop policies allowing + response policies based on the IP address of the client. + - ACLs can now be specified based on geographic location + using the MaxMind GeoIP databases. Use "configure + --with-geoip" to enable. + - Zone data can now be shared between views, allowing + multiple views to serve the same zones authoritatively + without storing multiple copies in memory. + - New XML schema (version 3) for the statistics channel + includes many new statistics and uses a flattened XML tree + for faster parsing. The older schema is now deprecated. + - A new stylesheet, based on the Google Charts API, displays + XML statistics in charts and graphs on javascript-enabled + browsers. + - The statistics channel can now provide data in JSON + format as well as XML. + - New stats counters track TCP and UDP queries received + per zone, and EDNS options received in total. + - The internal and export versions of the BIND libraries + (libisc, libdns, etc) have been unified so that external + library clients can use the same libraries as BIND itself. + - A new compile-time option, "configure --enable-native-pkcs11", + allows BIND 9 cryptography functions to use the PKCS#11 API + natively, so that BIND can drive a cryptographic hardware + service module (HSM) directly instead of using a modified + OpenSSL as an intermediary. (Note: This feature requires an + HSM to have a full implementation of the PKCS#11 API; many + current HSMs only have partial implementations. The new + "pkcs11-tokens" command can be used to check API completeness. + Native PKCS#11 is known to work with the Thales nShield HSM + and with SoftHSM version 2 from the Open DNSSEC project.) + - The new "max-zone-ttl" option enforces maximum TTLs for + zones. This can simplify the process of rolling DNSSEC keys + by guaranteeing that cached signatures will have expired + within the specified amount of time. + - "dig +subnet" sends an EDNS CLIENT-SUBNET option when + querying. + - "dig +expire" sends an EDNS EXPIRE option when querying. + When this option is sent with an SOA query to a server + that supports it, it will report the expiry time of + a slave zone. + - New "dnssec-coverage" tool to check DNSSEC key coverage + for a zone and report if a lapse in signing coverage has + been inadvertently scheduled. + - Signing algorithm flexibility and other improvements + for the "rndc" control channel. + - "named-checkzone" and "named-compilezone" can now read + journal files, allowing them to process dynamic zones. + - Multiple DLZ databases can now be configured. Individual + zones can be configured to be served from a specific DLZ + database. DLZ databases now serve zones of type "master" + and "redirect". + - "rndc zonestatus" reports information about a specified zone. + - "named" now listens on IPv6 as well as IPv4 interfaces + by default. + - "named" now preserves the capitalization of names + when responding to queries: for instance, a query for + "example.com" may be answered with "example.COM" if the + name was configured that way in the zone file. Some + clients have a bug causing them to depend on the older + behavior, in which the case of the answer always matched + the case of the query, rather than the case of the name + configured in the DNS. Such clients can now be specified + in the new "no-case-compress" ACL; this will restore the + older behavior of "named" for those clients only. + - new "dnssec-importkey" command allows the use of offline + DNSSEC keys with automatic DNSKEY management. + - New "named-rrchecker" tool to verify the syntactic + correctness of individual resource records. + - When re-signing a zone, the new "dnssec-signzone -Q" option + drops signatures from keys that are still published but are + no longer active. + - "named-checkconf -px" will print the contents of configuration + files with the shared secrets obscured, making it easier to + share configuration (e.g. when submitting a bug report) + without revealing private information. + - "rndc scan" causes named to re-scan network interfaces for + changes in local addresses. + - On operating systems with support for routing sockets, + network interfaces are re-scanned automatically whenever + they change. + - "tsig-keygen" is now available as an alternate command + name to use for "ddns-confgen". + +#### BIND 9.9.0 + +BIND 9.9.0 includes a number of changes from BIND 9.8 and earlier +releases. New features include: + +- Inline signing, allowing automatic DNSSEC signing of + master zones without modification of the zonefile, or + "bump in the wire" signing in slaves. +- NXDOMAIN redirection. +- New 'rndc flushtree' command clears all data under a given + name from the DNS cache. +- New 'rndc sync' command dumps pending changes in a dynamic + zone to disk without a freeze/thaw cycle. +- New 'rndc signing' command displays or clears signing status + records in 'auto-dnssec' zones. +- NSEC3 parameters for 'auto-dnssec' zones can now be set prior + to signing, eliminating the need to initially sign with NSEC. +- Startup time improvements on large authoritative servers. +- Slave zones are now saved in raw format by default. +- Several improvements to response policy zones (RPZ). +- Improved hardware scalability by using multiple threads + to listen for queries and using finer-grained client locking +- The 'also-notify' option now takes the same syntax as + 'masters', so it can used named masterlists and TSIG keys. +- 'dnssec-signzone -D' writes an output file containing only DNSSEC + data, which can be included by the primary zone file. +- 'dnssec-signzone -R' forces removal of signatures that are + not expired but were created by a key which no longer exists. +- 'dnssec-signzone -X' allows a separate expiration date to + be specified for DNSKEY signatures from other signatures. +- New '-L' option to dnssec-keygen, dnssec-settime, and + dnssec-keyfromlabel sets the default TTL for the key. +- dnssec-dsfromkey now supports reading from standard input, + to make it easier to convert DNSKEY to DS. +- RFC 1918 reverse zones have been added to the empty-zones + table per RFC 6303. +- Dynamic updates can now optionally set the zone's SOA serial + number to the current UNIX time. +- DLZ modules can now retrieve the source IP address of + the querying client. +- 'request-ixfr' option can now be set at the per-zone level. +- 'dig +rrcomments' turns on comments about DNSKEY records, + indicating their key ID, algorithm and function +- Simplified nsupdate syntax and added readline support + +#### BIND 9.8.0 + +BIND 9.8.0 includes a number of changes from BIND 9.7 and earlier +releases. New features include: + +- Built-in trust anchor for the root zone, which can be + switched on via "dnssec-validation auto;" +- Support for DNS64. +- Support for response policy zones (RPZ). +- Support for writable DLZ zones. +- Improved ease of configuration of GSS/TSIG for + interoperability with Active Directory +- Support for GOST signing algorithm for DNSSEC. +- Removed RTT Banding from server selection algorithm. +- New "static-stub" zone type. +- Allow configuration of resolver timeouts via + "resolver-query-timeout" option. +- The DLZ "dlopen" driver is now built by default. +- Added a new include file with function typedefs + for the DLZ "dlopen" driver. +- Made "--with-gssapi" default. +- More verbose error reporting from DLZ LDAP. + +#### BIND 9.7.0 + +BIND 9.7.0 includes a number of changes from BIND 9.6 and earlier +releases. Most are intended to simplify DNSSEC configuration. +New features include: + +- Fully automatic signing of zones by "named". +- Simplified configuration of DNSSEC Lookaside Validation (DLV). +- Simplified configuration of Dynamic DNS, using the "ddns-confgen" + command line tool or the "local" update-policy option. (As a side + effect, this also makes it easier to configure automatic zone + re-signing.) +- New named option "attach-cache" that allows multiple views to + share a single cache. +- DNS rebinding attack prevention. +- New default values for dnssec-keygen parameters. +- Support for RFC 5011 automated trust anchor maintenance +- Smart signing: simplified tools for zone signing and key + maintenance. +- The "statistics-channels" option is now available on Windows. +- A new DNSSEC-aware libdns API for use by non-BIND9 applications +- On some platforms, named and other binaries can now print out + a stack backtrace on assertion failure, to aid in debugging. +- A "tools only" installation mode on Windows, which only installs + dig, host, nslookup and nsupdate. +- Improved PKCS#11 support, including Keyper support and explicit + OpenSSL engine selection. + +#### BIND 9.6.0 + +- Full NSEC3 support +- Automatic zone re-signing +- New update-policy methods tcp-self and 6to4-self +- The BIND 8 resolver library, libbind, has been removed from the BIND 9 + distribution and is now available as a separate download. +- Change the default pid file location from /var/run to + /var/run/{named,lwresd} for improved chroot/setuid support. + +#### BIND 9.5.0 + +- GSS-TSIG support (RFC 3645). +- DHCID support. +- Experimental http server and statistics support for named via xml. +- More detailed statistics counters including those supported in BIND 8. +- Faster ACL processing. +- Use Doxygen to generate internal documentation. +- Efficient LRU cache-cleaning mechanism. +- NSID support. + +BIND 9.4.0 + +- Implemented "additional section caching (or acache)", an internal cache + framework for additional section content to improve response performance. + Several configuration options were provided to control the behavior. +- New notify type 'master-only'. Enable notify for master zones only. +- Accept 'notify-source' style syntax for query-source. +- rndc now allows addresses to be set in the server clauses. +- New option "allow-query-cache". This lets "allow-query" be used to + specify the default zone access level rather than having to have every + zone override the global value. "allow-query-cache" can be set at both + the options and view levels. If "allow-query-cache" is not set then + "allow-recursion" is used if set, otherwise "allow-query" is used if set + unless "recursion no;" is set in which case "none;" is used, otherwise + the default (localhost; localnets;) is used. +- rndc: the source address can now be specified. +- ixfr-from-differences now takes master and slave in addition to yes and + no at the options and view levels. +- Allow the journal's name to be changed via named.conf. +- 'rndc notify zone [class [view]]' resend the NOTIFY messages for the + specified zone. +- 'dig +trace' now randomly selects the next servers to try. Report if + there is a bad delegation. +- Improve check-names error messages. +- Make public the function to read a key file, dst_key_read_public(). +- dig now returns the byte count for axfr/ixfr. +- allow-update is now settable at the options / view level. +- named-checkconf now checks the logging configuration. +- host now can turn on memory debugging flags with '-m'. +- Don't send notify messages to self. +- Perform sanity checks on NS records which refer to 'in zone' names. +- New zone option "notify-delay". Specify a minimum delay between sets of + NOTIFY messages. +- Extend adjusting TTL warning messages. +- Named and named-checkzone can now both check for non-terminal wildcard + records. +- "rndc freeze/thaw" now freezes/thaws all zones. +- named-checkconf now check acls to verify that they only refer to existing + acls. +- The server syntax has been extended to support a range of servers. +- Report differences between hints and real NS rrset and associated address + records. +- Preserve the case of domain names in rdata during zone transfers. +- Restructured the data locking framework using architecture dependent + atomic operations (when available), improving response performance on + multi-processor machines significantly. x86, x86_64, alpha, powerpc, and + mips are currently supported. +- UNIX domain controls are now supported. +- Add support for additional zone file formats for improving loading + performance. The masterfile-format option in named.conf can be used to + specify a non-default format. A separate command named-compilezone was + provided to generate zone files in the new format. Additionally, the -I + and -O options for dnssec-signzone specify the input and output formats. +- dnssec-signzone can now randomize signature end times (dnssec-signzone -j + jitter). +- Add support for CH A record. +- Add additional zone data constancy checks. named-checkzone has extended + checking of NS, MX and SRV record and the hosts they reference. named + has extended post zone load checks. New zone options: check-mx and + integrity-check. +- edns-udp-size can now be overridden on a per server basis. +- dig can now specify the EDNS version when making a query. +- Added framework for handling multiple EDNS versions. +- Additional memory debugging support to track size and mctx arguments. +- Detect duplicates of UDP queries we are recursing on and drop them. New + stats category "duplicates". +- "USE INTERNAL MALLOC" is now runtime selectable. +- The lame cache is now done on a basis as some + servers only appear to be lame for certain query types. +- Limit the number of recursive clients that can be waiting for a single + query () to resolve. New options clients-per-query + and max-clients-per-query. +- dig: report the number of extra bytes still left in the packet after + processing all the records. +- Support for IPSECKEY rdata type. +- Raise the UDP recieve buffer size to 32k if it is less than 32k. +- x86 and x86_64 now have seperate atomic locking implementations. +- named-checkconf now validates update-policy entries. +- Attempt to make the amount of work performed in a iteration self tuning. + The covers nodes clean from the cache per iteration, nodes written to + disk when rewriting a master file and nodes destroyed per iteration when + destroying a zone or a cache. +- ISC string copy API. +- Automatic empty zone creation for D.F.IP6.ARPA and friends. Note: RFC + 1918 zones are not yet covered by this but are likely to be in a future + release. +- New options: empty-server, empty-contact, empty-zones-enable and + disable-empty-zone. +- dig now has a '-q queryname' and '+showsearch' options. +- host/nslookup now continue (default)/fail on SERVFAIL. +- dig now warns if 'RA' is not set in the answer when 'RD' was set in the + query. host/nslookup skip servers that fail to set 'RA' when 'RD' is set + unless a server is explicitly set. +- Integrate contibuted DLZ code into named. +- Integrate contibuted IDN code from JPNIC. +- libbind: corresponds to that from BIND 8.4.7. + +#### BIND 9.3.0 + +- DNSSEC is now DS based (RFC 3658). +- DNSSEC lookaside validation. +- check-names is now implemented. +- rrset-order is more complete. +- IPv4/IPv6 transition support, dual-stack-servers. +- IXFR deltas can now be generated when loading master files, + ixfr-from-differences. +- It is now possible to specify the size of a journal, max-journal-size. +- It is now possible to define a named set of master servers to be used in + masters clause, masters. +- The advertised EDNS UDP size can now be set, edns-udp-size. +- allow-v6-synthesis has been obsoleted. +- Zones containing MD and MF will now be rejected. +- dig, nslookup name. now report "Not Implemented" as NOTIMP rather than + NOTIMPL. This will have impact on scripts that are looking for NOTIMPL. +- libbind: corresponds to that from BIND 8.4.5. + +#### BIND 9.2.0 + +- The size of the cache can now be limited using the "max-cache-size" + option. +- The server can now automatically convert RFC1886-style recursive lookup + requests into RFC2874-style lookups, when enabled using the new option + "allow-v6-synthesis". This allows stub resolvers that support AAAA + records but not A6 record chains or binary labels to perform lookups in + domains that make use of these IPv6 DNS features. +- Performance has been improved. +- The man pages now use the more portable "man" macros rather than the + "mandoc" macros, and are installed by "make install". +- The named.conf parser has been completely rewritten. It now supports + "include" directives in more places such as inside "view" statements, and + it no longer has any reserved words. +- The "rndc status" command is now implemented. +- rndc can now be configured automatically. +- A BIND 8 compatible stub resolver library is now included in lib/bind. +- OpenSSL has been removed from the distribution. This means that to use + DNSSEC, OpenSSL must be installed and the --with-openssl option must be + supplied to configure. This does not apply to the use of TSIG, which + does not require OpenSSL. +- The source distribution now builds on Windows. See + win32utils/readme1.txt and win32utils/win32-build.txt for details. +- This distribution also includes a new lightweight stub resolver library + and associated resolver daemon that fully support forward and reverse + lookups of both IPv4 and IPv6 addresses. This library is considered + experimental and is not a complete replacement for the BIND 8 resolver + library. Applications that use the BIND 8 `res_*` functions to perform + DNS lookups or dynamic updates still need to be linked against the BIND 8 + libraries. For DNS lookups, they can also use the new "getrrsetbyname()" + API. +- BIND 9.2 is capable of acting as an authoritative server for DNSSEC + secured zones. This functionality is believed to be stable and complete + except for lacking support for verifications involving wildcard records + in secure zones. +- When acting as a caching server, BIND 9.2 can be configured to perform + DNSSEC secure resolution on behalf of its clients. This part of the + DNSSEC implementation is still considered experimental. For detailed + information about the state of the DNSSEC implementation, see the file + doc/misc/dnssec. diff --git a/Makefile.in b/Makefile.in index ba6153d9498..e20f6cf5b57 100644 --- a/Makefile.in +++ b/Makefile.in @@ -4,8 +4,6 @@ # 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/. -# $Id: Makefile.in,v 1.62 2011/09/06 04:06:37 marka Exp $ - srcdir = @srcdir@ VPATH = @srcdir@ top_srcdir = @top_srcdir@ @@ -20,7 +18,7 @@ MANPAGES = isc-config.sh.1 HTMLPAGES = isc-config.sh.html -MANOBJS = ${MANPAGES} ${HTMLPAGES} +MANOBJS = README HISTORY OPTIONS ${MANPAGES} ${HTMLPAGES} @BIND9_MAKE_RULES@ @@ -91,13 +89,19 @@ test-force: (test -f unit/unittest.sh && $(SHELL) unit/unittest.sh) || status=1; \ exit $$status -FAQ: FAQ.xml - ${XSLTPROC} doc/xsl/isc-docbook-text.xsl FAQ.xml | \ - LC_ALL=C ${W3M} -T text/html -dump -cols 72 >$@.tmp - mv $@.tmp $@ +README: README.md + ${PANDOC} --email-obfuscation=none -s -t html $< | \ + ${W3M} -dump -cols 75 -O ascii -T text/html > $@ + +HISTORY: HISTORY.md + ${PANDOC} --email-obfuscation=none -s -t html $< | \ + ${W3M} -dump -cols 75 -O ascii -T text/html > $@ + +OPTIONS: OPTIONS.md + ${PANDOC} --email-obfuscation=none -s -t html $< | \ + ${W3M} -dump -cols 75 -O ascii -T text/html > $@ unit:: sh ${top_srcdir}/unit/unittest.sh clean:: - rm -f FAQ.tmp diff --git a/OPTIONS b/OPTIONS new file mode 100644 index 00000000000..0be74b7aac6 --- /dev/null +++ b/OPTIONS @@ -0,0 +1,25 @@ +Setting the STD_CDEFINES environment variable before running configure can +be used to enable certain compile-time options that are not explicitly +defined in configure. + +Some of these settings are: + +Setting Description + Don't ovewrite memory when allocating or freeing +-DISC_MEM_FILL=0 it; this improves performance but makes + debugging more difficult. + Don't track memory allocations by file and line +-DISC_MEM_TRACKLINES=0 number; this improves performance but makes + debugging more difficult. +-DISC_FACILITY=LOG_LOCAL0 Change the default syslog facility for named +-DNS_CLIENT_DROPPORT=0 Disable dropping queries from particular + well-known ports: +-DCHECK_SIBLING=0 Don't check sibling glue in named-checkzone +-DCHECK_LOCAL=0 Don't check out-of-zone addresses in + named-checkzone +-DNS_RUN_PID_DIR=0 Create default PID files in ${localstatedir}/run + rather than ${localstatedir}/run/{named,lwresd}/ + Enable DNSSEC signature chasing support in dig. +-DDIG_SIGCHASE=1 (Note: This feature is deprecated. Use delv + instead.) + diff --git a/OPTIONS.md b/OPTIONS.md new file mode 100644 index 00000000000..7dfbe867cdc --- /dev/null +++ b/OPTIONS.md @@ -0,0 +1,17 @@ +Setting the `STD_CDEFINES` environment variable before running `configure` +can be used to enable certain compile-time options that are not explicitly +defined in `configure`. + +Some of these settings are: + +|Setting |Description | +|-----------------------------------|----------------------------------------| +|`-DISC_MEM_FILL=0`|Don't ovewrite memory when allocating or freeing it; this improves performance but makes debugging more difficult.| +|`-DISC_MEM_TRACKLINES=0`|Don't track memory allocations by file and line number; this improves performance but makes debugging more difficult.| +|`-DISC_FACILITY=LOG_LOCAL0`|Change the default syslog facility for `named`| +|`-DNS_CLIENT_DROPPORT=0`|Disable dropping queries from particular well-known ports:| +|`-DCHECK_SIBLING=0`|Don't check sibling glue in `named-checkzone`| +|`-DCHECK_LOCAL=0`|Don't check out-of-zone addresses in `named-checkzone`| +|`-DNS_RUN_PID_DIR=0`|Create default PID files in `${localstatedir}/run` rather than `${localstatedir}/run/{named,lwresd}/`| +|`-DDIG_SIGCHASE=1`|Enable DNSSEC signature chasing support in `dig`. (Note: This feature is deprecated. Use `delv` instead.)| + diff --git a/README b/README index a36600ca1a4..d10bcf7848a 100644 --- a/README +++ b/README @@ -1,374 +1,326 @@ BIND 9 - BIND version 9 is a major rewrite of nearly all aspects of the - underlying BIND architecture. Some of the important features of - BIND 9 are: +Contents + + 1. Introduction + 2. Reporting bugs and getting help + 3. Contributing to BIND + 4. BIND 9.12 features + 5. Building BIND + 6. Compile-time options + 7. Automated testing + 8. Documentation + 9. Change log +10. Acknowledgments + +Introduction + +BIND (Berkeley Internet Name Domain) is a complete, highly portable +implementation of the DNS (Domain Name System) protocol. + +The BIND name server, named, is able to serve as an authoritative name +server, recursive resolver, DNS forwarder, or all three simultaneously. It +implements views for split-horizon DNS, automatic DNSSEC zone signing and +key management, catalog zones to facilitate provisioning of zone data +throughout a name server constellation, response policy zones (RPZ) to +protect clients from malicious data, response rate limiting (RRL) and +recursive query limits to reduce distributed denial of service attacks, +and many other advanced DNS features. BIND also includes a suite of +administrative tools, including the dig and delv DNS lookup tools, +nsupdate for dynamic DNS zone updates, rndc for remote name server +administration, and more. - - DNS Security - DNSSEC (signed zones) - TSIG (signed DNS requests) - - - IP version 6 - Answers DNS queries on IPv6 sockets - IPv6 resource records (AAAA) - Experimental IPv6 Resolver Library - - - DNS Protocol Enhancements - IXFR, DDNS, Notify, EDNS0 - Improved standards conformance - - - Views - One server process can provide multiple "views" of - the DNS namespace, e.g. an "inside" view to certain - clients, and an "outside" view to others. - - - Multiprocessor Support - - - Improved Portability Architecture - - - BIND version 9 development has been underwritten by the following - organizations: - - Sun Microsystems, Inc. - Hewlett Packard - Compaq Computer Corporation - IBM - Process Software Corporation - Silicon Graphics, Inc. - Network Associates, Inc. - U.S. Defense Information Systems Agency - USENIX Association - Stichting NLnet - NLnet Foundation - Nominum, Inc. - - For a summary of functional enhancements in previous - releases, see the HISTORY file. - - For a detailed list of user-visible changes from - previous releases, see the CHANGES file. - - For up-to-date release notes and errata, see - http://www.isc.org/software/bind9/releasenotes - -BIND 9.12.0 - - BIND 9.12.0 includes a number of changes from BIND 9.10 and earlier - releases. New features include: - - - This release addresses the security flaws described in - CVE-2016-6170, CVE-2016-8864 and CVE-2016-9131. - -Building - - BIND 9 currently requires a UNIX system with an ANSI C compiler, - basic POSIX support, and a 64 bit integer type. - - We've had successful builds and tests on the following systems: - - COMPAQ Tru64 UNIX 5.1B - Fedora Core 6 - FreeBSD 4.10, 5.2.1, 6.2 - HP-UX 11.11 - Mac OS X 10.5 - NetBSD 3.x, 4.0-beta, 5.0-beta - OpenBSD 3.3 and up - Solaris 8, 9, 9 (x86), 10 - Ubuntu 7.04, 7.10 - Windows XP/2003/2008 - - NOTE: As of BIND 9.5.1, 9.4.3, and 9.3.6, older versions of - Windows, including Windows NT and Windows 2000, are no longer - supported. - - We have recent reports from the user community that a supported - version of BIND will build and run on the following systems: - - AIX 4.3, 5L - CentOS 4, 4.5, 5 - Darwin 9.0.0d1/ARM - Debian 4, 5, 6 - Fedora Core 5, 7, 8 - FreeBSD 6, 7, 8 - HP-UX 11.23 PA - MacOS X 10.5, 10.6, 10.7 - Red Hat Enterprise Linux 4, 5, 6 - SCO OpenServer 5.0.6 - Slackware 9, 10 - SuSE 9, 10 - - To build, just - - ./configure - make - - Do not use a parallel "make". - - Several environment variables that can be set before running - configure will affect compilation: - - CC - The C compiler to use. configure tries to figure - out the right one for supported systems. - - CFLAGS - C compiler flags. Defaults to include -g and/or -O2 - as supported by the compiler. Please include '-g' - if you need to set CFLAGS. - - STD_CINCLUDES - System header file directories. Can be used to specify - where add-on thread or IPv6 support is, for example. - Defaults to empty string. - - STD_CDEFINES - Any additional preprocessor symbols you want defined. - Defaults to empty string. - - Possible settings: - Change the default syslog facility of named/lwresd. - -DISC_FACILITY=LOG_LOCAL0 - Enable DNSSEC signature chasing support in dig. - (This feature is deprecated. Use `delv` instead.) - -DDIG_SIGCHASE=1 (sets -DDIG_SIGCHASE_TD=1 and - -DDIG_SIGCHASE_BU=1) - Disable dropping queries from particular well known ports. - -DNS_CLIENT_DROPPORT=0 - Sibling glue checking in named-checkzone is enabled by default. - To disable the default check set. -DCHECK_SIBLING=0 - named-checkzone checks out-of-zone addresses by default. - To disable this default set. -DCHECK_LOCAL=0 - To create the default pid files in ${localstatedir}/run rather - than ${localstatedir}/run/{named,lwresd}/ set. - -DNS_RUN_PID_DIR=0 - Enable workaround for Solaris kernel bug about /dev/poll - -DISC_SOCKET_USE_POLLWATCH=1 - The watch timeout is also configurable, e.g., - -DISC_SOCKET_POLLWATCH_TIMEOUT=20 - - LDFLAGS - Linker flags. Defaults to empty string. - - The following need to be set when cross compiling. - - BUILD_CC - The native C compiler. - BUILD_CFLAGS (optional) - BUILD_CPPFLAGS (optional) - Possible Settings: - -DNEED_OPTARG=1 (optarg is not declared in ) - BUILD_LDFLAGS (optional) - BUILD_LIBS (optional) - - On most platforms, BIND 9 is built with multithreading - support, allowing it to take advantage of multiple CPUs. - You can configure this by specifying "--enable-threads" or - "--disable-threads" on the configure command line. The default - is to enable threads, except on some older operating systems - on which threads are known to have had problems in the past. - (Note: Prior to BIND 9.10, the default was to disable threads on - Linux systems; this has been reversed. On Linux systems, the - threaded build is known to change BIND's behavior with respect - to file permissions; it may be necessary to specify a user with - the -u option when running named.) - - To build shared libraries, specify "--with-libtool" on the - configure command line. - - Certain compiled-in constants and default settings can be - increased to values better suited to large servers with abundant - memory resources (e.g, 64-bit servers with 12G or more of memory) - by specifying "--with-tuning=large" on the configure command - line. This can improve performance on big servers, but will - consume more memory and may degrade performance on smaller - systems. - - For the server to support DNSSEC, you need to build it - with crypto support. You must have OpenSSL 1.0.1t - or newer installed and specify "--with-openssl" on the - configure command line. If OpenSSL is installed under - a nonstandard prefix, you can tell configure where to - look for it using "--with-openssl=/prefix". - - To support the HTTP statistics channel, the server must - be linked with at least one of the following: libxml2 - (http://xmlsoft.org) or json-c (https://github.com/json-c). - If these are installed at a nonstandard prefix, use - "--with-libxml2=/prefix" or "--with-libjson=/prefix". - - To support compression on the HTTP statistics channel, the - server must be linked against libzlib (--with-zlib=/prefix). - - Python requires 'argparse' and 'ply' to be available. - 'argparse' is a standard module as of Python 2.7 and Python 3.2. - - On some platforms it is necessary to explicitly request large - file support to handle files bigger than 2GB. This can be - done by "--enable-largefile" on the configure command line. - - Support for the "fixed" rrset-order option can be enabled - or disabled by specifying "--enable-fixed-rrset" or - "--disable-fixed-rrset" on the configure command line. - The default is "disabled", to reduce memory footprint. - - If your operating system has integrated support for IPv6, it - will be used automatically. If you have installed KAME IPv6 - separately, use "--with-kame[=PATH]" to specify its location. - - "make install" will install "named" and the various BIND 9 libraries. - By default, installation is into /usr/local, but this can be changed - with the "--prefix" option when running "configure". - - You may specify the option "--sysconfdir" to set the directory - where configuration files like "named.conf" go by default, - and "--localstatedir" to set the default parent directory - of "run/named.pid". For backwards compatibility with BIND 8, - --sysconfdir defaults to "/etc" and --localstatedir defaults to - "/var" if no --prefix option is given. If there is a --prefix - option, sysconfdir defaults to "$prefix/etc" and localstatedir - defaults to "$prefix/var". - - To see additional configure options, run "configure --help". - Note that the help message does not reflect the BIND 8 - compatibility defaults for sysconfdir and localstatedir. - - If you're planning on making changes to the BIND 9 source, you - should also "make depend". If you're using Emacs, you might find - "make tags" helpful. - - If you need to re-run configure please run "make distclean" first. - This will ensure that all the option changes take. - - Building with gcc is not supported, unless gcc is the vendor's usual - compiler (e.g. the various BSD systems, Linux). - - Known compiler issues: - * gcc-3.2.1 and gcc-3.1.1 is known to cause problems with solaris-x86. - * gcc prior to gcc-3.2.3 ultrasparc generates incorrect code at -02. - * gcc-3.3.5 powerpc generates incorrect code at -02. - * Irix, MipsPRO 7.4.1m is known to cause problems. - - A limited test suite can be run with "make test". Many of - the tests require you to configure a set of virtual IP addresses - on your system, and some require Perl; see bin/tests/system/README - for details. - - SunOS 4 requires "printf" to be installed to make the shared - libraries. sh-utils-1.16 provides a "printf" which compiles - on SunOS 4. - -Known limitations - - Linux requires kernel build 2.6.39 or later to get the - performance benefits from using multiple sockets. +BIND 9 is a complete re-write of the BIND architecture that was used in +versions 4 and 8. Internet Systems Consortium (https://www.isc.org), a 501 +(c)(3) public benefit corporation dedicated to providing software and +services in support of the Internet infrastructure, developed BIND 9 and +is responsible for its ongoing maintenance and improvement. BIND is open +source software licenced under the terms of the Mozilla Public License, +version 2.0. + +For a summary of features introduced in past major releases of BIND, see +the file HISTORY. + +For a detailed list of changes made throughout the history of BIND 9, see +the file CHANGES. See below for details on the CHANGES file format. + +For up-to-date release notes and errata, see http://www.isc.org/software/ +bind9/releasenotes + +Reporting bugs and getting help + +Please report assertion failure errors and suspected security issues to +security-officer@isc.org. + +General bug reports can be sent to bind9-bugs@isc.org. + +Feature requests can be sent to bind-suggest@isc.org. + +Please note that, while ISC's ticketing system is not currently publicly +readable, this may change in the future. Please do not include information +in bug reports that you consider to be confidential. For example, when +sending the contents of your configuration file, it is advisable to +obscure key secrets; this can be done automatically by using +named-checkconf -px. + +Professional support and training for BIND are available from ISC at +https://www.isc.org/support. + +To join the BIND Users mailing list, or view the archives, visit https:// +lists.isc.org/mailman/listinfo/bind-users. + +If you're planning on making changes to the BIND 9 source code, you may +also want to join the BIND Workers mailing list, at https://lists.isc.org/ +mailman/listinfo/bind-workers. + +Contributing to BIND + +A public git repository for BIND is maintained at http://www.isc.org/git/, +and also on Github at https://github.com/isc-projects. + +Information for BIND contributors can be found in the following files: - +General information: doc/dev/contrib.md - BIND 9 code style: doc/dev/ +style.md - BIND architecture and developer guide: doc/dev/dev.md + +Patches for BIND may be submitted either as Github pull requests or via +email. When submitting a patch via email, please prepend the subject +header with "[PATCH]" so it will be easier for us to find. If your patch +introduces a new feature in BIND, please submit it to bind-suggest@isc.org +; if it fixes a bug, please submit it to bind9-bugs@isc.org. + +BIND 9.12 features + +BIND 9.12.0 is the newest development branch of BIND 9. It includes a +number of changes from BIND 9.11 and earlier releases. New features +include: + + * The query handling code has been substantially refactored for improved + readability, maintainability and testability + * dnstap output files can now be configured to roll automatically when + reaching a given size + * Log file timestamps can now also be formatted in ISO 8601 (local) or + ISO 8601 (UTC) formats + * Logging channels and dnstap output files can now be configured to use + a timestamp as the suffix when rolling to a new file + * named-checkconf -l lists zones found in named.conf + * Added support for the EDNS Padding and Keepalive options + +Building BIND + +BIND requires a UNIX or Linux system with an ANSI C compiler, basic POSIX +support, and a 64-bit integer type. Successful builds have been observed +on many versions of Linux and UNIX, including RedHat, Fedora, Debian, +Ubuntu, SuSE, Slackware, FreeBSD, NetBSD, OpenBSD, Mac OS X, Solaris, +HP-UX, AIX, SCO OpenServer, and OpenWRT. + +BIND is also available for Windows XP, 2003, 2008, and higher. See +win32utils/readme1st.txt for details on building for Windows systems. + +To build on a UNIX or Linux system, use: + + $ ./configure + $ make + +(NOTE: Using multiple processors in make is not reliable and is not +advised.) + +If you're planning on making changes to the BIND 9 source, you should run +make depend. If you're using Emacs, you might find make tags helpful. + +Several environment variables that can be set before running configure +will affect compilation: + +Variable Description +CC The C compiler to use. configure tries to figure out the + right one for supported systems. + C compiler flags. Defaults to include -g and/or -O2 as +CFLAGS supported by the compiler. Please include '-g' if you need + to set CFLAGS. + System header file directories. Can be used to specify +STD_CINCLUDES where add-on thread or IPv6 support is, for example. + Defaults to empty string. + Any additional preprocessor symbols you want defined. +STD_CDEFINES Defaults to empty string. For a list of possible settings, + see the file OPTIONS. +LDFLAGS Linker flags. Defaults to empty string. +BUILD_CC Needed when cross-compiling: the native C compiler to use + when building for the target system. +BUILD_CFLAGS Optional, used for cross-compiling +BUILD_CPPFLAGS +BUILD_LDFLAGS +BUILD_LIBS + +Compile-time options + +To see a full list of configuration options, run configure --help. + +On most platforms, BIND 9 is built with multithreading support, allowing +it to take advantage of multiple CPUs. You can configure this by +specifying --enable-threads or --disable-threads on the configure command +line. The default is to enable threads, except on some older operating +systems on which threads are known to have had problems in the past. +(Note: Prior to BIND 9.10, the default was to disable threads on Linux +systems; this has now been reversed. On Linux systems, the threaded build +is known to change BIND's behavior with respect to file permissions; it +may be necessary to specify a user with the -u option when running named.) + +To build shared libraries, specify --with-libtool on the configure command +line. + +Certain compiled-in constants and default settings can be increased to +values better suited to large servers with abundant memory resources (e.g, +64-bit servers with 12G or more of memory) by specifying --with-tuning= +large on the configure command line. This can improve performance on big +servers, but will consume more memory and may degrade performance on +smaller systems. + +For the server to support DNSSEC, you need to build it with crypto +support. To use OpenSSL, you should have OpenSSL 1.0.2e or newer +installed. If the OpenSSL library is installed in a nonstandard location, +specify the prefix using "--with-openssl=/prefix" on the configure command +line. To use a PKCS#11 hardware service module for cryptographic +operations, specify the path to the PKCS#11 provider library using +"--with-pkcs11=/prefix", and configure BIND with "--enable-native-pkcs11". + +To support the HTTP statistics channel, the server must be linked with at +least one of the following: libxml2 http://xmlsoft.org or json-c https:// +github.com/json-c. If these are installed at a nonstandard location, +specify the prefix using --with-libxml2=/prefix or --with-libjson=/prefix. + +To support compression on the HTTP statistics channel, the server must be +linked against libzlib. If this is installed in a nonstandard location, +specify the prefix using --with-zlib=/prefix. + +To support storing configuration data for runtime-added zones in an LMDB +database, the server must be linked with liblmdb. If this is installed in +a nonstandard location, specify the prefix using "with-lmdb=/prefix". + +To support GeoIP location-based ACLs, the server must be linked with +libGeoIP. This is not turned on by default; BIND must be configured with +"--with-geoip". If the library is installed in a nonstandard location, use +specify the prefix using "--with-geoip=/prefix". + +For DNSTAP packet logging, you must have libfstrm https://github.com/ +farsightsec/fstrm and libprotobuf-c https://developers.google.com/ +protocol-buffers, and BIND must be configured with "--enable-dnstap". + +Python requires the 'argparse' and 'ply' modules to be available. +'argparse' is a standard module as of Python 2.7 and Python 3.2. 'ply' is +available from https://pypi.python.org/pypi/ply. + +On some platforms it is necessary to explicitly request large file support +to handle files bigger than 2GB. This can be done by using +--enable-largefile on the configure command line. + +Support for the "fixed" rrset-order option can be enabled or disabled by +specifying --enable-fixed-rrset or --disable-fixed-rrset on the configure +command line. By default, fixed rrset-order is disabled to reduce memory +footprint. + +If your operating system has integrated support for IPv6, it will be used +automatically. If you have installed KAME IPv6 separately, use --with-kame +[=PATH] to specify its location. + +make install will install named and the various BIND 9 libraries. By +default, installation is into /usr/local, but this can be changed with the +--prefix option when running configure. + +You may specify the option --sysconfdir to set the directory where +configuration files like named.conf go by default, and --localstatedir to +set the default parent directory of run/named.pid. For backwards +compatibility with BIND 8, --sysconfdir defaults to /etc and +--localstatedir defaults to /var if no --prefix option is given. If there +is a --prefix option, sysconfdir defaults to $prefix/etc and localstatedir +defaults to $prefix/var. + +Automated testing + +A system test suite can be run with make test. The system tests require +you to configure a set of virtual IP addresses on your system (this allows +multiple servers to run locally and communicate with one another). These +IP addresses can be configured by by running the script bin/tests/system/ +ifconfig.sh up as root. + +Some tests require Perl and the Net::DNS and/or IO::Socket::INET6 modules, +and will be skipped if these are not available. Some tests require Python +and the 'dnspython' module and will be skipped if these are not available. +See bin/tests/system/README for further details. + +Unit tests are implemented using Automated Testing Framework (ATF). To run +them, use configure --with-atf, then run make test or make unit. Documentation - The BIND 9 Administrator Reference Manual is included with the - source distribution in DocBook XML and HTML format, in the - doc/arm directory. - - Some of the programs in the BIND 9 distribution have man pages - in their directories. In particular, the command line - options of "named" are documented in /bin/named/named.8. - There is now also a set of man pages for the lwres library. - - If you are upgrading from BIND 8, please read the migration - notes in doc/misc/migration. If you are upgrading from - BIND 4, read doc/misc/migration-4to9. - - Frequently asked questions and their answers can be found in - FAQ. - - Additional information on various subjects can be found - in the other README files. - - -Change Log - - A detailed list of all changes to BIND 9 is included in the - file CHANGES, with the most recent changes listed first. - Change notes include tags indicating the category of the - change that was made; these categories are: - - [func] New feature - - [bug] General bug fix - - [security] Fix for a significant security flaw - - [experimental] Used for new features when the syntax - or other aspects of the design are still - in flux and may change - - [port] Portability enhancement - - [maint] Updates to built-in data such as root - server addresses and keys - - [tuning] Changes to built-in configuration defaults - and constants to improve performance - - [performance] Other changes to improve server performance - - [protocol] Updates to the DNS protocol such as new - RR types - - [test] Changes to the automatic tests, not - affecting server functionality - - [cleanup] Minor corrections and refactoring - - [doc] Documentation - - [contrib] Changes to the contributed tools and - libraries in the 'contrib' subdirectory - - [placeholder] Used in the master development branch to - reserve change numbers for use in other - branches, e.g. when fixing a bug that only - exists in older releases - - In general, [func] and [experimental] tags will only appear - in new-feature releases (i.e., those with version numbers - ending in zero). Some new functionality may be backported to - older releases on a case-by-case basis. All other change - types may be applied to all currently-supported releases. - - -Bug Reports and Mailing Lists - - Bug reports should be sent to: - - bind9-bugs@isc.org - - Feature requests can be sent to: - - bind-suggest@isc.org - - To join or view the archives of the BIND Users mailing list, - visit: - - https://lists.isc.org/mailman/listinfo/bind-users - - If you're planning on making changes to the BIND 9 source - code, you may also want to join the BIND Workers mailing - list: - - https://lists.isc.org/mailman/listinfo/bind-workers - - Information on read-only Git access, coding style and developer - guidelines can be found at: - - http://www.isc.org/git/ - +The BIND 9 Administrator Reference Manual is included with the source +distribution, in DocBook XML, HTML and PDF format, in the doc/arm +directory. + +Some of the programs in the BIND 9 distribution have man pages in their +directories. In particular, the command line options of named are +documented in bin/named/named.8. + +Frequently (and not-so-frequently) asked questions and their answers can +be found in the ISC Knowledge Base at https://kb.isc.org. + +Additional information on various subjects can be found in other README +files throughout the source tree. + +Change log + +A detailed list of all changes that have been made throughout the +development BIND 9 is included in the file CHANGES, with the most recent +changes listed first. Change notes include tags indicating the category of +the change that was made; these categories are: + +Category Description +[func] New feature +[bug] General bug fix +[security] Fix for a significant security flaw +[experimental] Used for new features when the syntax or other aspects of + the design are still in flux and may change +[port] Portability enhancement +[maint] Updates to built-in data such as root server addresses and + keys +[tuning] Changes to built-in configuration defaults and constants to + improve performance +[performance] Other changes to improve server performance +[protocol] Updates to the DNS protocol such as new RR types +[test] Changes to the automatic tests, not affecting server + functionality +[cleanup] Minor corrections and refactoring +[doc] Documentation +[contrib] Changes to the contributed tools and libraries in the + 'contrib' subdirectory + Used in the master development branch to reserve change +[placeholder] numbers for use in other branches, e.g. when fixing a bug + that only exists in older releases + +In general, [func] and [experimental] tags will only appear in new-feature +releases (i.e., those with version numbers ending in zero). Some new +functionality may be backported to older releases on a case-by-case basis. +All other change types may be applied to all currently-supported releases. Acknowledgments - - This product includes software developed by the OpenSSL Project - for use in the OpenSSL Toolkit. (http://www.OpenSSL.org/). - - This product includes cryptographic software written by Eric - Young (eay@cryptsoft.com). - - This product includes software written by Tim Hudson - (tjh@cryptsoft.com). + * The original development of BIND 9 was underwritten by the following + organizations: + + Sun Microsystems, Inc. + Hewlett Packard + Compaq Computer Corporation + IBM + Process Software Corporation + Silicon Graphics, Inc. + Network Associates, Inc. + U.S. Defense Information Systems Agency + USENIX Association + Stichting NLnet - NLnet Foundation + Nominum, Inc. + + * This product includes software developed by the OpenSSL Project for + use in the OpenSSL Toolkit. http://www.OpenSSL.org/ + * This product includes cryptographic software written by Eric Young + (eay@cryptsoft.com) + * This product includes software written by Tim Hudson + (tjh@cryptsoft.com) + diff --git a/README.md b/README.md new file mode 100644 index 00000000000..395dfb32001 --- /dev/null +++ b/README.md @@ -0,0 +1,324 @@ +# BIND 9 + +### Contents + +1. [Introduction](#intro) +1. [Reporting bugs and getting help](#help) +1. [Contributing to BIND](#contrib) +1. [BIND 9.12 features](#features) +1. [Building BIND](#build) +1. [Compile-time options](#opts) +1. [Automated testing](#testing) +1. [Documentation](#doc) +1. [Change log](#changes) +1. [Acknowledgments](#ack) + +### Introduction + +BIND (Berkeley Internet Name Domain) is a complete, highly portable +implementation of the DNS (Domain Name System) protocol. + +The BIND name server, `named`, is able to serve as an authoritative name +server, recursive resolver, DNS forwarder, or all three simultaneously. It +implements views for split-horizon DNS, automatic DNSSEC zone signing and +key management, catalog zones to facilitate provisioning of zone data +throughout a name server constellation, response policy zones (RPZ) to +protect clients from malicious data, response rate limiting (RRL) and +recursive query limits to reduce distributed denial of service attacks, +and many other advanced DNS features. BIND also includes a suite of +administrative tools, including the `dig` and `delv` DNS lookup tools, +`nsupdate` for dynamic DNS zone updates, `rndc` for remote name server +administration, and more. + +BIND 9 is a complete re-write of the BIND architecture that was used in +versions 4 and 8. Internet Systems Consortium +([https://www.isc.org](https://www.isc.org)), a 501(c)(3) public benefit +corporation dedicated to providing software and services in support of the +Internet infrastructure, developed BIND 9 and is responsible for its +ongoing maintenance and improvement. BIND is open source software +licenced under the terms of the Mozilla Public License, version 2.0. + +For a summary of features introduced in past major releases of BIND, +see the file [HISTORY](HISTORY.md). + +For a detailed list of changes made throughout the history of BIND 9, see +the file [CHANGES](CHANGES). See [below](#changes) for details on the +CHANGES file format. + +For up-to-date release notes and errata, see +[http://www.isc.org/software/bind9/releasenotes](http://www.isc.org/software/bind9/releasenotes) + +### Reporting bugs and getting help + +Please report assertion failure errors and suspected security issues to +[security-officer@isc.org](mailto:security-officer@isc.org). + +General bug reports can be sent to +[bind9-bugs@isc.org](mailto:bind9-bugs@isc.org). + +Feature requests can be sent to +[bind-suggest@isc.org](mailto:bind-suggest@isc.org). + +Please note that, while ISC's ticketing system is not currently publicly +readable, this may change in the future. Please do not include information +in bug reports that you consider to be confidential. For example, when +sending the contents of your configuration file, it is advisable to obscure +key secrets; this can be done automatically by using `named-checkconf +-px`. + +Professional support and training for BIND are available from +ISC at [https://www.isc.org/support](https://www.isc.org/support). + +To join the __BIND Users__ mailing list, or view the archives, visit +[https://lists.isc.org/mailman/listinfo/bind-users](https://lists.isc.org/mailman/listinfo/bind-users). + +If you're planning on making changes to the BIND 9 source code, you +may also want to join the __BIND Workers__ mailing list, at +[https://lists.isc.org/mailman/listinfo/bind-workers](https://lists.isc.org/mailman/listinfo/bind-workers). + +### Contributing to BIND + +A public git repository for BIND is maintained at +[http://www.isc.org/git/](http://www.isc.org/git/), and also on Github +at [https://github.com/isc-projects](https://github.com/isc-projects). + +Information for BIND contributors can be found in the following files: +- General information: [doc/dev/contrib.md](doc/dev/contrib.md) +- BIND 9 code style: [doc/dev/style.md](doc/dev/style.md) +- BIND architecture and developer guide: [doc/dev/dev.md](doc/dev/dev.md) + +Patches for BIND may be submitted either as Github pull requests +or via email. When submitting a patch via email, please prepend the +subject header with "`[PATCH]`" so it will be easier for us to find. +If your patch introduces a new feature in BIND, please submit it to +[bind-suggest@isc.org](mailto:bind-suggest@isc.org); if it fixes a bug, +please submit it to [bind9-bugs@isc.org](mailto:bind9-bugs@isc.org). + +### BIND 9.12 features + +BIND 9.12.0 is the newest development branch of BIND 9. It includes a +number of changes from BIND 9.11 and earlier releases. New features +include: + +* The query handling code has been substantially refactored for improved + readability, maintainability and testability +* `dnstap` output files can now be configured to roll automatically when + reaching a given size +* Log file timestamps can now also be formatted in ISO 8601 (local) or ISO + 8601 (UTC) formats +* Logging channels and `dnstap` output files can now be configured to use a + timestamp as the suffix when rolling to a new file +* `named-checkconf -l` lists zones found in `named.conf` +* Added support for the EDNS Padding and Keepalive options + +### Building BIND + +BIND requires a UNIX or Linux system with an ANSI C compiler, basic POSIX +support, and a 64-bit integer type. Successful builds have been observed on +many versions of Linux and UNIX, including RedHat, Fedora, Debian, Ubuntu, +SuSE, Slackware, FreeBSD, NetBSD, OpenBSD, Mac OS X, Solaris, HP-UX, AIX, +SCO OpenServer, and OpenWRT. + +BIND is also available for Windows XP, 2003, 2008, and higher. See +`win32utils/readme1st.txt` for details on building for Windows systems. + +To build on a UNIX or Linux system, use: + + $ ./configure + $ make + +(NOTE: Using multiple processors in `make` is not reliable and is not +advised.) + +If you're planning on making changes to the BIND 9 source, you should run +`make depend`. If you're using Emacs, you might find `make tags` helpful. + +Several environment variables that can be set before running `configure` will +affect compilation: + +|Variable|Description | +|--------------------|-----------------------------------------------| +|`CC`|The C compiler to use. `configure` tries to figure out the right one for supported systems.| +|`CFLAGS`|C compiler flags. Defaults to include -g and/or -O2 as supported by the compiler. Please include '-g' if you need to set `CFLAGS`. | +|`STD_CINCLUDES`|System header file directories. Can be used to specify where add-on thread or IPv6 support is, for example. Defaults to empty string.| +|`STD_CDEFINES`|Any additional preprocessor symbols you want defined. Defaults to empty string. For a list of possible settings, see the file [OPTIONS](OPTIONS.md).| +|`LDFLAGS`|Linker flags. Defaults to empty string.| +|`BUILD_CC`|Needed when cross-compiling: the native C compiler to use when building for the target system.| +|`BUILD_CFLAGS`|Optional, used for cross-compiling| +|`BUILD_CPPFLAGS`|| +|`BUILD_LDFLAGS`|| +|`BUILD_LIBS`|| + +#### Compile-time options + +To see a full list of configuration options, run `configure --help`. + +On most platforms, BIND 9 is built with multithreading support, allowing it +to take advantage of multiple CPUs. You can configure this by specifying +`--enable-threads` or `--disable-threads` on the `configure` command line. +The default is to enable threads, except on some older operating systems on +which threads are known to have had problems in the past. (Note: Prior to +BIND 9.10, the default was to disable threads on Linux systems; this has +now been reversed. On Linux systems, the threaded build is known to change +BIND's behavior with respect to file permissions; it may be necessary to +specify a user with the -u option when running `named`.) + +To build shared libraries, specify `--with-libtool` on the `configure` +command line. + +Certain compiled-in constants and default settings can be increased to +values better suited to large servers with abundant memory resources (e.g, +64-bit servers with 12G or more of memory) by specifying +`--with-tuning=large` on the `configure` command line. This can improve +performance on big servers, but will consume more memory and may degrade +performance on smaller systems. + +For the server to support DNSSEC, you need to build it with crypto support. +To use OpenSSL, you should have OpenSSL 1.0.2e or newer installed. If the +OpenSSL library is installed in a nonstandard location, specify the prefix +using "--with-openssl=/prefix" on the configure command line. To use a +PKCS#11 hardware service module for cryptographic operations, specify the +path to the PKCS#11 provider library using "--with-pkcs11=/prefix", and +configure BIND with "--enable-native-pkcs11". + +To support the HTTP statistics channel, the server must be linked with at +least one of the following: libxml2 +[http://xmlsoft.org](http://xmlsoft.org) or json-c +[https://github.com/json-c](https://github.com/json-c). If these are +installed at a nonstandard location, specify the prefix using +`--with-libxml2=/prefix` or `--with-libjson=/prefix`. + +To support compression on the HTTP statistics channel, the server must be +linked against libzlib. If this is installed in a nonstandard location, +specify the prefix using `--with-zlib=/prefix`. + +To support storing configuration data for runtime-added zones in an LMDB +database, the server must be linked with liblmdb. If this is installed in a +nonstandard location, specify the prefix using "with-lmdb=/prefix". + +To support GeoIP location-based ACLs, the server must be linked with +libGeoIP. This is not turned on by default; BIND must be configured with +"--with-geoip". If the library is installed in a nonstandard location, use +specify the prefix using "--with-geoip=/prefix". + +For DNSTAP packet logging, you must have libfstrm +[https://github.com/farsightsec/fstrm](https://github.com/farsightsec/fstrm) +and libprotobuf-c +[https://developers.google.com/protocol-buffers](https://developers.google.com/protocol-buffers), +and BIND must be configured with "--enable-dnstap". + +Python requires the 'argparse' and 'ply' modules to be available. +'argparse' is a standard module as of Python 2.7 and Python 3.2. +'ply' is available from [https://pypi.python.org/pypi/ply](https://pypi.python.org/pypi/ply). + +On some platforms it is necessary to explicitly request large file support +to handle files bigger than 2GB. This can be done by using +`--enable-largefile` on the `configure` command line. + +Support for the "fixed" rrset-order option can be enabled or disabled by +specifying `--enable-fixed-rrset` or `--disable-fixed-rrset` on the +configure command line. By default, fixed rrset-order is disabled to +reduce memory footprint. + +If your operating system has integrated support for IPv6, it will be used +automatically. If you have installed KAME IPv6 separately, use +`--with-kame[=PATH]` to specify its location. + +`make install` will install `named` and the various BIND 9 libraries. By +default, installation is into /usr/local, but this can be changed with the +`--prefix` option when running `configure`. + +You may specify the option `--sysconfdir` to set the directory where +configuration files like `named.conf` go by default, and `--localstatedir` +to set the default parent directory of `run/named.pid`. For backwards +compatibility with BIND 8, `--sysconfdir` defaults to `/etc` and +`--localstatedir` defaults to `/var` if no `--prefix` option is given. If +there is a `--prefix` option, sysconfdir defaults to `$prefix/etc` and +localstatedir defaults to `$prefix/var`. + +### Automated testing + +A system test suite can be run with `make test`. The system tests require +you to configure a set of virtual IP addresses on your system (this allows +multiple servers to run locally and communicate with one another). These +IP addresses can be configured by by running the script +`bin/tests/system/ifconfig.sh up` as root. + +Some tests require Perl and the Net::DNS and/or IO::Socket::INET6 modules, +and will be skipped if these are not available. Some tests require Python +and the 'dnspython' module and will be skipped if these are not available. +See bin/tests/system/README for further details. + +Unit tests are implemented using Automated Testing Framework (ATF). +To run them, use `configure --with-atf`, then run `make test` or +`make unit`. + +### Documentation + +The *BIND 9 Administrator Reference Manual* is included with the source +distribution, in DocBook XML, HTML and PDF format, in the `doc/arm` +directory. + +Some of the programs in the BIND 9 distribution have man pages in their +directories. In particular, the command line options of `named` are +documented in `bin/named/named.8`. + +Frequently (and not-so-frequently) asked questions and their answers +can be found in the ISC Knowledge Base at +[https://kb.isc.org](https://kb.isc.org). + +Additional information on various subjects can be found in other +`README` files throughout the source tree. + +### Change log + +A detailed list of all changes that have been made throughout the +development BIND 9 is included in the file CHANGES, with the most recent +changes listed first. Change notes include tags indicating the category of +the change that was made; these categories are: + +|Category |Description | +|-------------- |-----------------------------------------------| +| [func] | New feature | +| [bug] | General bug fix | +| [security] | Fix for a significant security flaw | +| [experimental] | Used for new features when the syntax or other aspects of the design are still in flux and may change | +| [port] | Portability enhancement | +| [maint] | Updates to built-in data such as root server addresses and keys | +| [tuning] | Changes to built-in configuration defaults and constants to improve performance | +| [performance] | Other changes to improve server performance | +| [protocol] | Updates to the DNS protocol such as new RR types | +| [test] | Changes to the automatic tests, not affecting server functionality | +| [cleanup] | Minor corrections and refactoring | +| [doc] | Documentation | +| [contrib] | Changes to the contributed tools and libraries in the 'contrib' subdirectory | +| [placeholder] | Used in the master development branch to reserve change numbers for use in other branches, e.g. when fixing a bug that only exists in older releases | + +In general, [func] and [experimental] tags will only appear in new-feature +releases (i.e., those with version numbers ending in zero). Some new +functionality may be backported to older releases on a case-by-case basis. +All other change types may be applied to all currently-supported releases. + +### Acknowledgments + +* The original development of BIND 9 was underwritten by the + following organizations: + + Sun Microsystems, Inc. + Hewlett Packard + Compaq Computer Corporation + IBM + Process Software Corporation + Silicon Graphics, Inc. + Network Associates, Inc. + U.S. Defense Information Systems Agency + USENIX Association + Stichting NLnet - NLnet Foundation + Nominum, Inc. + +* This product includes software developed by the OpenSSL Project for use + in the OpenSSL Toolkit. + [http://www.OpenSSL.org/](http://www.OpenSSL.org/) +* This product includes cryptographic software written by Eric Young + (eay@cryptsoft.com) +* This product includes software written by Tim Hudson (tjh@cryptsoft.com) diff --git a/configure b/configure index ebdf11dc411..956376a85e7 100755 --- a/configure +++ b/configure @@ -695,6 +695,7 @@ CURL DOXYGEN XMLLINT XSLTPROC +PANDOC W3M DBLATEX PDFLATEX @@ -955,6 +956,7 @@ infodir docdir oldincludedir includedir +runstatedir localstatedir sharedstatedir sysconfdir @@ -1110,6 +1112,7 @@ datadir='${datarootdir}' sysconfdir='${prefix}/etc' sharedstatedir='${prefix}/com' localstatedir='${prefix}/var' +runstatedir='${localstatedir}/run' includedir='${prefix}/include' oldincludedir='/usr/include' docdir='${datarootdir}/doc/${PACKAGE_TARNAME}' @@ -1362,6 +1365,15 @@ do | -silent | --silent | --silen | --sile | --sil) silent=yes ;; + -runstatedir | --runstatedir | --runstatedi | --runstated \ + | --runstate | --runstat | --runsta | --runst | --runs \ + | --run | --ru | --r) + ac_prev=runstatedir ;; + -runstatedir=* | --runstatedir=* | --runstatedi=* | --runstated=* \ + | --runstate=* | --runstat=* | --runsta=* | --runst=* | --runs=* \ + | --run=* | --ru=* | --r=*) + runstatedir=$ac_optarg ;; + -sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb) ac_prev=sbindir ;; -sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \ @@ -1499,7 +1511,7 @@ fi for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \ datadir sysconfdir sharedstatedir localstatedir includedir \ oldincludedir docdir infodir htmldir dvidir pdfdir psdir \ - libdir localedir mandir + libdir localedir mandir runstatedir do eval ac_val=\$$ac_var # Remove trailing slashes. @@ -1652,6 +1664,7 @@ Fine tuning of the installation directories: --sysconfdir=DIR read-only single-machine data [PREFIX/etc] --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] --localstatedir=DIR modifiable single-machine data [PREFIX/var] + --runstatedir=DIR modifiable per-process data [LOCALSTATEDIR/run] --libdir=DIR object code libraries [EPREFIX/lib] --includedir=DIR C header files [PREFIX/include] --oldincludedir=DIR C header files for non-gcc [/usr/include] @@ -21246,6 +21259,53 @@ test -n "$W3M" || W3M="w3m" +# +# Look for pandoc +# +# Extract the first word of "pandoc", so it can be a program name with args. +set dummy pandoc; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_path_PANDOC+:} false; then : + $as_echo_n "(cached) " >&6 +else + case $PANDOC in + [\\/]* | ?:[\\/]*) + ac_cv_path_PANDOC="$PANDOC" # Let the user override the test with a path. + ;; + *) + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_path_PANDOC="$as_dir/$ac_word$ac_exec_ext" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + + test -z "$ac_cv_path_PANDOC" && ac_cv_path_PANDOC="pandoc" + ;; +esac +fi +PANDOC=$ac_cv_path_PANDOC +if test -n "$PANDOC"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $PANDOC" >&5 +$as_echo "$PANDOC" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + + + + # # Look for xsltproc (libxslt) # diff --git a/configure.in b/configure.in index 3d16a106ed8..941123a37ab 100644 --- a/configure.in +++ b/configure.in @@ -4430,6 +4430,13 @@ AC_SUBST(DBLATEX) AC_PATH_PROGS(W3M, w3m, w3m) AC_SUBST(W3M) +# +# Look for pandoc +# +AC_PATH_PROG(PANDOC, pandoc, pandoc) +AC_SUBST(PANDOC) + + # # Look for xsltproc (libxslt) # diff --git a/doc/markdown/howto.mkd b/doc/dev/contrib.md similarity index 84% rename from doc/markdown/howto.mkd rename to doc/dev/contrib.md index c2758b663c9..2928d7e1750 100644 --- a/doc/markdown/howto.mkd +++ b/doc/dev/contrib.md @@ -6,7 +6,7 @@ - file, You can obtain one at http://mozilla.org/MPL/2.0/. ---> ## BIND Source Access and Contributor Guidelines -*May 8, 2014* +*Apr 14, 2017* ### Contents @@ -81,8 +81,8 @@ Suggested changes or requests for new features can be emailed to `bind-suggest@isc.org`. Both bugs and suggestions are stored in the ticketing system used by the software engineering team at ISC. -All submissions to the ticketing system receive an automatic response. -Any followup email sent to the ticketing system should use the same subject +All submissions to the ticketing system receive an automatic response. Any +followup email sent to the ticketing system should use the same subject header, so that it will be routed to the same ticket. Due to a large ticket backlog and an even larger quantity of incoming spam, @@ -90,14 +90,15 @@ we are sometimes slow to respond, especially if a bug is cosmetic or if a feature request is vague or low in priority, but we will try at least to acknowledge legitimate bug reports within a week. -The bug database is not publicly readable. Information about your -system that you submit in bug reports will not be divulged outside ISC. +Currently, ISC's ticketing system is not publicly readable. However, ISC +may open it in the future. Please do not include information you consider +to be confidential. ### Contributing code BIND's [open source license](http://www.isc.org/downloads/software-support-policy/isc-license/) -does not require changes to be contributed back to ISC, but this page +not require changes to be contributed back to ISC, but this page includes some guidelines for those who would like to do so. We accept two different types of code contribution: Code intended for @@ -116,39 +117,40 @@ your patch introduces a new feature in BIND, please submit it to ISC does not require an explicit copyright assignment for patch contributions. However, by submitting a patch to ISC, you implicitly certify that you are the author of the code, that you intend to reliquish -exclusive copyright, and that you grant permission to publish your -work under the -[ISC license](http://www.isc.org/downloads/software-support-policy/isc-license/). +exclusive copyright, and that you grant permission to publish your work +under the +[Mozilla Public License 2.0](http://www.isc.org/downloads/software-support-policy/isc-license/) +for BIND 9.11 and higher, and the +[ISC License](http://www.isc.org/downloads/software-support-policy/isc-license/) +for BIND 9.10 and earlier. Patches should be submitted as diffs against a specific version of BIND -- preferably the current top of the `master` branch. Diffs may be generated using either `git format-patch` or `git diff`. -Those wanting to write code for BIND may be interested -in the [developer information](dev.html) page, which includes -information about BIND design and coding practices, including -discussion of internal APIs and overall system architecture. -(This is a work in progress, and still quite preliminary.) +Those wanting to write code for BIND may be interested in the [developer +information](dev.md) page, which includes information about BIND design and +coding practices, including discussion of internal APIs and overall system +architecture. (This is a work in progress, and still quite preliminary.) -Every patch submitted will be reviewed by ISC engineers following -our [code review process](dev.html#reviews) before it is merged. +Every patch submitted will be reviewed by ISC engineers following our [code +review process](dev.md#reviews) before it is merged. -It may take considerable time to review patch submissions, especially -if they don't meet ISC style and quality guidelines. If the patch -is a good idea, we can and will do additional work to bring them up -to par, but if we're busy with other work, it may take us a long -time to get to it. +It may take considerable time to review patch submissions, especially if +they don't meet ISC style and quality guidelines. If the patch is a good +idea, we can and will do additional work to bring them up to par, but if +we're busy with other work, it may take us a long time to get to it. To ensure your patch is acted on as promptly as possible, please: -* Try to adhere to the [BIND 9 coding style](style.html). +* Try to adhere to the [BIND 9 coding style](style.md). * Run `make` `check` to ensure your change hasn't caused any functional regressions. * Document your work, both in the patch itself and in the accompanying email. * In patches that make non-trivial functional changes, include system tests if possible; when introducing or substantially altering a - library API, include unit tests. See [Testing](dev.html#testing) + library API, include unit tests. See [Testing](dev.md#testing) for more information. ##### Changes to `configure` @@ -195,5 +197,5 @@ testers including `queryperf` and `perftcpdns`; and drivers and modules for DLZ. If you have code with a BSD-compatible license that you would like us to -includ in `contrib`, please send it to `bind-suggest@isc.org`, with +include in `contrib`, please send it to `bind-suggest@isc.org`, with "`[CONTRIB]`" in the subject header. diff --git a/doc/markdown/dev.mkd b/doc/dev/dev.md similarity index 99% rename from doc/markdown/dev.mkd rename to doc/dev/dev.md index fd289169d62..5b913c743ee 100644 --- a/doc/markdown/dev.mkd +++ b/doc/dev/dev.md @@ -27,7 +27,7 @@ * [Adding a new RR type](#rrtype) * [Task and timer model](#tasks) -### The code review process +### The code review process Every line of code comitted to BIND has been reviewed by ISC engineers first. @@ -334,8 +334,8 @@ creating a memory context. Similar functions `dns_test_begin()` and #### Namespace -See the [namespace](style.html#public_namespace) discussion in the -[BIND coding style](style.html) document. +See the [namespace](style.md#public_namespace) discussion in the +[BIND coding style](style.md) document. #### Design by contract @@ -520,17 +520,17 @@ as part of the 'used' subregion: Several functions are provided for both reading and writing to the buffer: -* `isc_buffer_getuint8`: Read and return an 8-bit unsigned integer -* `isc_buffer_putuint8`: Write an 8-bit unsigned integer to a buffer +* `isc_buffer_getuint8()`: Read and return an 8-bit unsigned integer +* `isc_buffer_putuint8()`: Write an 8-bit unsigned integer to a buffer -* `isc_buffer_getuint16`: Read a 16-bit unsigned integer in +* `isc_buffer_getuint16()`: Read a 16-bit unsigned integer in network byte order, convert to host byte order, and return it -* `isc_buffer_putuint16`: Convert an unsigned 16-bit integer from +* `isc_buffer_putuint16()`: Convert an unsigned 16-bit integer from host to network byte order and write it to a buffer. -* `isc_buffer_getuint32`: Read a 32-bit unsigned integer in +* `isc_buffer_getuint32()`: Read a 32-bit unsigned integer in network byte order, convert to host byte order, and return it -* `isc_buffer_putuint32`: Convert an unsigned 32-bit integer from +* `isc_buffer_putuint32()`: Convert an unsigned 32-bit integer from host to network byte order and write it to a buffer. * `isc_buffer_putstr()`: Copy a null-terminated string into a buffer diff --git a/doc/markdown/style.mkd b/doc/dev/style.md similarity index 98% rename from doc/markdown/style.mkd rename to doc/dev/style.md index ef0a223005a..42475f7deb9 100644 --- a/doc/markdown/style.mkd +++ b/doc/dev/style.md @@ -370,7 +370,7 @@ be ambiguous. #### Clear Success or Failure A function should report success or failure, and do so accurately. It -should never fail silently. Use of [design by contract](dev.html#dbc) +should never fail silently. Use of [design by contract](dev.md#dbc) can help here. When a function is designed to return results to the caller by assigning @@ -380,8 +380,8 @@ fails. A `REQUIRE()` statement should be used to ensure that the pointer is in a sane state when the function is called. The `isc_result_t` is provided for use by result codes. See the -[results](dev.html#results) section of the [developer -information](dev.html) page for more details. +[results](dev.md#results) section of the [developer +information](dev.md) page for more details. #### Testing Bits @@ -648,7 +648,7 @@ from a source with a BSD-compatible license). BIND provides portable internal versions of many common library calls. Some are designed to ensure that library calls have standardized -[ISC result codes](dev.html#results) instead of using potentially +[ISC result codes](dev.md#results) instead of using potentially nonwportable `errno` values; these include the file operations in `isc_file` and `isc_stdio`. Others, such as `isc_tm_strptime()`, are needed to ensure consistent cross-platform behavior. @@ -668,7 +668,7 @@ in separate files, such as `lib/isc/unix/file.c` and `lib/isc/win32/file.c`. #### Log messages Error and warning messages should be logged through the [logging -system](dev.html#logging). Debugging `printf`s may be used during +system](dev.md#logging). Debugging `printf`s may be used during development, but must be removed when the debugging is finished. Log messages do not start with a capital letter, nor do they end in a diff --git a/doc/markdown/.gitignore b/doc/markdown/.gitignore deleted file mode 100644 index 2d19fc766d9..00000000000 --- a/doc/markdown/.gitignore +++ /dev/null @@ -1 +0,0 @@ -*.html diff --git a/doc/markdown/Makefile b/doc/markdown/Makefile deleted file mode 100644 index b3285aa9ad3..00000000000 --- a/doc/markdown/Makefile +++ /dev/null @@ -1,13 +0,0 @@ -# Copyright (C) 2014, 2016 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/. - -all: style.html howto.html dev.html - -%.html: %.mkd - markdown $< > $@ - -clean: - rm style.html howto.html dev.html diff --git a/make/rules.in b/make/rules.in index 6a127bd54fb..6e83b693bc5 100644 --- a/make/rules.in +++ b/make/rules.in @@ -307,6 +307,7 @@ LATEX = @LATEX@ PDFLATEX = @PDFLATEX@ DBLATEX = @DBLATEX@ W3M = @W3M@ +PANDOC = @PANDOC@ ### ### Script language program used to create internal symbol tables