RE: TCP/IP Configuration

I don't know what else the domain name is used for. We haven't changed ours since 2008 when we set up EIM.


I'd say you're going to have to get your DNS resolved for EIM to work. My notes say that a forward lookup by short hostname and a reverse lookup by IP must both resolve to the fully-qualified name. That applies to IBMi, Active Directory and the client. Although my notes may be specific to my environment (it's been 10 years, and I don’t recall where they came from).



-----Original Message-----
From: Mark Murphy [mailto:jmarkmurphy@xxxxxxxxx]
Sent: Tuesday, February 27, 2018 8:09 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: TCP/IP Configuration

So our domains are kinda messed up. Have been for a while, not sure how it got that way, not sure how to fix them.

Our internet/mail domain is: metalexmfg.com Our Active directory domain is: exchange2.metalexmfg.com IBM i domain name: metalex.manufacturing

When we create a new user, we set the SMTP domain to metalexmfg.com (it defaults to metalex.manufacturing)

According to the redbook " Windows-based Single Signon and the EIM Framework on the IBM Eserver iSeries Server", I need to make sure that the IBM i domain name matches what is returned by nslookup. That returns nothing, likely because reverse DNS isn't set up. Not sure if that is a problem or not, but I can ping as400.exchange2.metalexmfg.com, and that is what is in our local DNS. So I think I need to change the "IBM i domain name" to exchange2.metalexmfg.com. But what is that going to break?