diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml index 3f8253fe36..51bcc42258 100644 --- a/doc/guide/bind10-guide.xml +++ b/doc/guide/bind10-guide.xml @@ -785,7 +785,7 @@ as a dependency earlier --> - Starting BIND10 with <command>bind10</command> + Starting BIND 10 with <command>bind10</command> BIND 10 provides the bind10 command which starts up the required processes. @@ -1746,7 +1746,7 @@ can use various data source backends. Each data source has several options. The first one is type, which specifies the type of data source to - use. Valid types include the ones listed below, but bind10 uses + use. Valid types include the ones listed below, but BIND 10 uses dynamically loaded modules for them, so there may be more in your case. This option is mandatory. @@ -1794,7 +1794,7 @@ can use various data source backends.
Examples - As this is one of the more complex configurations of Bind10, + As this is one of the more complex configurations of BIND 10, we show some examples. They all assume they start with default configuration. @@ -1820,7 +1820,7 @@ can use various data source backends. > config commit Now every time the zone in the data source is changed by the - operator, Bind10 needs to be told to reload it, by + operator, the authoritative server needs to be told to reload it, by > Auth loadzone example.org You don't need to do this when the zone is modified by XfrIn, it does so automatically. @@ -2602,18 +2602,18 @@ then change those defaults with config set Resolver/forward_addresses[0]/address be deployed that facilitate communication between servers and clients. Even though principles of both DHCPv4 and DHCPv6 are somewhat similar, these are two radically different - protocols. BIND10 offers server implementations for both DHCPv4 + protocols. BIND 10 offers server implementations for both DHCPv4 and DHCPv6. This chapter is about DHCP for IPv4. For a description of the DHCPv6 server, see . The DHCPv4 server component is currently under intense development. You may want to check out BIND10 DHCP (Kea) wiki + url="http://bind10.isc.org/wiki/Kea">BIND 10 DHCP (Kea) wiki and recent posts on BIND10 + url="https://lists.isc.org/mailman/listinfo/bind10-dev">BIND 10 developers mailing list. - The DHCPv4 and DHCPv6 components in BIND10 architecture are + The DHCPv4 and DHCPv6 components in BIND 10 architecture are internally code named Kea. @@ -2631,7 +2631,7 @@ then change those defaults with config set Resolver/forward_addresses[0]/address
DHCPv4 Server Usage - BIND10 provides the DHCPv4 server component since December + BIND 10 provides the DHCPv4 server component since December 2011. It is a skeleton server and can be described as an early prototype that is not fully functional yet. It is mature enough to conduct first tests in lab environment, but it has @@ -2640,9 +2640,9 @@ then change those defaults with config set Resolver/forward_addresses[0]/address - b10-dhcp4 is a BIND10 component and is being - run under BIND10 framework. To add a DHCPv4 process to the set of running - BIND10 services, you can use following commands in bindctl: + b10-dhcp4 is a BIND 10 component and is being + run under BIND 10 framework. To add a DHCPv4 process to the set of running + BIND 10 services, you can use following commands in bindctl: > config add Boss/components b10-dhcp4 > config set Boss/components/b10-dhcp4/kind dispensable > config commit @@ -2792,19 +2792,19 @@ const std::string HARDCODED_SERVER_ID = "192.0.2.1"; DHCPv6 Server Dynamic Host Configuration Protocol for IPv6 (DHCPv6) is - specified in RFC3315. BIND10 provides DHCPv6 server implementation + specified in RFC3315. BIND 10 provides DHCPv6 server implementation that is described in this chapter. For a description of the DHCPv4 server implementation, see . The DHCPv6 server component is currently under intense development. You may want to check out BIND10 DHCP (Kea) wiki + url="http://bind10.isc.org/wiki/Kea">BIND 10 DHCP (Kea) wiki and recent posts on BIND10 + url="https://lists.isc.org/mailman/listinfo/bind10-dev">BIND 10 developers mailing list. - The DHCPv4 and DHCPv6 components in BIND10 architecture are + The DHCPv4 and DHCPv6 components in BIND 10 architecture are internally code named Kea. @@ -2823,7 +2823,7 @@ const std::string HARDCODED_SERVER_ID = "192.0.2.1";
DHCPv6 Server Usage - BIND10 provides the DHCPv6 server component since September + BIND 10 provides the DHCPv6 server component since September 2011. It is a skeleton server and can be described as an early prototype that is not fully functional yet. It is mature enough to conduct first tests in lab environment, but it has @@ -2832,9 +2832,9 @@ const std::string HARDCODED_SERVER_ID = "192.0.2.1"; - b10-dhcp6 is a BIND10 component and is being - run under BIND10 framework. To add a DHCPv6 process to the set of running - BIND10 services, you can use following commands in bindctl: + b10-dhcp6 is a BIND 10 component and is being + run under BIND 10 framework. To add a DHCPv6 process to the set of running + BIND 10 services, you can use following commands in bindctl: > config add Boss/components b10-dhcp6 > config set Boss/components/b10-dhcp6/kind dispensable > config commit @@ -3001,7 +3001,7 @@ const std::string HARDCODED_DNS_SERVER = "2001:db8:1::1"; For non-Linux systems, there is currently stub implementation provided. Interface manager detects loopback interfaces only as their name (lo or lo0) can be easily predicted. - Please contact BIND10 development team if you are interested + Please contact the BIND 10 development team if you are interested in running DHCP components on systems other than Linux.