Serious DNS problem making my domain unusable

[jordanr at my-deja.com]

Well, it's still not working. The namesdirect.com people apparently did
remove my domain (jrsoftware.org) from their DNS, because nslookup is
now returning a "non-authorative" answer:

> jrsoftware.org
Server:  ns1.namesdirect.com
Address:  209.40.101.7

Non-authoritative answer:
Name:    jrsoftware.org
Address:  24.4.49.97

However, my ISP's DNS (24.4.48.33) is still returning the old/wrong IP
address for jrsoftware.org (209.40.101.7), and it's been almost two
days now. How long should I wait on it to "refresh" the IP? Is there
anything I can do with nslookup or a similar tool to force it to
refresh?

Jordan Russell

In article <7sdnnc$fjd$1 at nnrp1.deja.com>,
  jordanr at my-deja.com wrote:
> Thanks for the expert advice! I would have never guessed that. The
> first time I contacted them they said they problem was with my ISP.
> I've contacted them again to see about getting the domain removed from
> their DNS...
>
> Jordan Russell
>
> In article <Vt8G3.47$854.1724 at burlma1-snr2>,
>   Barry Margolin <barmar at bbnplanet.com> wrote:
> > In article <7sb08s$gdl$1 at nnrp1.deja.com>,  <jordanr at my-deja.com>
> wrote:
> > >This may not be specifically related to bind, but...
> > >
> > >I am having the biggest problem with a domain (jrsoftware.org)
> > >registered through yournamefree.com. Even though I have changed the
> DNS
> > >servers for the domain to ns1.granitecanyon.com and
> > >ns2.granitecanyon.com with Network Solutions over a *week*
> > >ago, "nslookup" is still showing my domain as pointing to
> > >the "namesdirect.com" servers (what yournamefree.com sets them as
by
> > >default), according to my ISP's DNS servers:
> >
> > This is a well-known problem with BIND cache management, which is
> supposed
> > to be fixed in the next version.  The problem is that every time
your
> ISP's
> > server needs to look something up in the domain, it uses the NS
> records in
> > its cache to find the servers for your domain.  The cache initially
> > contained the old servers.  When that server responds, it includes
NS
> > records in the Authority Records section of the reply, and the ISP's
> server
> > updates the TTL of these records in its cache.  So as long as it
> keeps on
> > doing lookups before the NS records' TTLs expire, it will keep
> resetting
> > the timeout, and they'll never expire.
> >
> > The solution is to get the namesdirect.com people to remove the
> domain from
> > their servers.
> >
> > --
> > 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.
> >
> >
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.