host statement scope rules (ISC DHCP 3.0.5b1)

[Glenn Satchell]

Based on the number of posts to this list it appears that unfortunately
it is common practice to configure hosts entries this way. Enforcing it
in the way you propose would break a lot of configurations. Printing a
warning is a friendlier way to do this.

The type of change you propose is more suitable for a major release, eg
when it goes to 3.1.0 perhaps.

regards,
-glenn

>Date: Fri, 28 Jul 2006 19:20:25 +0200
>From: Sten Carlsen <sten at s-carlsen.dk>
>To: dhcp-users at isc.org
>Subject: Re: host statement scope rules (ISC DHCP 3.0.5b1)
>
>I was just thinking: wouldn't it be much clearer if host {} records
>could only be accepted in the global scope by syntax. I.e. the config
>file would be rejected if any host declarations were found inside any
>subnet or other places where it does not belong (by the arguments in
>this thread).
>
>David W. Hankins wrote:
>> On Fri, Jul 28, 2006 at 10:56:37AM +0200, Phil Pennock wrote:
>>   
>>> On 2006-07-27 at 15:30 -0700, David W. Hankins wrote:
>>>     
>>>> 			Changes since 3.0.4
>>>>
>>>> - A warning that host statements declared within subnet or shared-network
>>>>   scopes are actually global has been added.
>>>>