Features/BIND10

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Detailed Description)
Line 25: Line 25:
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
 +
Users can easily install & use BIND10 from distribution repositories.
  
 
== Scope ==
 
== Scope ==
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 +
* package BIND10
 +
* pass it through review
 +
* ship it in distro
  
 
== How To Test ==
 
== How To Test ==
 
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
 
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
 
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
 
 
A good "how to test" should answer these four questions:
 
  
 
0. What special hardware / data / etc. is needed (if any)?
 
0. What special hardware / data / etc. is needed (if any)?
Line 43: Line 43:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
 +
 +
* install bind10
 +
* test DNS authoritative/recursive server
 +
* test DHCP4/DHCP6 servers
 +
* configuration is really non-trivial, good documentation is [http://bind10.isc.org/docs/bind10-guide.html BIND10 guide]
  
 
== User Experience ==
 
== User Experience ==
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 +
Ability to use BIND10.
  
 
== Dependencies ==
 
== Dependencies ==
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 +
None
  
 
== Contingency Plan ==
 
== Contingency Plan ==
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 +
Not needed, users just don't have to install bind10 pkgs.
  
 
== Documentation ==
 
== Documentation ==
Line 60: Line 68:
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
*
+
* http://bind10.isc.org/wiki
 +
* [http://bind10.isc.org/docs/bind10-guide.html BIND10 guide]
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
* See [[Talk:Features/Your_Feature_Name]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
+
* See [[Talk:Features/BIND10]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
  
  

Revision as of 12:46, 8 January 2013

Contents

BIND10

Summary

BIND10 is next generation of the popular BIND9 DNS server rewritten from scratch. BIND10 suite includes both DNS and DHCP service servers.

Owner

  • Email: atkac redhat com

Current status

  • Targeted release: Fedora 19
  • Last updated: 08-Jan-2013
  • Percentage of completion: 00%


Detailed Description

BIND10 suite implements two crucial network services - DNS and DHCP. The BIND10 is going to replace both widely used ISC BIND9 and ISC DHCP4 software in the future. It is written from scratch and has modular design.

Benefit to Fedora

Users can easily install & use BIND10 from distribution repositories.

Scope

  • package BIND10
  • pass it through review
  • ship it in distro

How To Test

  • install bind10
  • test DNS authoritative/recursive server
  • test DHCP4/DHCP6 servers
  • configuration is really non-trivial, good documentation is BIND10 guide

User Experience

Ability to use BIND10.

Dependencies

None

Contingency Plan

Not needed, users just don't have to install bind10 pkgs.

Documentation

Release Notes

Comments and Discussion