Jenkins build became unstable: FreeBSD_stable_10 #140

2016-03-15 Thread jenkins-admin
See ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problems with unbound

2016-03-15 Thread Andrea Brancatelli
Hello everybody, we're suddenly having problems with unbound on almost all of our servers and I cannot really understand why. To make a long story short, we use this forward.conf: root@dbengine-ent-rm-01:/var/unbound # cat /etc/unbound/forward.conf # This file was generated by

Re: Problems with unbound

2016-03-15 Thread Matthew Seaman
On 03/15/16 11:28, Andrea Brancatelli wrote: > Hello everybody, > > we're suddenly having problems with unbound on almost all of our servers > and I cannot really understand why. > > To make a long story short, we use this forward.conf: > > root@dbengine-ent-rm-01:/var/unbound # cat

Jenkins build is back to stable : FreeBSD_stable_10 #139

2016-03-15 Thread jenkins-admin
See ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with unbound

2016-03-15 Thread Trond Endrestøl
On Tue, 15 Mar 2016 12:28+0100, Andrea Brancatelli wrote: > Hello everybody, > > we're suddenly having problems with unbound on almost all of our servers > and I cannot really understand why. > > To make a long story short, we use this forward.conf: > > root@dbengine-ent-rm-01:/var/unbound

Re: Problems with unbound

2016-03-15 Thread Andrea Brancatelli
Hi, the machine is connected "directly enough" (it's in a datacenter) to safely excude point 1. How can I check it with tcpdump or whatever? For point 2 I have the same exact problem adding OpenDNS in forward.conf, so I'd exclude it too. I have an interest and funny input tho: the problem

Re: Problems with unbound

2016-03-15 Thread Eugene Grosbein
15.03.2016 21:55, Andrea Brancatelli пишет: Hi, the machine is connected "directly enough" (it's in a datacenter) to safely excude point 1. Contrary, datacenters are known to have dumb filters dropping fragmented UDP packets that are essential for DNSSEC, so the "point 1" is most probable

Jenkins build is back to stable : FreeBSD_stable_10 #141

2016-03-15 Thread jenkins-admin
See ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"