Serious problem - Cache data not expiring!

Barry Margolin barmar at genuity.net
Fri May 17 16:04:28 UTC 2002


In article <ac39ec$54r6$1 at isrv4.isc.org>,
Laurie Robert Young  <laurie at doc.ic.ac.uk> wrote:
>I run the domain angusandross.com, which at the momnet only needs to
>consist of www.angusandross.com. Up until about a month ago the http
>server and bind were both installed on 62.49.139.178 which was my ADSL
>IP address. Then my ADSL account got cancelled. Neither the httpd
>server, nor bind is now active on that IP address, and I had no time to
>prepare for the shutdown.
>
>I moved the entire site (httpd and bind) to a coloacted server run by a
>frined of mine. 195.82.119.254 (lillypad.ecclestoad.co.uk)
>
>I then sent Network Solutions an update to get them to update the whois
>database and the root servers.

Did you tell them to update the following Host record:

   Server Name: WWW.ANGUSANDROSS.COM
   IP Address: 62.49.139.178
   Registrar: NETWORK SOLUTIONS, INC.
   Whois Server: whois.networksolutions.com
   Referral URL: http://www.networksolutions.com

>However a week later I discoverd that all DNS servers were still
>pointing to 62.49.139.178 for www.angusandross.com. I did some checking
>and discovered that the root servers did not list anywhere as the
>authorative nameservers ;-(

The problem is the above glue record.  Since the GTLD servers have this
record installed, queries stop there, without going to your servers.  Tell
NSI to delete or update that record.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, 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