From: Ted Powell on behalf of Ted Powell
Sent: Tue 04/07/2006 15:56
To: Bernard Li
Cc: [email protected]
Subject: Re: [Oscar-devel] Issue with dhcpd.conf
On Tue, Jul 04, 2006 at 12:30:09PM -0700, Bernard Li
wrote:
> Hi Ted:
>
> Actually this was a feature request
by me since I need to have multiple
> search domains in the clients'
resolv.conf. One way to do this is to
> add multiple search domains
in the "option domain-name" entry.
You write _the_ "option domain-name"
entry, as if there were only one.
Yet there are actually N+1 such entries,
one at the outermost lexical
level:
> >
deny unknown-clients;
> > option subnet-mask
255.255.255.0;
> > option broadcast-address
192.168.150.255;
> > option domain-name
"private";
> > option routers
192.168.150.101;
> > ddns-update-style none; #
For dhpcd version 3
and another one for each and every individual
host:
> >
>
host oscar01{
> >
>
hardware ethernet 00:02:B3:18:AB:BE;
> >
>
fixed-address 192.168.0.11;
> >
>
filename "pxelinux.0";
> >
>
option routers 192.168.0.2;
> >
>
option domain-name "ocg.org ocg.org";
> >
>
next-server oscar_server;
> >
>
}
The one at the top level should suffice, unless there is some reason
why
some hosts need to receive different domain-name information from
others
in the same cluster. This is especially so, considering that
the
top-level one doesn't have the bogus repetition.
Here is a short
quote from the dhcpd.conf man page (from
FC5):
Notice that at the beginning
of the file, there’s a place for
global
parameters. These might be things like the
organization’s
domain name, the
addresses of the name servers (if they are
common
to the entire organization), and
so on. So, for
example:
option domain-name
"isc.org";
option domain-name-servers ns1.isc.org, ns2.isc.org;
Further down on that
page, it gives an example of specifying a different
domain-name for a
specific group of hosts, but there's no suggestion
that _every_ host should
have an override of the global value (not even
one that's syntactically
correct).
> We're still trying to figure out a better way to do this -
if you have
> some ideas, we're all ears :-)
The present situation
appears to be that most users will have to
patch their
head-node:/etc/dhcpd.conf whenever a new node is added,
to remove the
duplicate domain name for the new node and to remove the
duplicate domain
names that have been reintroduced for all the previously
configured
nodes.
Perhaps it would be less work over all if those users who need a
special
/etc/resolv.conf were to accomplish it by some mechanism that does
not
affect other users. For example, those users who needed to could add
an
/etc/dhclient-exit-hooks to their system image which would make
the
desired changes/additions to /etc/resolv.conf.
--
Ted
Powell <[EMAIL PROTECTED]> http://psg.com/~ted/
"If you don't look, you
don't know."
Dr. Sam Ting, Nobel laureate experimental
physicist.
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
