Prev: Everything about Red Hat Linux Certifications
Next: Serial Data
From: Doug Holtz on 27 Jan 2008 15:03
Hello Group;
I have an older DEC PPro server running Centos 4.5. I use it at home as a
DHCP/DNS/File/WEB server.
I'm getting a log file entry I don't understand:
"192.168.0.0
If this DHCP server is authoritative for that subnet, please write
"authoritative:" directive either in the subnet declaration or in some scope
that encloses the subnet declaration - for example, write it in the top of
the dhcpd.conf file."
Not being much of a dhcp guy, I don't know what to put in the conf file.
All I know is that my 3 PC's get an IP address and do their thing on the
internet.
What should I do to eliminate these log files?
TNX
Doug


From: slackerama on 29 Jan 2008 19:45
Doug Holtz wrote:
> Hello Group;
> I have an older DEC PPro server running Centos 4.5. I use it at home as a
> DHCP/DNS/File/WEB server.
> I'm getting a log file entry I don't understand:
> "192.168.0.0
> If this DHCP server is authoritative for that subnet, please write
> "authoritative:" directive either in the subnet declaration or in some scope
> that encloses the subnet declaration - for example, write it in the top of
> the dhcpd.conf file."
> Not being much of a dhcp guy, I don't know what to put in the conf file.
> All I know is that my 3 PC's get an IP address and do their thing on the
> internet.
> What should I do to eliminate these log files?
> TNX
> Doug
>
>
The authoritative statement

authoritative;

not authoritative;

The DHCP server will normally assume that the configuration
information about a given network segment is not known to be correct
and is not authoritative. This is so that if a naive user installs a
DHCP server not fully understanding how to configure it, it does not
send spurious DHCPNAK messages to clients that have obtained addresses
from a legitimate DHCP server on the network.

Network administrators setting up authoritative DHCP servers for
their networks should always write authoritative; at the top of their
configuration file to indicate that the DHCP server should send
DHCPNAK messages to misconfigured clients. If this is not done,
clients will be unable to get a correct IP address after changing
subnets until their old lease has expired, which could take quite a
long time.

Usually, writing authoritative; at the top level of the file
should be sufficient. However, if a DHCP server is to be set up so
that it is aware of some networks for which it is authoritative and
some networks for which it is not, it may be more appropriate to
declare authority on a per-network-segment basis.

Note that the most specific scope for which the concept of
authority makes any sense is the physical network segment - either a
shared-network statement or a subnet statement that is not contained
within a shared-network statement. It is not meaningful to specify
that the server is authoritative for some subnets within a shared
network, but not authoritative for others, nor is it meaningful to
specify that the server is authoritative for some host declarations
and not others.
 | 
Pages: 1
Prev: Everything about Red Hat Linux Certifications
Next: Serial Data