Bug 2492

Summary: Documentation libunbound
Product: unbound Reporter: Дилян Палаузов <dpa-nlnetlabs>
Component: serverAssignee: unbound team <unbound-team>
Status: RESOLVED FIXED    
Severity: enhancement CC: cathya, wouter
Priority: P5    
Version: 1.6.7   
Hardware: All   
OS: All   

Description Дилян Палаузов 2017-11-06 19:47:24 CET
The manual of libunbound does not make it clear, how libunbound relates to unbound at run time.  At first I though that libunbound is a means to connect to an unbound instance running on the same host.

Something like:

CURRENT:
DESCRIPTION
       Unbound is an implementation of a DNS resolver, that does  caching  and
       DNSSEC  validation.  This  is  the library API, for using the -lunbound
       library.  The server daemon is described in  unbound(8).   The  library
       can  be used to convert hostnames to ip addresses, and back, and obtain
       other information from the DNS. The library performs public-key valida-
       tion of results with DNSSEC.

PROPOSED:
DESCRIPTION
       Unbound is an implementation of a DNS resolver, that does  caching  and
       DNSSEC  validation.  This  is  the library API, for using the -lunbound
       library.  The server daemon is described in  unbound(8).   The  library
       works independent from a running unbound server,
       can  be used to convert hostnames to ip addresses, and back, and obtain
       other information from the DNS. The library performs public-key valida-
       tion of results with DNSSEC.
Comment 1 Wouter Wijngaards 2017-11-07 09:06:03 CET
Hi,

Thanks for the report!  Fixed it.

Best regards, Wouter