I'm the exception to the rule. We live for our internal Host table
We connect to over 50 unique networks and there is no central DNS. We
use a huge NAT server. Oh, and these networks could cutover to a backup
network at any given time, which changes the IP's of all the printers
and devices for that one network. (Yes, users experience a drop out, but
they can log back in immediately) We use our host table to track the
printer IP's and our DEVD's for the printer are based off of name. We
have a job that monitors the network and if it cuts to backup, it will
change all the printer host table entries for that network to the
alternate IP using CHGTCPHTE.
On 3/12/2023 12:34 PM, Larry "DrFranken" Bolhuis wrote:
This might be the end-all to having people use hard coded IP addresses
for their IBM i servers!! This way, IBM i's IP address will change,
not often, but it WILL change at some point. Those using DNS won't know,
or care. Those using a fixed IP address won't know either, BUT they will
eventually care as they will be stuck!!
On 3/12/2023 10:45 AM, Marc Rauzier wrote:
Le 12/03/2023 à 15:17, Rob Berendt a écrit :--
When we do a switch from our system at xx.10.xx.xx to our system atJust curious: did you investigate using DNS dynamic update in
xx.27.xx.xx we have API's on our IBM i automatically update that DNS to
change the entry.
conjunction with setting up IBM i IP address as provided by a DHCP
ADDTCPIFC INTNETADR(*IP4DHCP) DHCPDYNDNS(*YES)
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
Before posting, please take a moment to review the archives
Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.