In response to my question about what could cause a system to disregard
its own host table,
On 4/15/22 11:31 AM, Jack Woehr (of the Midrange List) wrote:
Which order the search happens, DNS or hosts table first, is an option in
IBM i TCP configuration. CFGTCP option 12.
Fascinating. I can't begin to imagine how setting it to "*REMOTE" could
possibly be useful (or that the OS would *allow* LOCALHOST or LOOPBACK
to be overridden), but I see that at least one other customer box has
this setting.
I will note that this, by itself, wasn't enough to kill Tomcat. It was a
combination of this, and a DNS (presumably a "house DNS" rather than a
public one) that recognized LOCALHOST and LOOPBACK, and responded with
"LOCALHOST.<domain redacted>" or "LOOPBACK.<domain redacted>," and an
address that was something other than 127.0.0.1, that did it.
--
JHHL
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
