|
It would be a good practice to always set the name server search to *LOCAL from CHGTCPDMN. This will always hit the 400 host table first before going out to a remote name server. This could also be an issue however, if you have an entry in the host table AND one on DNS...you would need to update both locations if something changes. It is also recommended that besides making sure you specify the TCP address specifically (which I would think you have done by saying that each server has its own address) in the notes.ini file - for example: TCPIP_TcpIpAddress=0,10.23.224.170:1352 Lastly it is further recommended that you do have host table entries not only for the fully qualified name of the 400 but also the Domino servers. This avoids confusion if your remote DNS servers may not have totally updated with new info or you have a cache issue. For internal system communications, the host table is better than a remote server. In fact certain parts of MGTC may fail simply due to the fully qualified name of the 400 not being in that host table. --------------------- Kevin E. Mort iSeries Technical Support Support Net, Inc. Ph: 888.480.TECH Fx: 954.428.3991 Mailto:kmort@supnet.com IBM Certified Expert - e(logo)server iSeries 400 Technology Lotus Certified Specialist " i want everything to work. i choose iSeries. " <SNIP> --__--__-- Message: 5 Date: Thu, 29 Nov 2001 10:23:55 -0600 From: "Chris Beck" <CBeck@good-sam.com> To: <midrange-l@midrange.com> Subject: Re: Ping returning wrong address Reply-To: midrange-l@midrange.com -- Ask the Cisco kid what the TTL is. This is on the DNS. On the OS/400, you can forceably clear the cache with CHGTCPDMN. You can also disable the cache in V5R1 >>> rob@dekko.com 11/28/01 03:16PM >>> Where is this cache? On the 400 or the DNS? The Cisco kid said there was a 20 min cache. I waited longer than that. Rob Berendt ================== "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin KirkG@PacInfoSys.co m To: midrange-l@midrange.com Sent by: cc: midrange-l@midrange.com, midrange-l-admin@midrange.com midrange-l-admin@mi Fax to: drange.com Subject: Re: Ping returning wrong address 11/28/2001 02:16 PM Please respond to midrange-l Rob, I agree with Jeff. The AS/400 follows the standard when it come to How Long to cache the DNS info for an address. Windows for example ignores the time-out value and will Always do a look-up. When the DNS info is sent to a computer, along with it is a value that tells the computer how long to use its cached info for that address. The iSeries does what is told. If the data time-out is set to 5mins or indefinitely that's what it will do. Find out what the time-out is set to. --------------------------------- Kirk Goins IBM Certified AS/400 Technical Solutions Pacific Information Systems - An IBM Premier Business Partner 503-674-2985 kirkg@pacinfosys.com "WE KNOW TECHNOLOGY" --------------------------------- rob@dekko.com Sent by: midrange-l-admin@midrange.com 11/28/2001 08:35 AM Please respond to midrange-l To: midrange-l@midrange.com cc: Subject: Ping returning wrong address We have multiple IP addresses set up in our TCP/IP interfaces on this one 400. Each Domino server has it's own. Well the NT people here got cute and used one of our IP addresses for one of our Domino servers and set that up in the DNS for the 400 itself. 10.10.1.186 is for the Domino server GDSHELP. 10.10.1.123 is for the 400 GDIMAIL. But I ping GDIMAIL from elsewhere and it went to 10.10.1.186. Well, I got the Cisco kid to fix the DNS. Now when I ping GDIMAIL from my PC I get 10.10.1.123. However when I ping GDIMAIL from another 400 it still goes to 10.10.1.186. I checked the host table on the source 400 and there is no GDIMAIL, no GDSHELP and no 10.10.1.186. I checked out the address of the DNS using 12. Change TCP/IP domain information and it matches the address of the dns from my PC. So I tried adding a host table entry for 10.10.1.123 to GDIMAIL. Now when I ping GDIMAIL it works. I removed the host table entry and it goes back to 10.10.1.186. Is there some sort of cache or am I missing something? I'll probably leave the host table in for a workaround. </SNIP>
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.