B1 worked!

Thank you very much.

On Tue, Apr 28, 2020 at 2:53 PM Jan Komissar (jkomissa) <[email protected]>
wrote:

> Hi,
>
>
>
> If you are using a stub-zone for any of the as112 zones (incl. rfc-1918
> zones) You must do one of three things.
>
>    1. You can set “unblock-lan-zones: yes”, but that will make *all* lan
>    zone queries be resolved upstream (this may be frowned upon).
>    2. If you don’t want that, your choices are:
>
>
>    1. If your zone is a subzone of one of the as112 zones, you must add
>       “local-zone: <your .arpa zone> transparent”.
>       2. If your zone equals or encloses one those zones, you must add:
>        “local-zone: <your .arpa zone> nodefault”.
>
>
>
> Good Luck,
>
>
>
> Jan.
>
>
>
> *From: *Unbound-users <[email protected]> on
> behalf of bofh via Unbound-users <[email protected]>
> *Reply-To: *bofh <[email protected]>
> *Date: *Tuesday, April 28, 2020 at 1:37 PM
> *To: *Mike Kazantsev <[email protected]>
> *Cc: *"[email protected]" <[email protected]
> >
> *Subject: *Re: unbound and nsd on the same machine - what am I missing?
>
>
>
> I took out local-zone: 10.10.10.in-addr.arpa and no changes.
>
>
>
> I added private-address: 10.10.10.0/24 and no changes.
>
> I changed private-address to 10.0.0.0/8 and I can't look up hosts on my
> internal network any more (both reverse and forward lookups failed).
>
>
>
> This is driving me nuts... :(
>
> Does anyone have a simple working config that they are willing to share,
> with unbound and bind or unbound and nsd on the same server?  In a private
> address space.
>
>
>
> Thank you so much.
>

Reply via email to