Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Wed, 26 Sep 2012 02:05:09 +1100 (NCT)
From: "Kiran Ayyagari (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <1744963245.122463.1348585509148.JavaMail.jiratomcat@arcas>
Subject: [jira] [Closed] (DIRSERVER-132) Implement zone catalog
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRSERVER-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Ayyagari closed DIRSERVER-132.
------------------------------------

    Resolution: Won't Fix

DNS server is not actively maintained
                
> Implement zone catalog
> ----------------------
>
>                 Key: DIRSERVER-132
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-132
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>          Components: dns
>            Reporter: Enrique Rodriguez
>            Assignee: Enrique Rodriguez
>             Fix For: 2.1.0
>
>
> RFC 1035 6.1.2 describes a "catalog" that contains pointers to zone data.  We will implement a zone catalog and ensure that zone and Kerberos realm semantics are similar.
> o  apache.schema objectClass called apachedsServiceConfiguration 
> o  STRUCTURAL objectClass MUST cn
> o  uses ExtensibleObject
> o  apachedsDnsConfiguration extends apachedsServiceConfiguration
> o  OC apacheCatalogEntry is a mapping of a zone name attribute to a zoneBaseDN attribute
> o  zone=example.com --> ou=zones,dc=example,dc=com
> o  put a ou=zones under the configuration for the service instance
> o  add OC apacheCatalogEntry's
> o  pull all catalog entries into memory with a single level search under ou=zones
> o  use the zoneBaseDn with the InitialContextFactory.  The nexus will figure out under what partition it is.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira