Issue 336 in roster-dns-management: When adding a reverse slave zone a reverse range permission is created.

[roster-dns...@googlecode.com]

Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Medium Release-0.19

New issue 336 by sharrell...@gmail.com: When adding a reverse slave zone a
reverse range permission is created.
http://code.google.com/p/roster-dns-management/issues/detail?id=336

When adding a reverse slave zone a reverse range permission is created. It
shouldn't be created since a slave zone has no records.

[roster-dns...@googlecode.com]

Updates:
Owner: J.S.P...@gmail.com

Comment #1 on issue 336 by J.S.P...@gmail.com: When adding a reverse

slave zone a reverse range permission is created.
http://code.google.com/p/roster-dns-management/issues/detail?id=336

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[roster-dns...@googlecode.com]

Comment #2 on issue 336 by J.S.P...@gmail.com: When adding a reverse

slave zone a reverse range permission is created.
http://code.google.com/p/roster-dns-management/issues/detail?id=336

I believe this was fixed already. See -
https://code.google.com/p/roster-dns-management/source/detail?r=1057&path=/trunk/roster-user-tools/scripts/dnsmkzone

[roster-dns...@googlecode.com]

Updates:
Status: Fixed

Comment #3 on issue 336 by Cooke...@gmail.com: When adding a reverse slave

zone a reverse range permission is created.
http://code.google.com/p/roster-dns-management/issues/detail?id=336

Fixed in r1057