× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The main concern I have is email. Make sure you do not send with your
System i as .local.

You can still create an internal zone on your DC as .com and put all of
your internal IP address. This way when your internal PC's and servers
reference your external URL's, they will get the internal real IP
addresses instead of the external NAT address. If you have your
firewall locked down, you should not be able to get from inside to your
external NAT IP addresses. Then you can slowly move your clients to use
Systemi.dilgardfoods.local instead of .com



Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Thursday, June 11, 2009 8:14 AM
To: 'Midrange Systems Technical Discussion'
Subject: Internal domain change

All,

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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.