|
-----Original Message-----list
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, June 11, 2009 3:10 PM
To: Midrange Systems Technical Discussion
Subject: RE: Internal domain change
How do you know that the i is the DNS server?
Even if it was, it sure DOES NOT use what appears in
CFGTCP, 10. Work with TCP/IP host table entries
as the entries being served by DNS.
Think of
CFGTCP, 10. Work with TCP/IP host table entries
as the i's version of Window's xp's example of
C:\WINDOWS\system32\drivers\etc\hosts
It's only a hosts file - it's not your DNS table.
To maintain your DNS table on i pretty much requires iNav to do
Start, Programs System i Access for Windows, System i Navigator, Network,
Servers, DNS
unless you really bang out the api's.
Here's the test on your windows clients. Do this:
Start, Run, type in CMD, click Ok.
type in
nslookup nra.org
You will see
Server: gdsdns.dekko-1
Address: 10.10.4.250
Non-authoritative answer:
Name: nra.org
Address: 64.29.201.96
In our case the pc was using gdsdns.dekko-1 as it's DNS. nslookup looked
through that to discover that the ip address for nra.org was 64.29.201.96.
see also commands on the pc like
ipconfig /flushdns
ipconfig /all
ipconfig /?
And, you can use this command on your 5250 command line
nslookup 'nra.org'
and see stuff like
Server: 10.10.4.250
Address: 10.10.4.250#53
Non-authoritative answer:
Name: nra.org
Address: 64.29.201.96
Press ENTER to end terminal session.
Here, I can tell the the DNS for my i is currently 10.10.4.250. And if
you don't know the name being served by that IP address you can always
type in
nslookup '10.10.4.250'
and the return will tell you the answer.
Ok, where did my i know to use 10.10.4.250 as my DNS? This I comprehend.
CFGTCP, 12. Change TCP/IP domain information, Page down,
Domain name server:
Internet address . . . . . . . '10.10.4.250'
Internet address . . . . . . . '10.10.4.252'
Internet address . . . . . . . '10.17.4.180'
Most domains have more than one DNS. If one is down for maintenance the
others will pick up the duty. Or in our case, if your network consultant
is playing around with IP addresses again hopefully he won't change them
all at once. Notice that one dns is in a different subnet? Actually it's
in a different city.
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 02:01 PM
Subject:
RE: Internal domain change
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
"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-----server.
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
Start, Programs System i Access for Windows, System i Navigator,Network,
Servers, DNS and actually see something in there. We have one lpar(the
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
iput
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
this in here. But it isn't really necessary, is it? Thunderbird andand
Outlook could just as easily use "i5.dilgardfoods.com" as the incoming
outgoing mail server as long as the i is still the mail server.didn't
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
gonames
that route many years ago and split-brained DNS is still a pain!use
I know I've got to look at i Access at all the PCs to make sure they
vs.IP address instead of i5.dilgardfoods.com.
Why go IP instead of referring to i5.dilgardfoods.local? If it's a now
later issue you should be able to setup a DNS server right now thathandled
the .local domain until AD was online.
As for HOSTSCHPTY the advantage of *LOCAL is that you can override
on(DNS)
the i without changing DNS. The advantage of *REMOTE is that you don'tneed
to remember to change the local entries when you change the remote
*REMOTE.entries. I don't see a reason to do local overrides so I'd use
weeks,
-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
thei
tech has suggested "dilgardfoods.local" as the internal domain on theSystem
i instead of "dilgardfoods.com" as it currently is, to avoid internaland
external DNS conflicts. This makes great sense to me.
Are there hidden pitfalls to this change? I know I've got to look at
myAccess 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
listcompany. Unless I say so.list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxlist
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
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
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
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.
As an Amazon Associate we earn from qualifying purchases.
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.