Bug 1229599 - [RFE] option for setting maximum negative cache TTL
Summary: [RFE] option for setting maximum negative cache TTL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: unbound
Version: 22
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Tomáš Hozza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: Default_Local_DNS_Resolver 1229596
TreeView+ depends on / blocked
 
Reported: 2015-06-09 08:32 UTC by Tomáš Hozza
Modified: 2015-06-30 00:21 UTC (History)
4 users (show)

Fixed In Version: unbound-1.5.3-8.fc22
Clone Of:
Environment:
Last Closed: 2015-06-30 00:21:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomáš Hozza 2015-06-09 08:32:16 UTC
Description of problem:
Currently Unbound does not provide an option to set the maximum negative cache TTL. This needs to be implemented first, so we can set a low negative cache TTL in Fedora, to prevent user experience issue in the early stages.

This is Fedora bug for tracking purposes, due to the Fedora 23 "default DNS resolver" change.

Upstream bug:
https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=675

Comment 1 Fedora Update System 2015-06-15 19:31:10 UTC
unbound-1.5.3-7.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/unbound-1.5.3-7.fc22

Comment 2 Fedora Update System 2015-06-21 00:20:04 UTC
Package unbound-1.5.3-8.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing unbound-1.5.3-8.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-10359/unbound-1.5.3-8.fc22
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2015-06-30 00:21:42 UTC
unbound-1.5.3-8.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.