Maintained by: NLnet Labs

Unbound 1.6.0rc1 prerelease

Spike
Thu Dec 15 20:18:32 CET 2016


Brilliant, thank you Wouter for your insight, this is enough to get us off
of the python module at least on half of our instances. I've clearly still
much to learn about unbound and how to leverage its power.

For some other cases however in the python script I'm using simple regexps
and I'm wondering if there is any way to use wildcards in the local-zone
string. So, following from your example, could I do something like:

local-zone: "domain.tld" static
local-zone: "www*.domain.tld" transparent

so that nothing resolves except www1.domain.tld, www2.domain.tld etc.

thanks,

Spike

On Thu, Dec 15, 2016 at 12:16 AM W.C.A. Wijngaards via Unbound-users <
unbound-users at unbound.net> wrote:

> Hi Spike,
>
> Just wanted to add a small comment:
>
> On 15/12/16 05:04, Spike via Unbound-users wrote:
> > unfortunately in some cases I need inverted regexps/whitelists, for
> > example allow sub.domain.tld but otherwise block *.domain.tld. As far as
> > I could see you can't do that with local-data.
>
> Yes this is possible, with
> local-zone: "domain.tld" static
> local-zone: "sub.domain.tld" transparent
>
> The most specific match is used.  The sub.domain.tld resolves normally.
> But other queries, like foo.domain.tld, get NXDOMAIN.
>
> Best regards, Wouter
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://unbound.nlnetlabs.nl/pipermail/unbound-users/attachments/20161215/ab1e7593/attachment.html>