Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.syd.connect.com.au!news.bri.connect.com.au!fjholden.OntheNet.com.au!not-for-mail From: Tony Griffiths <tonyg@OntheNet.com.au> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: A strange DNS occurrence... Date: Thu, 20 Mar 1997 11:05:39 +1000 Organization: On the Net (ISP on the Gold Coast, Australia) Lines: 25 Message-ID: <33308D63.3F74@OntheNet.com.au> References: <doug-1503971637150001@pb.injapan.net> Reply-To: tonyg@OntheNet.com.au NNTP-Posting-Host: swanee.nt.com.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0 (WinNT; I) To: Doug Lerner <doug@inJapan.net> Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37415 Doug Lerner wrote: > > However, when I tried making changes to db.domain2, even though the > changes were correctly reflected throughout our local network, using > nslookup none of the changes were visible from outside. The new records > I added were as though they did not exist, to the outside only. > > Can anybody think of a reason why this might be so? One or more DNS servers (ie. .com) have cached the old information. All you can do is wait for their cached entries to expire so that they will go back to the authoritative source (your DNS server) to pick up the latest info. The TTL field is the time (in seconds) that another DNS server will hold on to a cached entry. I don't know of any way of forcing the 'stale' entries to expire earlier! > > Thanks, in advance... > > Doug Lerner, Tokyo > doug@inJapan.net Tony