Maintained by: NLnet Labs

Configuration issue

W.C.A. Wijngaards
Mon Nov 27 17:08:52 CET 2017


Hi,

The order does not matter for local-zone, local-data, forward and stub
clauses.  Unbound picks the closest one.  First the local-zone and
local-data statements are processed.  Then the cache of forward and stub
data.  Then the lookup vi forward and stub data.

You could create a local-zone: "." refuse and local-zone: "example.com"
transparent for all of the names you want resolved.  If you want those
names forwarded somewhere, you can then also include forward clauses for
those names.  The other names are rejected.

Best regards, Wouter

On 27/11/17 15:09, Sonic via Unbound-users wrote:
> Maybe post the unbound.conf file (no comment lines please).
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://unbound.nlnetlabs.nl/pipermail/unbound-users/attachments/20171127/6f083ca3/attachment.sig>