Bug 1360222

Summary:	cache-max-negative-ttl don't work as expected
Product:	[Fedora] Fedora	Reporter:	Harald Reindl <h.reindl>
Component:	unbound	Assignee:	Paul Wouters <pwouters>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	25	CC:	drjohnson1, pj.pandit, pwouters, thozza
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-08 15:54:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Harald Reindl 2016-07-26 09:31:56 UTC

unbound running as recursion cache on a inbound mailserver using DNSBL/URIBL with some forwarding RBL zones to a local "rbldnsd"

server:
 cache-min-ttl: 3600
 cache-max-ttl: 43200
 cache-max-negative-ttl: 60

as far as i understand "cache-max-negative-ttl" only positive responses for RBL/DNSBL on a inbound MX should be cached for an hour - today i added one IP to our own rbldnsd which is configured like below as forwarder for unbound

15 minutes later i passed the spam message again to spamd - no hit
reastarted unbound hard - RBL hits, our own as well as external ones and 2 URIBL

my understanding of "cache-max-negative-ttl" is that in case of NXDOMAIN responses it should hit after 60 seconds and only postitive hits should be cached for 60 minutes

forward-zone:
 name: "dnsbl.thelounge.net."
 forward-addr: 127.0.0.1@1053

Comment 1 Harald Reindl 2016-08-13 15:47:58 UTC

upstream bugtracker: https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=818

Comment 2 Paul Wouters 2016-09-27 22:25:50 UTC

waiting on upstream resolution of bug

Comment 3 Fedora End Of Life 2017-07-25 22:04:09 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-08-08 15:54:09 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.