On Wed, Oct 17, 2012 at 10:22 PM, Matthew Grant wrote:
> On Wed, Oct 17, 2012 at 1:57 PM, Michael Gilbert
>> No. We're in the freeze now. Fixes need to be backported.
>
>
> If backporting a fix is not possible with the certainty of no introduced
> bugs, we have no choice.
>
> Debian Bind9 cannot
On Wed, Oct 17, 2012 at 1:57 PM, Michael Gilbert wrote:
> On Tue, Oct 16, 2012 at 6:49 PM, Matthew Grant wrote:
> > Can Bug #690569 (DNS wildcards fail to resolve with DNSsec enabled -
> breaks
> > RFC 4035)be reclassified as grave, or at least Important severity?
>
You i
before I leap.
> >
> > Can Bug #690569 (DNS wildcards fail to resolve with DNSsec enabled -
> breaks
> > RFC 4035)be reclassified as grave, or at least Important severity?
> >
> > We need to get something done about this one. Having to turn off DNSSEC
> &g
On Tue, Oct 16, 2012 at 6:49 PM, Matthew Grant wrote:
> Hi Michael!
>
> Sorry to bother you again, but want some advice before I leap.
>
> Can Bug #690569 (DNS wildcards fail to resolve with DNSsec enabled - breaks
> RFC 4035)be reclassified as grave, or at least Important seve
Package: bind9
Version: 1:9.8.1.dfsg.P1-4.2
Followup-For: Bug #690569
Problem exists in current Debian Version of bind9. This is broken behaviour
with regards RFC4035 Section 3.1.3 and maybe some parts of RFC4952.
This means the version of bind in unstable and testing is non functional for
the p
Package: bind9
Version: 1:9.7.3.dfsg-1~squeeze7
When using bind9 as a resolver it will fail to resolve *.example.org
when DNSsec is enabled in the resolver. So when resolving
'www.example.org' relies on resolving '*.example.org', the RR won't
be found.
Below an example taken from /var/log/sysl
6 matches
Mail list logo
