# nets: pool of addresses available for allocation by specific join servers.
#
# $Id: nets,v 1.11 1996/01/15 17:50:00 hyung Exp $
#
# DESCRIPTION
# This file instructs the server which nets and subnets it is to administer
# and the addresses which are available for dynamic allocation.
#
# Each non-comment line in this file has up to three fields:
#    Subnet IP address
#    IP address or name of host "owning" the address range.
#    The address range itself

# If there are fewer than three fields then the subnet and owner
# are implied by previous entries. The address range is specified
# as one or two IP addresses. If two then they must be separated
# by a dash "-", with no whitespace intervening. Multiple ranges
# may be specified for any owner. The IP addresses are checked for
# syntax, for uniqueness of ownership, and validity on the network
# specified. If the owner of a range is multi-homed, then the
# name used must be its canonical name (e.g. as echoed by hostname),
# or, if specified by address, the address must correspond to
# the canonical name as given in /etc/hosts
#
# For OpenVMS with DHCP configured on multiple cluster nodes (ie. DHCP
# cluster failover) enter 0.0.0.0 in the "owning" DHCP server field
# (field 2).
#

# Examples:
#192.1.1.32      192.1.1.34       192.1.1.35-192.1.1.43
#192.1.1.32      192.1.2.34       192.1.1.44-192.1.1.62
#192.1.1.64      192.1.2.34       192.1.1.66-192.1.1.94
#
# DHCP cluster failover example:
#192.1.1.64      0.0.0.0          192.1.1.66-192.1.1.94