getting past my dialup provider's ns

Barry Margolin barmar at bbnplanet.com
Thu Oct 21 22:21:42 UTC 1999


In article <380F97E6.107D5B92 at earthlink.net>,
Scott Prince  <saprince at earthlink.net> wrote:
>I manage a couple of web servers via a dialup connection. When making
>dns changes it's easy enough to check every thing out with nslookup from
>either of the servers. But it takes up to 3 days before I can reach the
>account by name - I'm guessing this is due to my dialup's nameservers.
>It would be nice if I could find a way to access a web site right away,
>rather than using a remote server to access the site via telnet.
>Unfortunately all the sites are name based virtual hosts, running on a
>handfull of ip#'s. Any suggestions?

Are these new domains that you're registering each time?  It takes a couple
of days for the registrar (e.g. Network Solutions) to process the
registration request and add the domain to the root servers.  Until this
happens, no other servers on the Internet know how to look things up in the
new domain.

But if these are new entries in an existing domain, they should usually be
visible immediately after they're added to all the authoritative servers
for the domain, and your dialup ISP has nothing to do with this.  Negative
caching can add some delay to this, but BIND limits negative cache TTL to 3
hours by default.

-- 
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