×
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.
Defining DNS servers is "falling off a log easy".
iNav => Network then right-click TCP/IP Config => Properties
I'd guess the compelling reason is that DNS isn't required for the "AS/400", "5250" mindset that seems to be common.
-----Original Message-----
From: Booth Martin [mailto:booth@xxxxxxxxxxxx]
Sent: Thursday, December 08, 2016 7:32 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: "3 out of 4 IBM i machines I work on do not have DNS servers specified" Why not?
Thus my question. If 3 out of 4 IBM i Series machines are not enabling their DNS, there must be a compelling reason. Is that reason reluctance, fear, and generally not understanding what the DNS feature offers a typical iSeries shop? Is it technically challenging with so little benefit as to not be worth the candle? Is it something else?
I have been looking at enabling the DNS on a development box that is on an Intranet and playing around with it. All the reading so far suggests that it is possible, confusing but not complicated, and beneficial.
None of what I have seen so far would keep 3 out of 4 shops from using the feature. In other words the words do not support the facts on the ground. So... what am I not seeing? What is the rest of the story?
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
