mir/isc-dhcp
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/dhcp synced 2025-08-31 06:15:55 +00:00
Code Issues Releases Wiki Activity

Make name-servers option ien116-name-servers

Browse Source
This commit is contained in:
Ted Lemon
1997-06-02 23:27:22 +00:00
parent 40f63fcd4f
commit ee31d9923a
2 changed files with 115 additions and 115 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
server/dhcpd.conf.5
View File

@@ -171,7 +171,7 @@ the entire organization), and so on. So, for example:
.nf
option domain-name "isc.org";
option name-servers ns1.isc.org, ns2.isc.org;
option domain-name-servers ns1.isc.org, ns2.isc.org;
.ce 1
Figure 2
@@ -783,9 +783,9 @@ The time-server option specifies a list of RFC 868 time servers
available to the client. Servers should be listed in order of
preference.
.PP
\fBoption\fR \fBname-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR ... ];
\fBoption\fR \fBien116-name-servers\fR \fIip-address\fR [\fB,\fR \fIip-address\fR ... ];
.PP
The name-servers option specifies a list of IEN 116 name servers
The ien116-name-servers option specifies a list of IEN 116 name servers
available to the client. Servers should be listed in order of
preference.
.PP

224
server/dhcpd.conf.cat5
View File

@@ -171,7 +171,7 @@ dhcpd.conf(5) dhcpd.conf(5)
organization), and so on. So, for example:
option domain-name "isc.org";
option name-servers ns1.isc.org, ns2.isc.org;
option domain-name-servers ns1.isc.org, ns2.isc.org;
Figure 2
@@ -819,37 +819,37 @@ dhcpd.conf(5) dhcpd.conf(5)
servers available to the client. Servers should be listed
in order of preference.
ooppttiioonn nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];
ooppttiioonn iieenn111166--nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ...
];
The name-servers option specifies a list of IEN 116 name
servers available to the client. Servers should be listed
in order of preference.
The ien116-name-servers option specifies a list of IEN 116
name servers available to the client. Servers should be
listed in order of preference.
ooppttiioonn ddoommaaiinn--nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ...
ooppttiioonn ddoommaaiinn--nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ...
];;
The domain-name-servers option specifies a list of Domain
Name System (STD 13, RFC 1035) name servers available to
the client. Servers should be listed in order of prefer-
The domain-name-servers option specifies a list of Domain
Name System (STD 13, RFC 1035) name servers available to
the client. Servers should be listed in order of prefer-
ence.
ooppttiioonn lloogg--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
The log-server option specifies a list of MIT-LCS UDP log
The log-server option specifies a list of MIT-LCS UDP log
servers available to the client. Servers should be listed
in order of preference.
ooppttiioonn ccooookkiiee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
The cookie server option specifies a list of RFC 865
The cookie server option specifies a list of RFC 865
cookie servers available to the client. Servers should be
listed in order of preference.
ooppttiioonn llpprr--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
The LPR server option specifies a list of RFC 1179 line
printer servers available to the client. Servers should
be listed in order of preference.
The LPR server option specifies a list of RFC 1179 line
printer servers available to the client. Servers should
@@ -862,43 +862,45 @@ dhcpd.conf(5) dhcpd.conf(5)
dhcpd.conf(5) dhcpd.conf(5)
be listed in order of preference.
ooppttiioonn iimmpprreessss--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
The impress-server option specifies a list of Imagen
Impress servers available to the client. Servers should
The impress-server option specifies a list of Imagen
Impress servers available to the client. Servers should
be listed in order of preference.
ooppttiioonn rreessoouurrccee--llooccaattiioonn--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s
... ];;
This option specifies a list of RFC 887 Resource Location
This option specifies a list of RFC 887 Resource Location
servers available to the client. Servers should be listed
in order of preference.
ooppttiioonn hhoosstt--nnaammee _s_t_r_i_n_g;;
This option specifies the name of the client. The name
This option specifies the name of the client. The name
may or may not be qualified with the local domain name (it
is preferable to use the domain-name option to specify the
domain name). See RFC 1035 for character set restric-
domain name). See RFC 1035 for character set restric-
tions.
ooppttiioonn bboooott--ssiizzee _u_i_n_t_1_6;;
This option specifies the length in 512-octet blocks of
This option specifies the length in 512-octet blocks of
the default boot image for the client.
ooppttiioonn mmeerriitt--dduummpp _s_t_r_i_n_g;;
This option specifies the path-name of a file to which the
client's core image should be dumped in the event the
client crashes. The path is formatted as a character
client's core image should be dumped in the event the
client crashes. The path is formatted as a character
string consisting of characters from the NVT ASCII charac-
ter set.
ooppttiioonn ddoommaaiinn--nnaammee _s_t_r_i_n_g;;
This option specifies the domain name that client should
This option specifies the domain name that client should
use when resolving hostnames via the Domain Name System.
ooppttiioonn sswwaapp--sseerrvveerr _i_p_-_a_d_d_r_e_s_s;;
@@ -907,15 +909,13 @@ dhcpd.conf(5) dhcpd.conf(5)
ooppttiioonn rroooott--ppaatthh _s_t_r_i_n_g;;
This option specifies the path-name that contains the
client's root disk. The path is formatted as a character
This option specifies the path-name that contains the
client's root disk. The path is formatted as a character
string consisting of characters from the NVT ASCII charac-
ter set.
ooppttiioonn iipp--ffoorrwwaarrddiinngg _f_l_a_g;;
This option specifies whether the client should configure
its IP layer for packet forwarding. A value of 0 means
@@ -928,61 +928,61 @@ dhcpd.conf(5) dhcpd.conf(5)
dhcpd.conf(5) dhcpd.conf(5)
disable IP forwarding, and a value of 1 means enable IP
This option specifies whether the client should configure
its IP layer for packet forwarding. A value of 0 means
disable IP forwarding, and a value of 1 means enable IP
forwarding.
ooppttiioonn nnoonn--llooccaall--ssoouurrccee--rroouuttiinngg _f_l_a_g;;
This option specifies whether the client should configure
its IP layer to allow forwarding of datagrams with non-
local source routes (see Section 3.3.5 of [4] for a dis-
cussion of this topic). A value of 0 means disallow for-
warding of such datagrams, and a value of 1 means allow
This option specifies whether the client should configure
its IP layer to allow forwarding of datagrams with non-
local source routes (see Section 3.3.5 of [4] for a dis-
cussion of this topic). A value of 0 means disallow for-
warding of such datagrams, and a value of 1 means allow
forwarding.
ooppttiioonn ppoolliiccyy--ffiilltteerr _i_p_-_a_d_d_r_e_s_s _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s
ooppttiioonn ppoolliiccyy--ffiilltteerr _i_p_-_a_d_d_r_e_s_s _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s
_i_p_-_a_d_d_r_e_s_s ... ];;
This option specifies policy filters for non-local source
routing. The filters consist of a list of IP addresses
and masks which specify destination/mask pairs with which
This option specifies policy filters for non-local source
routing. The filters consist of a list of IP addresses
and masks which specify destination/mask pairs with which
to filter incoming source routes.
Any source routed datagram whose next-hop address does not
match one of the filters should be discarded by the
match one of the filters should be discarded by the
client.
See STD 3 (RFC1122) for further information.
ooppttiioonn mmaaxx--ddggrraamm--rreeaasssseemmbbllyy _u_i_n_t_1_6;;
This option specifies the maximum size datagram that the
client should be prepared to reassemble. The minimum
This option specifies the maximum size datagram that the
client should be prepared to reassemble. The minimum
value legal value is 576.
ooppttiioonn ddeeffaauulltt--iipp--ttttll _u_i_n_t_8_;
This option specifies the default time-to-live that the
This option specifies the default time-to-live that the
client should use on outgoing datagrams.
ooppttiioonn ppaatthh--mmttuu--aaggiinngg--ttiimmeeoouutt _u_i_n_t_3_2;;
This option specifies the timeout (in seconds) to use when
aging Path MTU values discovered by the mechanism defined
aging Path MTU values discovered by the mechanism defined
in RFC 1191.
ooppttiioonn ppaatthh--mmttuu--ppllaatteeaauu--ttaabbllee _u_i_n_t_1_6 [,, _u_i_n_t_1_6 ... ];;
This option specifies a table of MTU sizes to use when
This option specifies a table of MTU sizes to use when
performing Path MTU Discovery as defined in RFC 1191. The
table is formatted as a list of 16-bit unsigned integers,
ordered from smallest to largest. The minimum MTU value
table is formatted as a list of 16-bit unsigned integers,
ordered from smallest to largest. The minimum MTU value
cannot be smaller than 68.
ooppttiioonn iinntteerrffaaccee--mmttuu _u_i_n_t_1_6;;
This option specifies the MTU to use on this interface.
15
@@ -994,63 +994,63 @@ dhcpd.conf(5) dhcpd.conf(5)
dhcpd.conf(5) dhcpd.conf(5)
This option specifies the MTU to use on this interface.
The minimum legal value for the MTU is 68.
ooppttiioonn aallll--ssuubbnneettss--llooccaall _f_l_a_g;;
This option specifies whether or not the client may assume
that all subnets of the IP network to which the client is
connected use the same MTU as the subnet of that network
to which the client is directly connected. A value of 1
that all subnets of the IP network to which the client is
connected use the same MTU as the subnet of that network
to which the client is directly connected. A value of 1
indicates that all subnets share the same MTU. A value of
0 means that the client should assume that some subnets of
the directly connected network may have smaller MTUs.
ooppttiioonn bbrrooaaddccaasstt--aaddddrreessss _i_p_-_a_d_d_r_e_s_s;;
This option specifies the broadcast address in use on the
This option specifies the broadcast address in use on the
client's subnet. Legal values for broadcast addresses are
specified in section 3.2.1.3 of STD 3 (RFC1122).
ooppttiioonn ppeerrffoorrmm--mmaasskk--ddiissccoovveerryy _f_l_a_g;;
This option specifies whether or not the client should
perform subnet mask discovery using ICMP. A value of 0
indicates that the client should not perform mask discov-
ery. A value of 1 means that the client should perform
This option specifies whether or not the client should
perform subnet mask discovery using ICMP. A value of 0
indicates that the client should not perform mask discov-
ery. A value of 1 means that the client should perform
mask discovery.
ooppttiioonn mmaasskk--ssuupppplliieerr _f_l_a_g;;
This option specifies whether or not the client should
respond to subnet mask requests using ICMP. A value of 0
indicates that the client should not respond. A value of
This option specifies whether or not the client should
respond to subnet mask requests using ICMP. A value of 0
indicates that the client should not respond. A value of
1 means that the client should respond.
ooppttiioonn rroouutteerr--ddiissccoovveerryy _f_l_a_g;;
This option specifies whether or not the client should
This option specifies whether or not the client should
solicit routers using the Router Discovery mechanism
defined in RFC 1256. A value of 0 indicates that the
client should not perform router discovery. A value of 1
defined in RFC 1256. A value of 0 indicates that the
client should not perform router discovery. A value of 1
means that the client should perform router discovery.
ooppttiioonn rroouutteerr--ssoolliicciittaattiioonn--aaddddrreessss _i_p_-_a_d_d_r_e_s_s;;
This option specifies the address to which the client
This option specifies the address to which the client
should transmit router solicitation requests.
ooppttiioonn ssttaattiicc--rroouutteess _i_p_-_a_d_d_r_e_s_s _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s
ooppttiioonn ssttaattiicc--rroouutteess _i_p_-_a_d_d_r_e_s_s _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s
_i_p_-_a_d_d_r_e_s_s ... ];;
This option specifies a list of static routes that the
client should install in its routing cache. If multiple
routes to the same destination are specified, they are
This option specifies a list of static routes that the
client should install in its routing cache. If multiple
routes to the same destination are specified, they are
listed in descending order of priority.
16
@@ -1060,20 +1060,20 @@ dhcpd.conf(5) dhcpd.conf(5)
dhcpd.conf(5) dhcpd.conf(5)
The routes consist of a list of IP address pairs. The
first address is the destination address, and the second
The routes consist of a list of IP address pairs. The
first address is the destination address, and the second
address is the router for the destination.
The default route (0.0.0.0) is an illegal destination for
a static route. To specify the default route, use the
The default route (0.0.0.0) is an illegal destination for
a static route. To specify the default route, use the
rroouutteerrss option.
ooppttiioonn ttrraaiilleerr--eennccaappssuullaattiioonn _f_l_a_g;;
This option specifies whether or not the client should
negotiate the use of trailers (RFC 893 [14]) when using
the ARP protocol. A value of 0 indicates that the client
should not attempt to use trailers. A value of 1 means
This option specifies whether or not the client should
negotiate the use of trailers (RFC 893 [14]) when using
the ARP protocol. A value of 0 indicates that the client
should not attempt to use trailers. A value of 1 means
that the client should attempt to use trailers.
ooppttiioonn aarrpp--ccaacchhee--ttiimmeeoouutt _u_i_n_t_3_2;;
@@ -1084,32 +1084,32 @@ dhcpd.conf(5) dhcpd.conf(5)
ooppttiioonn iieeeeee880022--33--eennccaappssuullaattiioonn _f_l_a_g;;
This option specifies whether or not the client should use
Ethernet Version 2 (RFC 894) or IEEE 802.3 (RFC 1042)
Ethernet Version 2 (RFC 894) or IEEE 802.3 (RFC 1042)
encapsulation if the interface is an Ethernet. A value of
0 indicates that the client should use RFC 894 encapsula-
tion. A value of 1 means that the client should use RFC
0 indicates that the client should use RFC 894 encapsula-
tion. A value of 1 means that the client should use RFC
1042 encapsulation.
ooppttiioonn ddeeffaauulltt--ttccpp--ttttll _u_i_n_t_8;;
This option specifies the default TTL that the client
should use when sending TCP segments. The minimum value
This option specifies the default TTL that the client
should use when sending TCP segments. The minimum value
is 1.
ooppttiioonn ttccpp--kkeeeeppaalliivvee--iinntteerrvvaall _u_i_n_t_3_2;;
This option specifies the interval (in seconds) that the
client TCP should wait before sending a keepalive message
on a TCP connection. The time is specified as a 32-bit
unsigned integer. A value of zero indicates that the
client should not generate keepalive messages on connec-
This option specifies the interval (in seconds) that the
client TCP should wait before sending a keepalive message
on a TCP connection. The time is specified as a 32-bit
unsigned integer. A value of zero indicates that the
client should not generate keepalive messages on connec-
tions unless specifically requested by an application.
ooppttiioonn ttccpp--kkeeeeppaalliivvee--ggaarrbbaaggee _f_l_a_g;;
This option specifies the whether or not the client should
send TCP keepalive messages with a octet of garbage for
compatibility with older implementations. A value of 0
send TCP keepalive messages with a octet of garbage for
compatibility with older implementations. A value of 0
indicates that a garbage octet should not be sent. A value
of 1 indicates that a garbage octet should be sent.
@@ -1126,43 +1126,43 @@ dhcpd.conf(5) dhcpd.conf(5)
dhcpd.conf(5) dhcpd.conf(5)
This option specifies the name of the client's NIS (Sun
Network Information Services) domain. The domain is for-
This option specifies the name of the client's NIS (Sun
Network Information Services) domain. The domain is for-
matted as a character string consisting of characters from
the NVT ASCII character set.
ooppttiioonn nniiss--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
This option specifies a list of IP addresses indicating
NIS servers available to the client. Servers should be
This option specifies a list of IP addresses indicating
NIS servers available to the client. Servers should be
listed in order of preference.
ooppttiioonn nnttpp--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
This option specifies a list of IP addresses indicating
NTP (RFC 1035) servers available to the client. Servers
This option specifies a list of IP addresses indicating
NTP (RFC 1035) servers available to the client. Servers
should be listed in order of preference.
ooppttiioonn nneettbbiiooss--nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ...
ooppttiioonn nneettbbiiooss--nnaammee--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ...
];;
The NetBIOS name server (NBNS) option specifies a list of
The NetBIOS name server (NBNS) option specifies a list of
RFC 1001/1002 NBNS name servers listed in order of prefer-
ence.
ooppttiioonn nneettbbiiooss--dddd--sseerrvveerr _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
The NetBIOS datagram distribution server (NBDD) option
specifies a list of RFC 1001/1002 NBDD servers listed in
The NetBIOS datagram distribution server (NBDD) option
specifies a list of RFC 1001/1002 NBDD servers listed in
order of preference.
ooppttiioonn nneettbbiiooss--nnooddee--ttyyppee _u_i_n_t_8;;
The NetBIOS node type option allows NetBIOS over TCP/IP
clients which are configurable to be configured as
described in RFC 1001/1002. The value is specified as a
The NetBIOS node type option allows NetBIOS over TCP/IP
clients which are configurable to be configured as
described in RFC 1001/1002. The value is specified as a
single octet which identifies the client type. A value of
1 corresponds to a NetBIOS B-node; a value of 2 corre-
1 corresponds to a NetBIOS B-node; a value of 2 corre-
sponds to a P-node; a value of 4 corresponds to an M-node;
a value of 8 corresponds to an H-node.
@@ -1170,13 +1170,13 @@ dhcpd.conf(5) dhcpd.conf(5)
The NetBIOS scope option specifies the NetBIOS over TCP/IP
scope parameter for the client as specified in RFC
1001/1002. See RFC1001, RFC1002, and RFC1035 for charac-
1001/1002. See RFC1001, RFC1002, and RFC1035 for charac-
ter-set restrictions.
ooppttiioonn ffoonntt--sseerrvveerrss _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
This option specifies a list of X Window System Font
servers available to the client. Servers should be listed
This option specifies a list of X Window System Font
servers available to the client. Servers should be listed
in order of preference.
ooppttiioonn xx--ddiissppllaayy--mmaannaaggeerr _i_p_-_a_d_d_r_e_s_s [,, _i_p_-_a_d_d_r_e_s_s ... ];;
@@ -1192,26 +1192,26 @@ dhcpd.conf(5) dhcpd.conf(5)
dhcpd.conf(5) dhcpd.conf(5)
This option specifies a list of systems that are running
the X Window System Display Manager and are available to
the client. Addresses should be listed in order of pref-
This option specifies a list of systems that are running
the X Window System Display Manager and are available to
the client. Addresses should be listed in order of pref-
erence.
ooppttiioonn ddhhccpp--cclliieenntt--iiddeennttiiffiieerr _d_a_t_a_-_s_t_r_i_n_g;;
This option can be used to specify the a DHCP client iden-
tifier in a host declaration, so that dhcpd can find the
tifier in a host declaration, so that dhcpd can find the
host record by matching against the client identifier.
SSEEEE AALLSSOO
dhcpd.conf(5), dhcpd.leases(5), draft-ietf-dhc-
dhcpd.conf(5), dhcpd.leases(5), draft-ietf-dhc-
options-1533update-04.txt, draft-ietf-dhc-dhcp-07.txt.
AAUUTTHHOORR
ddhhccppdd((88)) was written by Ted Lemon <mellon@vix.com> under a
contract with Vixie Labs. Funding for this project was
provided by the Internet Software Corporation. Informa-
tion about the Internet Software Consortium can be found
contract with Vixie Labs. Funding for this project was
provided by the Internet Software Corporation. Informa-
tion about the Internet Software Consortium can be found
at hhttttpp::////wwwwww..iisscc..oorrgg//iisscc..