[Dnssec-trigger] current status?

[Tomas Hozza]

On 03/12/2015 02:31 PM, Chuck Anderson wrote:
> On Thu, Mar 12, 2015 at 09:20:28AM +0100, Tomas Hozza wrote:
>> On 03/11/2015 08:21 PM, Chuck Anderson wrote:
>>> Every day after resuming from suspend, I have crash messages pop up on
>>> Fedora 21 from dnssec-trigger (even after I fixed rhbz#1187371 myself
>>> over a month ago).
>>>
>>> I'm very concerned about this:
>>>
>>> https://fedoraproject.org//wiki/Changes/Default_Local_DNS_Resolver
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1187371
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1187183
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1200996
>>
>> Hi Chuck.
>>
>> I'm also using dnssec-trigger on Fedora 21 every day, with VPN and
>> SELinux in enforcing mode. But my Fedora is also upgraded from older
>> ones.
> 
> My systems are almost always fresh installs, but I do update them with
> "dnf update" and reboot every once in while, maybe every week or two.
> I started seeing this crash only on my home laptop I use every day.
> It started in January and hasn't gone away.  My earlier attempt to
> file this bug with ABRT local core dump analysis failed, so I just
> filed this one using the retrace server:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1201283
> 
>> Sometimes my system also ends up without resolv.conf due to
>> https://bugzilla.redhat.com/show_bug.cgi?id=1195752 . But other
>> than that, the experience is pretty seamless.
> 
> My experience is also mostly seamless, at least until this
> disappearing /etc/resolv.conf just started happening.  My earlier
> report about DNS resolution timeouts after re-opening Firefox with
> many tabs open I believe is related to the NAT table filling up on my
> old Netgear stock-firmware router when unbound gets flooded with DNS
> resolution requests from Firefox.  I do not have that problem anymore
> after moving to a newer Netgear router running Cerowrt (Openwrt fork).
> 
>> We deferred the Fedora Change to Fedora 23, to sort out these issues.
>> Lately we had some higher priority issues to deal with, but we are
>> aware of the status in Fedora and are planning to address all the
>> user's issues.
> 
> Thank you, that is good to hear.  I see the wiki page shows Fedora 23
> as the targeted release, but the "Last Update" date wasn't changed and
> still says 2014-04-11.
> 
>> Thank you for filing bugs and for adding them to the tracker bug.
> 
> I'll finish going through the bugs and add more I think should be
> blockers.
> 
>> Feel free to reach to us directly by email, here on the mailing list
>> or via Bugzilla.
> 
> Thanks.  I was worried since there seemed to be a long silence.  I am
> also a Fedora packager and could volunteer to help, but my time is
> also limited.  But if it would help for me to push out updates for
> trivial fixes like rhbz#1187371, I can do that.

I just sent some patches to the mailing list and will fix those in Fedora
once I get some response for them. So I'll cover also rhbz#1187371.
Anyway thank you for your offer. I think we would appreciate any help,
so feel free to request permission in the fedora package-db.

Regards,
-- 
Tomas Hozza
Software Engineer - EMEA ENG Developer Experience

PGP: 1D9F3C2D
Red Hat Inc.                               http://cz.redhat.com