mirror of
https://github.com/NLnetLabs/unbound.git
synced 2025-12-20 23:00:56 -05:00
FAQ entry
git-svn-id: file:///svn/unbound/trunk@1504 be551aaa-1e26-0410-a405-d3ace91eadb9
This commit is contained in:
parent
a9754e0727
commit
2bf8d9b4b2
2 changed files with 5 additions and 6 deletions
|
|
@ -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
|
||||
|
|
|
|||
10
doc/README
10
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
|
||||
|
|
|
|||
Loading…
Reference in a new issue