I am using an amazon large EC2 instance (4ECUs, 2 cores) for my unbound
configured as below. I am seeing a 150ms+ average response time as reported
by namebench Alexa 2K result. In order to reduce my lookup times, I am
running an hourly scan of these 35K sites (from namebench dat files) in
order to
On 07/06/2012 04:45 PM, W.C.A. Wijngaards wrote:
So unbound asks dnsmasq for the address of "myhost.lan" as it
is instructed by forward-zone, gets correct result (!), but
then marks it bogus because it cannot establish trust chain.
>>>
>>> You'll need
>>>
>>> private-domain: "lan."
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Eugene,
On 07/06/2012 02:25 PM, Eugene Crosser wrote:
> On 07/06/2012 03:33 PM, Jan-Piet Mens wrote:
>>> So unbound asks dnsmasq for the address of "myhost.lan" as it
>>> is instructed by forward-zone, gets correct result (!), but
>>> then marks it
On 07/06/2012 03:33 PM, Jan-Piet Mens wrote:
>> So unbound asks dnsmasq for the address
>> of "myhost.lan" as it is instructed by forward-zone, gets correct result (!),
>> but then marks it bogus because it cannot establish trust chain.
>
> You'll need
>
> private-domain: "lan."
>
> So unbound asks dnsmasq for the address
> of "myhost.lan" as it is instructed by forward-zone, gets correct result (!),
> but then marks it bogus because it cannot establish trust chain.
You'll need
private-domain: "lan."
domain-insecure: "lan."
Regards,
-JP
__
Hello all,
sorry if this was discussed already, I could not find the answer.
I am trying to configure unbound (1.4.5, running on openwrt) to resolve local
zones ("lan." and "168.192.in-addr.arpa.") from another DNS server that has them
(in my case, dnsmasq: I want DHCP names resolved in the .lan
