RE: Is there an easy way to monitor for Internet failures?

We have 3 internal DNS servers, for redundancy purposes.
We always use URL when possible, some 3rd party software does not allow.
Issue is when IPs change (internal or external), procedure to flush DNS cache, etc. is not always followed to the T.
Another issue is, when running multiple IPs (interfaces) on the I, and when I is the client or initiates the connection, static routes must be coded on the I.
These statics can only be IPs.

Changing IPS is never fun, nor smooth.
Too many touch points.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, November 23, 2015 1:51 PM
To: Midrange Systems Technical Discussion
Subject: Re: Is there an easy way to monitor for Internet failures?

I disagree. If your company changes ISP's, etc then all customer's have to change. Nope, no hardcoded host table entries or IP addresses. If they can't justify the time to setup DNS on their IBM i or some other box then they need to use some external DNS server.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 11/23/2015 01:28 PM
Subject: Re: Is there an easy way to monitor for Internet failures?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



On 11/23/15 8:13 AM, Bradley Stone wrote:

No application should ever use IPs (well, I'm sure there are cases, but
99.99999% shouldn't). That's one of my pet peaves and I deal with it

every

day with customers using our software. :)

Raw, hard-coded IP addresses are useful as a backup to the URL when an
application needs to be able to "phone home" from a customer box that
doesn't necessarily have DNS access or a host table entry.

And likewise, host table entries are ideal for directly accessing
internal servers that aren't directly reachable from outside, at least
in organizations that aren't big enough to warrant an internal DNS.

--
JHHL