I will always do one of two things: [1] use an IP address, or
[2] have a rather complex hosts file on the server(s) running the monitoring software. After all, if DNS stops responding, are you going to stop monitoring? Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: David Lum [mailto:[email protected]] Sent: Tuesday, January 18, 2011 2:06 PM To: NT System Admin Issues Subject: DHCP reservations explained... The other day someone commented that it seemed like a bit much that 50% of my 100-ish servers have DHCP reservations - driving home yesterday I realized another reason why I have it that way (because yes, I chew on these questions and constantly evaluate why I do some process or another) - because my fellow SE's have their server monitoring set up to look at specific IP's instead of hostnames and I am unable to convince them otherwise. If the server IP changes it hoses their tests and the dependencies. It's not how I set *MY* monitoring up for servers I maintain, but I have posted that question here in fact and have seen differing opinions on weather hostname or IP is preferred. David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 503.548.5229 // (Cell) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
