Issue #105: Cache is not flushed after deleting a zone with conditional forwarder - bind-dyndb-ldap

bind-dyndb-ldap

#105 Cache is not flushed after deleting a zone with conditional forwarder

Closed: Fixed None Opened 11 years ago by pspacek.

This bug is "deletion counterpart" of bug #97.

Steps to reproduce are very similar - create conditional forwarder, ask for record from forwarded zone, remove conditional forwarder and then try to ask for the same record again.

The buggy version returns same results for both queries.

pspacek commented 10 years ago

It was fixed in version 2.3 back in 2012.

pspacek commented 9 years ago

I'm closing this ancient ticket. It was properly fixed by introduction of idnsForwardZone object class and by removing support for forwarding definition from idnsZone object class.

Metadata Update from @pspacek:
- Issue assigned to pspacek
- Issue set to the milestone: Fedora 20

7 years ago

Metadata

Assignee

pspacek

Tags

None

Blocking

None

Depending on

None

Priority

major

Milestone

Fedora 20

rhbz

blockedby

None

blocking

None

fixedby

760bebb0e8744301420cf6e4918690ed171529a2, 3bf0d6fa6e6fe1bd81882a6819e9680e9c069997, bff6d68ac200ea1ab543b090ab2763e2437a48ce

fixedin

5.0

proposedmilestone

None

type

defect

component

ldap driver

version

2.3

keywords

nihsyndrome

None

bind-dyndb-ldap

Source Code

Documentation

#105 Cache is not flushed after deleting a zone with conditional forwarder Closed: Fixed None Opened 11 years ago by pspacek.

Metadata

#105 Cache is not flushed after deleting a zone with conditional forwarder

Closed: Fixed None Opened 11 years ago by pspacek.