DHCP 4.0.1 fails to recover from communications-interrupted after network outage
jeremiah.jinno at gmail.com
Thu Jun 5 16:18:09 UTC 2014
Thanks for the help. I may give 4.3.0 a try, but for now an upgrade to
4.2.6 did result in the correct behavior in the end.
Interestingly, I note that upon resolving back to the normal state (aka.
once they transition from communications-interrupted to normal), both
servers essentially restart their state machines? causing an additional
transition from communications-interrupted to normal... unfortunately the
fix being more important than the mechanism at this point, I have not
looked into it any further.
Thanks again for all the help.
- Jeremiah D. Jinno
On Sat, May 31, 2014 at 9:21 AM, /dev/rob0 <rob0 at gmx.co.uk> wrote:
> On Thu, May 29, 2014 at 01:35:06PM -0700, Doug Barton wrote:
> > On 05/29/2014 07:38 AM, sthaug at nethelp.no wrote:
> > >There are very significant failover problems fixed in newer
> > >versions. You want *at least* 4.1.1, newer is better. We're
> > >running 4.2.5-P1 on a failover pair here, with great results.
> > Big +1, I wouldn't even consider it on less than 4.2.
> I'm going to toss out a suggestion of 4.3.0 ... yes, .0! It was
> released quite some time ago, and is not having the kind of issues
> one might expect with a .0 release <cough>BIND 9.10.0</cough>. It
> also has a greatly enhanced feature set.
> If you're going to upgrade anyway (and in this case I agree, OP
> really should upgrade), it makes sense to go to the most recent
> stable release.
> Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
> dhcp-users mailing list
> dhcp-users at lists.isc.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dhcp-users