-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Unbound 1.5.7 is available:
http://www.unbound.net/downloads/unbound-1.5.7.tar.gz
sha1 6306fec537f507a41b9c3a7e16e4aa1c10532510
sha256 4b2088e5aa81a2d48f6337c30c1cf7e99b2e2dc4f92e463b3bee626eee731ca8
pgpsig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Pujo,
On 06/12/15 04:35, pujo mulyono via Unbound-users wrote:
> Hi,
>
> Ask, how to set TTL for redirect local-data lower than 3600
> (default)? i read the Documentation but i could not find it if i
> want to set ttl = 900, something similar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Unbound 1.5.7rc1 prerelease is available:
http://www.unbound.net/downloads/unbound-1.5.7rc1.tar.gz
sha1 938ab7e2739aa65c261ce2ff989e27e7fcccd5c4
sha256 c614c4234776d919dd296ee750d3cf6161a2749d83010b4b4385cf21cf165861
pgpsig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 23/11/15 06:31, Steinar Haug via Unbound-users wrote:
>> I have a few recursive name servers running Debian. I have
>> recently upgraded the packages I was running from Jessie
>> (1.4.22-3) to testing (1.5.6-1). Since the upgrade I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 11/20/2015 10:11 AM, W.C.A. Wijngaards via Unbound-users wrote:
> Hi Ian,
>
> On 11/19/2015 09:47 PM, Ian Cohee via Unbound-users wrote:
>> Hello all,
>
>> One of our engineers discovered some interesting behavior wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ian,
On 11/19/2015 09:47 PM, Ian Cohee via Unbound-users wrote:
> Hello all,
>
> One of our engineers discovered some interesting behavior while
> testing bad EDNS RRs in Unbound. He discovered that Unbound
> properly checks and identifies a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dave,
On 11/03/2015 10:04 PM, Dave Warren via Unbound-users wrote:
> On 2015-11-03 05:57, W.C.A. Wijngaards via Unbound-users wrote:
>> No, there is no option to disable the CNAME checks. The trust in
>> the other nameserve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Unbound 1.5.6 is available:
http://www.unbound.net/downloads/unbound-1.5.6.tar.gz
sha1 b1e521669d6e5a3c1baf8b71dad070e38887162b
sha256 ad3823f5895f59da9e408ea273fcf81d8a76914c18864fba256d7f140b83e404
pgp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sami,
On 10/14/2015 09:32 PM, Sami Kerola wrote:
> On 14 October 2015 at 08:12, W.C.A. Wijngaards
> wrote:
>
> Hi Wouter, et.al.,
>
>> The patch looks very nice. I would like to include contrib items
>> that make systemd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Hendrik,
On 10/16/2015 12:47 PM, Hendrik Jaeger via Unbound-users wrote:
> Hi,
>
> I’m running unbound 1.4.22 from debian unstable on my laptop. Since
> yesterday unbound started behaving strangely, flooding the syslog
> with failure messages.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Unbound 1.5.6rc1 maintainers prerelease is available:
http://www.unbound.net/downloads/unbound-1.5.6rc1.tar.gz
sha1 b657098c3878d85e9f3f23d6c39b81aaf7ddbc1e
sha256 2aa591c91ac8f9ddcd4c6c80d0862d37ee1b08c480af5874256d4e5394c30301
pgp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sami,
The patch looks very nice. I would like to include contrib items that
make systemd integration easier. The code patches are well written.
I would like to incorporate them (with some changes, like not
installing the systemd integration
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dag-Erling,
On 10/14/2015 01:44 PM, Dag-Erling Smørgrav via Unbound-users wrote:
> Traditionally, Unix daemons will reload their configuration upon
> receiving SIGHUP and terminate gracefully upon receiving SIGTERM.
> Unbound follows this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Patrick,
You are not using full recursion but forwarding to 'public services'
of apparently debatable quality. Try turning off the forwarding
clause in unbound.conf and go to the authoritative servers to get the
data yourself.
If you are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Andreas,
On 07/10/15 15:06, A. Schulze via Unbound-users wrote:
>
> Hello,
>
> we have the following configuration to point unbound-1.5.4 to our
> private nameservers:
>
> server: local-zone: "10.in-addr.arpa." transparent domain-insecure:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Unbound 1.5.5 is available:
http://www.unbound.net/downloads/unbound-1.5.5.tar.gz
sha1 ff93df847187120c9ee98e7eebe4bb1bc859a8f2
sha256 f3bd7d3bc9519e8717abdc35c26cb2d84c3c3a3e2cd657604307e6860b37da5e
pgp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Havard,
On 05/10/15 14:43, Havard Eidnes via Unbound-users wrote:
> Hi,
>
> it looks like I'll have to answer my own question, which is a
> little disappointing:
>
>> I'm running unbound 1.5.4 on NetBSD/amd64 7.0, and I notice that
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Yuri,
On 10/02/2015 03:50 PM, Yuri Voinov via Unbound-users wrote:
>
> Hi there,
>
> does anybody know, is Unbound has local zone limit?
No, they are kept in a lookup structure that is similar in design to
the data structure in NSD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Unbound 1.5.5rc1 maintainers prelease candidate 1 is available:
http://www.unbound.net/downloads/unbound-1.5.5rc1.tar.gz
sha1 5b00efea35abb168d7788d6970edf221ddcc975d
sha256 d03f293305ca5c5e354db6fb1389870322b1fa2ec02e3c146c6a14c2ba53c525
pgp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Paul,
On 22/09/15 17:28, Paul Wouters wrote:
> I'm not sure. It did not become non-bogus for sure. I didn't drop
> the cache and the domain is fixed now. So you'll have to create a
> test case I guess? :)
Found a race condition in that code,
-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
-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.
-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
-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
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Ed,
It does not say a lot because all it does is do an UDP query, see that
it works, and exit. If you add, say, -F (force TLS update), then
it'll print out a lot of info (with -). Like, https headers, ssl
certificates, xml contents ...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Patrik,
On 22/08/15 07:27, Patrik Lundin wrote:
On Fri, Aug 21, 2015 at 11:13:34PM +0200, Wouter Wijngaards via
Unbound-users wrote:
This is because the RRset cache is shared between answers. The
SOA record is in that cache. When you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Poprocks,
On 24/08/15 01:52, Poprocks via Unbound-users wrote:
Hello,
I have encountered an issue in which unbound appears to hang when
issuing commands via unbound-control. I am running unbound 1.5.4
built on an Ubuntu 12.04 system. I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Over,
On 18/08/15 13:20, Over Dexia via Unbound-users wrote:
Hello,
If this is a double post, I'm sorry. I just have no way of checking
if this request arrived at the list (I didn't get a copy, that much
I know). Maybe if someone could at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Christian,
On 10/08/15 17:49, Christian Neukirchen via Unbound-users wrote:
Hi,
I noticed the LibreSSL configure test in unbound 1.5.4 does not
detect LibreSSL 2.2.2:
if grep OPENSSL_VERSION_TEXT $ssldir/include/openssl/opensslv.h |
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Patrik,
On 03/08/15 18:50, Patrik Lundin wrote:
On Mon, Aug 03, 2015 at 12:42:00PM +0200, W.C.A. Wijngaards via
Unbound-users wrote:
I've fixed up the manual page and the example config file, and
they now discuss configuring domain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Darren,
On 03/08/15 19:50, Darren Spruell via Unbound-users wrote:
Unbound's documentation mentions that query logging can have very
adverse performance on server operation. I was curious if the
project feels this has been optimized to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Patrik,
On 01/08/15 10:33, Patrik Lundin via Unbound-users wrote:
On Fri, Jul 31, 2015 at 10:36:34PM -0400, Sonic via Unbound-users
wrote:
I doubt that local-zone: 1.168.192.in-addr.arpa nodefault is
necessary since you're defining it as a
201 - 234 of 234 matches
Mail list logo