Re: Internal domain change

"Obtain DNS server address automatically"

Since the i is the DNS server, does that not mean it will use the i to
resolve "mail.dilgardfoods.com", and the i will tell it "192.168.0.1"?

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

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, June 11, 2009 1:23 PM
To: Midrange Systems Technical Discussion
Subject: RE: Internal domain change

Those names have no meaning or use for any of your clients.  What those
names allow is that FROM YOUR i you can telnet, ping, ftp, whatever to
either of those four names and still end up at 192.168.0.1.

If your windows clients truly are using your i as their dns then you
should be able to

- do this from your client
Start, Settings, Network Connections, Local Area Network, Properties and
see how it obtains the address of the DNS.  Granted I haven't quite
grasped getting the address of your DNS automatically.

- do this from your client to check out the configuration on your server.
Start, Programs System i Access for Windows, System i Navigator, Network,
Servers, DNS and actually see something in there.  We have one lpar
serving up dns for our dmz and beyond.  The rest of our DNS' are Windows
based.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
"Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
To:
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date:
06/11/2009 12:28 PM
Subject:
RE: Internal domain change
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Thanks all of you.

I have the following 4 names in the i's host table to refer to the i (the
i
is the DNS server):

192.168.0.1    DILGARD
               I5.DILGARDFOODS.COM
               DILGARDFOODS.COM
               MAIL.DILGARDFOODS.COM

In thinking about these individually:

DILGARD
- I don't know why I have this one in there

I5.DILGARDFOODS.COM
- this is the name I use in i Access

DILGARDFOODS.COM
- I don't know why I have this one in there either

MAIL.DILGARDFOODS.COM
- The i is currently (but not for long!) our mail server, that's why I put
this in here.  But it isn't really necessary, is it?  Thunderbird and
Outlook could just as easily use "i5.dilgardfoods.com" as the incoming and
outgoing mail server as long as the i is still the mail server.


It seems to me I could get rid of at least 1, if not more, of these,
thereby
making room for i5.dilgardfoods.local.



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

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Thursday, June 11, 2009 11:29 AM
To: Midrange Systems Technical Discussion
Subject: RE: Internal domain change

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

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Thursday, June 11, 2009 11: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.

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




--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.