Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bind9 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Which versions relevant to Ubuntu are affected by this? Do you have a
list of version numbers for each supported Ubuntu release, please? And
in which upstream versions is this issue fixed?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Marc, can you please inform us why you don't consider this to be a
security bug when the only work-around is to disable a important
security feature of the resolver?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1203976
Title:
DNS wildcards fail to resolve with DNSsec enabled
To manage
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1203976
Title:
DNS wildcards fail to resolve with DNSsec enabled
To manage
** Bug watch added: Debian Bug tracker #690569
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690569
** Also affects: bind9 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690569
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: bind9 (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1203976
Title:
DNS wildcards fail to resolve with DNSsec enabled
To manage
