Re: Making unbound-anchor very verbose

Thanks. That has kicked me off in some direction. On 9/21/15, 11:02, "Unbound-users on behalf of unbound-users@unbound.net" wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA256 > >Hi Ed, > >It does not say a lot

Re: inconsistent forward-zone behavior between config files, unbound-control

A. Schulze via Unbound-users wrote: > Am 22.09.2015 um 19:02 schrieb Mike Brown via Unbound-users: > >* by default, queries go to my ISP's resolvers (Comcast: 75.75.75.75 & > >75.75.76.76) > why would you do that? Comcast's 75.75.75.75 and 75.75.76.76 nameservers are anycasted. 75.75.75.75 in

Re: rfc6761 compliance

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Robert, Andreas, On 11/09/15 17:54, Robert Edmonds via Unbound-users wrote: > A. Schulze via Unbound-users wrote: >> Hello, >> >> the RFC 6761 give some advise how caching DNS servers SHOULD >> handle queries for reserved domains. Mostly it

Re: rfc6761 compliance

On Tue, 22 Sep 2015, Robert Edmonds via Unbound-users wrote: W.C.A. Wijngaards via Unbound-users wrote: It is not a particularly heavy root server load to mitigate, less code is better and easier, the unblock-lan-zones statement is a frequently asked question from our users. That said, we

inconsistent forward-zone behavior between config files, unbound-control

It is quite possible I am just clueless and doing things all wrong, so please forgive me if this is a waste of your time. I've Googled and experimented for hours, and am no closer to understanding what's going wrong here. I'm just trying to get Unbound configured on FreeBSD 10.2-STABLE such

Re: rfc6761 compliance

W.C.A. Wijngaards via Unbound-users wrote: > It is not a particularly heavy root server load to mitigate, less code > is better and easier, the unblock-lan-zones statement is a frequently > asked question from our users. That said, we could add new code for > this (and .onion?). Hi, Wouter: I

Re: [PATCH] unable to reload globs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Dag-Erling, On 17/09/15 18:39, Dag-Erling Smørgrav via Unbound-users wrote: > When the configuration lexer processes an include directive and > unbound is chrooted, it will attempt to strip the chroot directory > from the front of the filename.

Re: unbound-control flush_zone behaviour w.r.t the DS record

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Paul, On 16/09/15 04:35, Paul Wouters via Unbound-users wrote: > > Hi, > > Today I ran into an unexpected flush issue. A domain with DS record > no longer signed its zone and became BOGUS. Once the registrar > removed the DS record, I ran an

Re: A record from cache for request that resolved to (some) CNAMEs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Mehmed, On 21/09/15 13:17, Mehmed Kahric via Unbound-users wrote: > Hi, > > I have a similar issue as reported in Bug 669. > > For some (one for now) CNAMEs we have a empty A record answer from > Unbound. Proper answer came from remote DNS as

Re: Minor error in unbound.conf.5.in

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Ross, On 01/09/15 06:29, Ross L Richardson via Unbound-users wrote: > Word repetition error: If the the minimum kicks in should be If the > minimum kicks in Thank you. Fixed. Best regards, Wouter -BEGIN PGP SIGNATURE- Version: GnuPG v2

Re: unbound.conf(5) access-control suggestions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Patrik, On 05/08/15 20:14, Patrik Lundin via Unbound-users wrote: > Hello, > > Following the recent man page modifications I was reminded of > another part of the manual that I am curios if it could be modifed > a bit. This is the part about

Re: unbound-control flush_zone behaviour w.r.t the DS record

On Tue, 22 Sep 2015, W.C.A. Wijngaards via Unbound-users wrote: Today I ran into an unexpected flush issue. A domain with DS record no longer signed its zone and became BOGUS. Once the registrar removed the DS record, I ran an unbound-control flush_zone on the zone, but I still received a