how did wrong record get cached?

Barry Margolin barmar at bbnplanet.com
Tue Aug 17 13:48:55 UTC 1999


In article <37B91E63.8131DD83 at tinker.com>,
Carol Deihl  <carol at tinker.com> wrote:
>Question 1: How did some name servers cache the wrong address,
>considering that my name servers report the correct address,
>and the previous name server had a ttl of 10 minutes?

It would help if you told us the particulars, like the name that's been
cached incorrectly and the old and new nameservers.

My guess is that the name appears as a glue record somewhere.  If you dump
the cache of a nameserver with the incorrect record, it should tell you
where it learned it.

>Question 2: (Probably a dumb question, but...) Is there anything
>I can do to cause the wrong record to time out sooner?

Find the servers giving out the glue record and fix them.

>Question 3: What can I do to prevent this problem in the future?

Without knowing precisely what caused it in the first place, it's hard to
say.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list