[
https://issues.apache.org/jira/browse/ZOOKEEPER-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882607#action_12882607
]
Fred Emmott commented on ZOOKEEPER-703:
---------------------------------------
Quick-and-dirty code:
http://gitorious.org/zkdns/zkdns
No promises about reliability etc. We only use this to provide a convenience
hostname for accessing the hbase master web interface (not depended on by any
live services).
Can be used for any entry containing an ipv4 address, optionally followed by a
port. Hostname format is "/hbase/master" -> "master.hbase.zk". We use CNAMEs to
hook this into our existing hierarchy.
> GSoC 2010: ZooKeeper DNS Server
> -------------------------------
>
> Key: ZOOKEEPER-703
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-703
> Project: Zookeeper
> Issue Type: Wish
> Reporter: Henry Robinson
>
> ZooKeeper DNS Server
> Possible Mentor
> Henry Robinson (henry at apache dot org)
> Requirements
> Java or Python or C
> Description
> Although ZooKeeper is primarily used for co-ordination of distributed
> processes, its consistency semantics means that it's a good candidate for
> serving small (key,value) records as well. The Domain Name Service has
> similar requirements, raising the interesting question of whether ZooKeeper
> would be a capable DNS server for your local network. One intriguing
> possibility is having versioned DNS records, such that known-good
> configurations can be stored and rolled back to in the case of an issue. If
> this versioning primitive proves to be useful, it's easy to imagine other
> types of configuration that could be stored.
> This project would involve designing and building an RFC-1035 compliant DNS
> server and performing a detailed performance study against an already
> existant simple DNS server like tinydns.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
