On 11/23/15 1:09 PM, rob@xxxxxxxxx wrote:
Is that the hardcoded IP address as it used to be provided by your old
ISP, or the one provided by your new ISP?
Or is that the hardcoded IP address to go directly to one of your servers
or the sprayer you just now fronted that with to go to multiple servers?
It's the hardcoded IP address of whatever the relevant server is at the
time the application was last coded, and if the customer is using good
common sense, and gave the box access to a DNS when it was given access
to the outside world, it's a hardcoded IP address that the app never has
to fall back on.
And yes, the last time we changed ISPs, the handful of customers who
actually DID have to fall back on the hardcoded IP address needed to
either give their boxes access to a DNS, or create a host table entry,
or manually download an update. But better to leave them stuck out in
the cold once in a blue moon than leave them stuck out in the cold
Actually, I have a much longer host table on my Mac than I've seen on
any IBM Midrange box. There are a few entries so that I can reach all
the internal servers by name, but the lion's share of the entries are
0.0.0.0 entries to make Facebook (and a rather large number of
browser-busting ad servers) completely unreachable. (I don't do
Facebook, and I don't want some stealth link sending me there without my
knowledge or consent!)