Re: Internal domain change

[Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>]

On Thu, Jun 11, 2009 at 17:14, Jeff Crosby<jlcrosby@xxxxxxxxxxxxxxxx> wrote:
> 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.

There are multiple schools of thought here, but using .local is
certainly a way that could be used. I prefer using int.example.tld my
AD deployments, but each of the choices has it's own set of drawbacks.

> 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.

Well, that depends on what third party software you run on your i, and
if you run any web servers.

In general, when you're just using legacy 5250 apps, it's easy as pie :)