Our company is divided in many different ways, multiple network departments, multiple domains.
DNS currently not used 100% across the board.
One solution on the table is that our current IP would become a virtual IP.
The primary box would get a new IP and the backup box another new IP.
Everything would point to the virtual IP.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Friday, May 04, 2018 10:04 AM
To: Midrange Systems Technical Discussion
Subject: RE: Initiating a Windows DNS change from IBM i
<snip>
PC iSeries Access for Windows configurations with IP (200)
</snip>
Let the <plural derogatory term for a child of unmarried parents> suffer.
They shouldn't be using an IP address anyway.
But I can see how you'd want to address it beforehand. How you even knew
there's 200 of them interests me.
<snip>
Remote systems with IP in host tables
</snip>
Something to address for sure. The obvious solution is to use a DNS. And
you might not want the DNS to be based on the IBM server that you're
planning to bring down. Here we use multiple Windows based DNS servers.
Basically one in each major location, except I don't think we have one in
our DC in Grand Rapids despite my constant urging. The network guy
doesn't want to do it and if you disagree with him you will be badgered
until you are beaten into submission. Even though we have a robust vmware
environment at that DC and to go between systems they use an out of state
DNS server.
But in your case you need to either hunt down and replace these host table
entries with DNS calls or let the <...> suffer during the switch.
Sometimes software vendors try to do cute stuff like
a - when you type in a name they do a dns lookup for the IP address and
store that instead of the name. In their feeble minds they find IP
addresses more reliable.
b - talk a developer into doing something they shouldn't. We had one who
talked him through CFGTCP and just picking an entry off of the list of
interfaces shown. We really wondered why we were getting such database
connections through an IP address reserved for a particular Domino server,
which just happened to be the first on the list.
Here's another fun one: When your network guy sets up restrictive routing
so that particular printers and hand held scanners could only talk to one
particular subnet. I actually won that one. And since a lot of outbound
stuff from IBM i does not allow you to bind to a particular interface I
also had an issue in which he only allowed one particular IP address. He
had a tough time trying to figure out why a Domino server wanted to
connect to a label printer. I can understand that but with random picks
on outbound he just had to allow it. I have an RFE to allow more binding
to particular interfaces.
Rob Berendt
midrange.com
