In preparation for changing from a workgroup to a domain in a few weeks, the
tech has suggested "dilgardfoods.local" as the internal domain on the System
i instead of "dilgardfoods.com" as it currently is, to avoid internal and
external DNS conflicts. This makes great sense to me.
Are there hidden pitfalls to this change? I know I've got to look at i
Access at all the PCs to make sure they use IP address instead of
i5.dilgardfoods.com.
As an aside, I see the infocenter recommends the HOSTSCHPTY parm on
CHGTCPDMN be set to *REMOTE. Mine is *LOCAL. Thoughts there?
Thanks.
--
Jeff Crosby
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
As an Amazon Associate we earn from qualifying purchases.
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.