×
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.
I agree with the .local or .corp setting for internal domains. We didn't go that route many years ago and split-brained DNS is still a pain!
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.
Why go IP instead of referring to i5.dilgardfoods.local? If it's a now vs. later issue you should be able to setup a DNS server right now that handled the .local domain until AD was online.
As for HOSTSCHPTY the advantage of *LOCAL is that you can override names on the i without changing DNS. The advantage of *REMOTE is that you don't need to remember to change the local entries when you change the remote (DNS) entries. I don't see a reason to do local overrides so I'd use *REMOTE.
-Walden
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.
midrange.com
