DHCP clients connected to the same network as the ISC DHCP server or
ISC relay agent will not see messages from the DHCP server. It *is*
possible to run into trouble with this on Linux 2.2 and later if you
-are running a verson of the DHCP server that was compiled on a Linux
+are running a version of the DHCP server that was compiled on a Linux
2.0 system, though.
It is possible to work around this problem on some versions of Linux
on multi-interface machines if configured to listen on only one of the
interfaces.)
-We have reports of Windows XP clients having difficutly retrieving
+We have reports of Windows XP clients having difficulty retrieving
addresses from a server running on an AIX machine. This issue
was traced to the client requiring messages be sent to the all ones
broadcast address (255.255.255.255) while the AIX server was sending
NEW FEATURES
-The major "theme" for ISC DHCP 4.3.x was to update the support for
+The major "theme" for ISC DHCP 4.3.x was to update the suport for
DHCPv6 to include several of the features that have been available
for DHCPv4. These include:
- DHCPv6 includes human-readable text in status code messages, in
English. A method to reconfigure or support other languages would
- be preferrable.
+ be preferable.
- The "host-identifier" option is limited to a simple token.
than extend or renew the lease. This absolves the server of needing
to perform an fsync() operation on the lease database before reply,
which improves performance. [ISC-Bugs #22228]
- Update this patch to support asynchronous DDNS. If the server is
+ Updated this patch to support asynchronous DDNS. If the server is
attempting to do DDNS on a lease it should be udpated and written to
disk even if that wouldn't be necessary due to the thresholding.
[ISC-Bugs #26311]
[ISC-Bugs #19598]
- When doing DDNS if there isn't an appropriate zone statement attempt
- to find a reasoanble nameserver via a DNS resolver. This restores
+ to find a reasonable nameserver via a DNS resolver. This restores
some functionality that was lost in the transition to asynchronous
DDNS. Due to the lack of security and increase in fragility of the
system when using this feature we strongly recommend the use of