moving subnet to another server

[Dana Huggard]

The change has begun.  Slowly.  It seems to be working out okay. I don't
know yet if it will fix the original issue but at least the method of
defining a 'class' based on hostname and a 'deny' on one server, and a
'deny' on the other server works nicely.



On Thu, Jan 22, 2015 at 8:25 AM, Dana Huggard <dana.huggard at cohodata.com>
wrote:

> Thanks Niall.
>
> Absolutely.
>
> And thanks again to the others for their feedback and ideas.
>
> I am not sure yet when I will implement this change, the sooner the
> better, and I will definetly follow-up here to let everyone know of success
> and or failures.
>
>
>
> On Thu, Jan 22, 2015 at 8:22 AM, Niall O'Reilly <niall.oreilly at ucd.ie>
> wrote:
>
>> At Thu, 22 Jan 2015 10:11:50 -0500,
>> Bob Harold wrote:
>> >
>> > On Thu, Jan 22, 2015 at 6:35 AM, Simon Hobson <dhcp1 at thehobsons.co.uk>
>> > wrote:
>>
>>   [I'm sorry, I lost Simon's earlier message]
>>
>> >     Dana Huggard <dana.huggard at cohodata.com> wrote:
>> >
>> >     > subnet 10.x.x.x netmask 255.255.192.0 {
>> >     > option routers 10.x.x.x;
>> >     > option nis-servers 10.x.x.x;
>> >     > option domain-name-servers ns.sub.domain.name;
>> >     >
>> >     > pool {
>> >     > allow members of "select-hosts"
>> >     > range 10.x.x.x 10.x.x.x;
>> >     > }
>> >     > }
>>
>>   I expect you'll need a corresponding "deny" directive on the other
>>   server.  Otherwise, either a client may persist in using a
>>   previously leased address, or may pick up a lease from the "wrong"
>>   server.
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150203/895b1e91/attachment-0001.html>