Oh I see. I understood you incorrectly.<br><br>It is open source...<br><br clear="all">Josh Luthman<br>Office: 937-552-2340<br>Direct: 937-552-2343<br>1100 Wayne St<br>Suite 1337<br>Troy, OH 45373<br><br>"When you have eliminated the impossible, that which remains, however improbable, must be the truth."<br>
--- Sir Arthur Conan Doyle<br>
<br><br><div class="gmail_quote">On Thu, Sep 17, 2009 at 7:38 PM, David Rees <span dir="ltr"><<a href="mailto:drees76@gmail.com">drees76@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Thu, Sep 17, 2009 at 4:36 PM, Josh Luthman<br>
<<a href="mailto:josh@imaginenetworksllc.com">josh@imaginenetworksllc.com</a>> wrote:<br>
> Well if communication between the two servers was just fine on layer 3 but<br>
> it couldn't resolve, layer 7, your problem there was that the slave didn't<br>
> know what IP the master was.<br>
><br>
> You could up the TTL to 4 hours and it could have worked in that last<br>
> scenario, or 8 hours, etc.<br>
><br>
> For DNS on something like this I suggest you keep a long record, we'll say a<br>
> week. If you know you're going to change it, change the TTL for half an<br>
> hour or a full hour a week in advance of the change. Then change it to the<br>
> new IP and put the TTL back to a week.<br>
<br>
</div>Yes, that's all fine - but the DNS issue with one of the hosts the<br>
slave was monitoring prevented it from monitoring ALL hosts it was<br>
supposed to be monitoring... So if DNS for one host stops working for<br>
whatever reason, that shouldn't keep it from monitoring other hosts.<br>
<br>
-Dave<br>
</blockquote></div><br>