Re: Timeout semantics of Unbound differ radically from Bind 9

2016-04-09 Thread Aaron Hopkins via Unbound-users
yOn Sun, 10 Apr 2016, Dhalgren Tor wrote: However please note that Tor project has modified the eventdns code so it may not match exactly the behavior of the generic version. The generic version seems to have 3 retries at 3 seconds each, before considering the nameserver dead. So Tor's

Re: Timeout semantics of Unbound differ radically from Bind 9

2016-04-09 Thread Aaron Hopkins via Unbound-users
On Sun, 10 Apr 2016, Dhalgren Tor via Unbound-users wrote: While I appreciate the elegance and persistence of Unbound's timeout scheme, it breaks Tor and probably breaks other high-volume DNS requesters that expect the simple ten-second timeout behavior of 'named'. Under the covers, Tor uses

Re: [Unbound-users] stub-prime unexpected behavior

2013-03-21 Thread Aaron Hopkins
On Thu, 21 Mar 2013, W.C.A. Wijngaards wrote: Not for stub-prime, the newly introduced behaviour for 'normal referrals' is to check at the parent as a last resort to get information. When you add a stub-zone with stub-prime yes, then this also activates. Based on the current documentation, I

[Unbound-users] stub-prime unexpected behavior

2013-03-20 Thread Aaron Hopkins
I internally override an externally visible domain to be able to give different answers with a config like: stub-zone: name: example.com stub-addr: 10.1.2.3 stub-addr: 10.1.2.4 stub-prime: yes I recently upgraded from Unbound 1.4.4 to 1.4.19 and after running for a few hours was

Re: [Unbound-users] Unbound x Bind - Round robin DNS

2012-12-13 Thread Aaron Hopkins
On Fri, 14 Dec 2012, Leandro Anjos Moura wrote: When my application directly query my server Bind all ips are utilized in connection, but when my application query my server Unbound ips network 10.XXX are never recovered. See the rrset-roundrobin option as of Unbound 1.4.17:

Re: [Unbound-users] NOTIFY implementation to unbound

2009-10-19 Thread Aaron Hopkins
On Mon, 19 Oct 2009, Greg A. Woods wrote: The key concept here is that notify says something has changed with the given zone. It means whoever sent you the NOTIFY has updated data for this zone. However, unbound won't just query whoever sent it the NOTIFY; it will query any authoritative

Re: [Unbound-users] unbound occasionally does not answer

2009-09-18 Thread Aaron Hopkins
On Fri, 18 Sep 2009, W.C.A. Wijngaards wrote: By default, it polls every socket for 100 datagrams, but in your case that can be 8000 'not port 53' sockets. It might be an interesting experiment to track the average and max amount of time spent handling 53 vs not-53 sockets in one pass on a

Re: [Unbound-users] Unbound and Round Robin DNS

2009-08-21 Thread Aaron Hopkins
On Fri, 21 Aug 2009, Paul Wouters wrote: Perhaps Wouter can explain that part, as I am sure some conscious design decision has gone into that. I'm guessing this is the same anti-feature-creep sentiment as why round-robinning RRs was left out of NSD. This is unfortunate, because very few