Issue #115: PTR record synchronization deletes all data under reverse name - bind-dyndb-ldap

bind-dyndb-ldap

#115 PTR record synchronization deletes all data under reverse name

Closed: Fixed None Opened 11 years ago by pspacek.

PTR record synchronization sometimes delete all data under name in reverse tree (e.g. 1.2.0.192.in-addr.arpa.).

Inputs

Forward zone:

test.example.com.       3600 IN  A  192.0.2.1

Reverse zone:

1.2.0.192.in-addr.arpa. 3600 IN PTR test.example.com.
1.2.0.192.in-addr.arpa. 3600 IN TXT "address reserved for DNS tests"

Update:

update delete test.example.com. IN A 192.0.2.1

Result

Forward zone:

Name test.example.com. does not exist.

Reverse zone:

Name 1.2.0.192.in-addr.arpa. does not exist.

Reverse zone should contain the original TXT record, only PTR record should be deleted:

1.2.0.192.in-addr.arpa. 3600 IN TXT "address reserved for DNS tests"

pspacek commented 11 years ago

The fix was really simple so I sent the patch to the freeipa-devel list.

dpal commented 11 years ago

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=958140

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

7 years ago

Metadata

Assignee

pspacek

Tags

None

Blocking

None

Depending on

None

Priority

major

Milestone

Fedora 19

rhbz

https://bugzilla.redhat.com/show_bug.cgi?id=958140

blockedby

None

blocking

None

fixedby

1c63c045b5238fb675b7a517876869bcace2cdab

fixedin

3.2

proposedmilestone

None

type

defect

component

ldap driver

version

2.3-2.el6

keywords

syncptr

None

bind-dyndb-ldap

Source Code

Documentation

#115 PTR record synchronization deletes all data under reverse name Closed: Fixed None Opened 11 years ago by pspacek.

Metadata

#115 PTR record synchronization deletes all data under reverse name

Closed: Fixed None Opened 11 years ago by pspacek.