[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2015-06-17 Thread Rolf Leggewie
lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as Won't Fix. ** Changed in: bind9 (Ubuntu Lucid) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2013-01-06 Thread LoOoD
I'm still affected by this. I'm using version 9.7.0.dfsg.P1-1ubuntu0.8 of the bind9 package. From the hosts listed above I'm still seeing it for these hosts: zidvox.com edadfs.partners.extranet.microsoft.com -- You received this bug notification because you are a member of Ubuntu Server Team,

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2012-02-02 Thread Dave Walker
** Changed in: bind9 (Ubuntu) Importance: Low = High ** Also affects: bind9 (Ubuntu Lucid) Importance: Undecided Status: New ** Changed in: bind9 (Ubuntu) Status: Confirmed = Fix Released ** Changed in: bind9 (Ubuntu Lucid) Status: New = Triaged ** Changed in: bind9

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2012-02-02 Thread Andres Rodriguez
** Changed in: bind9 (Ubuntu Lucid) Assignee: (unassigned) = Andres Rodriguez (andreserl) -- 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/807324 Title: BIND 9.7.0 (ie., lucid) is

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2011-12-09 Thread Edwin Chiu
Natty backport to Lucid available in my PPA repo: https://launchpad.net/~edwin-chiu/+archive/bind9 -- 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/807324 Title: BIND 9.7.0 (ie.,

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2011-12-08 Thread Edwin Chiu
Bunch of domains impacted, I'm shocked a patch hasn't being issued for Lucid yet... Some other domains impacted: webserver.mta.info www.energy.alberta.ca www.baixing.com www.engineering.utoronto.ca e.newegg.ca dns1.name-services.com -- You received this bug notification because you are a member

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2011-09-28 Thread Matt Day
I think we're hitting this problem, and I'm surprised to see the Importance of this bug set to Low. BIND9 version 1:9.7.0.dfsg.P1-1ubuntu0.3 on Ubuntu's Lucid LTS can't resolve certain DNS names: * www.newegg.ca * www.neweggbusiness.com * edadfs.partners.extranet.microsoft.com (sometimes) These

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2011-09-28 Thread Launchpad Bug Tracker
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. https://bugs.launchpad.net/bugs/807324

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2011-07-15 Thread Dave Walker
Thanks for reporting this bug, please can you comment a little on the impact that this bug has on a deployment? Thanks. ** Changed in: bind9 (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to

[Bug 807324] Re: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the aa flag

2011-07-15 Thread mibus
It means that a small number of domains that used to resolve perfectly fine prior to Lucid, no longer work (due to the stricter handling of the 'aa' flag). I run caching resolvers for an ISP; all the time we're on an affected version of BIND, our customers can't access specific domains. Very few