3 Mar
2011
3 Mar
'11
10:31 a.m.
Hi Adam,
On Wed, Mar 02, 2011 at 11:08:18AM -0500, Adam Spiers wrote:
On 1 March 2011 20:20, Andy Smith
<andy(a)bitfolk.com> wrote:
Fair enough. I can't do it for 85.119.80.244 / 212.13.194.71 because
the version of Nagios currently in use can't be told to use a
specific IP address, so it just uses the main IP of the host (which
is what that IP is), and it's a multi-purpose host[1].
Additional hosts will be solely for monitoring so that problem won't
exist, and I'll retire 85.119.80.244 from monitoring then.
I've added sensible reverse DNS for the other IP ahead of time
although nobody should see anything from it yet.
Cheers,
Andy
[1] This was a massive but very old mistake from about 2005. I
learnt very soon afterwards to use service IPs not main host IPs
on any host that had a chance of becoming multi-purpose, but by
then it was too late for 212.13.194.71.
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"It is I, Simon Quinlank. The chief conductor on the bus that is called
hobby." -- Simon Quinlank
On Tue, Mar 01, 2011 at 01:42:06PM -0500, Adam
Spiers wrote:
Makes sense, although I still think it would be helpful to have
DNS entries for those IPs, e.g. monitor{1,2,3}.bitfolk.com. Are there corresponding DNS entries?
There aren't yet because I haven't actually deployed any other
monitoring nodes, and I'm not 100% sure how I'm going to do it. I
just know that we need to have more than one because:
- It's starting to get to the point where one host can't do every
check in a timely manner, and;
- If that one host is down there is no monitoring[1], which is less
than ideal
Also because at some point everything needs to renumber into
85.119.80.0/21 so might as well start with infrastructure.