From 2bf8d9b4b212b6c414d9264754423e897dccd98d Mon Sep 17 00:00:00 2001 From: Wouter Wijngaards Date: Mon, 2 Mar 2009 09:35:56 +0000 Subject: [PATCH] FAQ entry git-svn-id: file:///svn/unbound/trunk@1504 be551aaa-1e26-0410-a405-d3ace91eadb9 --- doc/Changelog | 1 + doc/README | 10 ++++------ 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/doc/Changelog b/doc/Changelog index c45634f3e..152b72a2e 100644 --- a/doc/Changelog +++ b/doc/Changelog @@ -3,6 +3,7 @@ This should fix extraneous symbols exported from libunbound. Thanks to Ondrej Sury and Robert Edmonds for finding it. - iana portlist updated. + - document FAQ entry on stub/forward zones and default blocking. 27 February 2009: Wouter - Fixup lexer, to not give warnings about fwrite. Appeared in diff --git a/doc/README b/doc/README index a0693b6b4..c62447b45 100644 --- a/doc/README +++ b/doc/README @@ -64,18 +64,16 @@ This software is under BSD license, see LICENSE for details. Known issues ------------ +o If there are no replies for a forward or stub zone, for a reverse zone, + you may need to add a local-zone: name transparent or nodefault to the + server: section of the config file to unblock the reverse zone. + Only happens for (sub)zones that are blocked by default; e.g. 10.in-addr.arpa o If libevent is older (before 1.3c), unbound will exit instead of reload on sighup. On a restart 'did not exit gracefully last time' warning is printed. Perform ./configure --with-libevent=no or update libevent, rerun configure and recompile unbound to make sighup work correctly. It is strongly suggested to use the latest version of libevent (1.4 or more) on Solaris, because of fixes in the solaris event port code in libevent. -o If you receive no answers deploying unbound on a private network. - Check that the zone you configure as a stub zone is correct, listing working - ip-addresses. Check that the NS data in the zone, those hostnames, are - in fact those same, working, ip-addresses. Unbound will fetch the NS data - from the zone and use that information in preference to the config - information. o If you are not receiving the correct source IP address on replies (e.g. you are running a multihomed, anycast server), the interface-automatic option can be enabled to set socket options to achieve the correct