Cache still not expiring...

[Stephen Amadei]

On Thu, 7 Sep 2000, James Raftery wrote:

> On Thu, Sep 07, 2000 at 12:09:59PM -0400, Stephen Amadei wrote:
> > Then since his customers use my dial-up and DNS, they
> > are not seeing the DNS changes right away.  In fact, sometimes it takes
> > days...
> 
> A phenomenon called "propogation delay". Nameservers remember the
> responses they get to queries. This is called caching and it's a good
> thing (tm). People who run domains can specify in their zone file for
> each domain how long they would like nameservers around the world to
> remember responses from those zones for. This is the "time to live",
> a.k.a. the "TTL". When changing records you should lower the TTL
> beforehand so that the soon-to-be-wrong responses aren't cached for too
> long.

This is all part of the problem I have... using nslookup to check up the
domain, the SOA has a TTL of 1 day.  My server has been spitting out bogus
results for about 7 days now.  It's slightly possible that my reseller
has got a clue and changed the TTL, but I doubt it.  He doesn't have
direct control over the domain's DNS either...
 
> Your reseller is an idiot. It's not your fault he doesn't know how to
> change DNS records with a minimum of disruption and hassle. There are
> many explantory texts about how to do this. Suggest to him that he gets
> and reads the "DNS and BIND" book, gets a clue and failing that, gets
> lost. (As you may have guessed, people blaming me for their screw-ups
> really irritates me).

I absolutely agree on all points of this paragraph.  I'm just not 100%
sure my BIND is totally perfect.
 
> > usually until I rehup my named for a DNS change on my network.
> 
> To empty BIND's cache you need to restart (not reload) it.

ARGH! Sorry, I meant restart... mental typo that survived from my original
message.


					----Steve
Stephen Amadei
Dandy.net CTO
Atlantic City, NJ