Maintained by: NLnet Labs

[Unbound-users] local-zone transparent behavior

Bryan Clay
Fri Mar 19 15:43:30 CET 2010

I just tried this to no effect.  I'm thinking the behavior I detailed is by
design due to a change log entry on Unbound 1.2.0.

"fixup reported problem with transparent local-zone data where queries with
different type could get nxdomain. Now queries with a different name get
resolved normally, with different type get a correct NOERROR/NODATA answer."

The MX is a different type than the A, so it gets NOERROR/NODATA...or am I
misunderstanding that entry?


On Fri, Mar 19, 2010 at 10:37 AM, Paul Wouters <paul at> wrote:

> On Fri, 19 Mar 2010, Bryan Clay wrote:
>  Tried to send an email to, the email server can't find the
>> MX record.  The MX record exists upstream,
>> it points to  When I hit Bind directly, it returns the
>> private IP fine.  Unbound returns that the
>> record doesn't exist due to overriding A.
> Ohh, this might be because the RFC1918 address are dropped for security
> reasons.
> To allow these, check the private-address: and private-domain: options. Try
> adding:
> private-domain:
> private-domain:
> private-domain:
> Paul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>