You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kiran Ayyagari (JIRA)" <ji...@apache.org> on 2012/09/25 17:05:09 UTC
[jira] [Closed] (DIRSERVER-132) Implement zone catalog
[ 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