req: found 'cshl.org' as 'cshl.org' BUT still times out

[Dermot Paikkos]

...snip...
> Hi Dermot,
> 
> Okay the zone file for cshl.org lists only phage, so if phage is
> down bad things will happen, although phage also appears to be
> the web server(?) (for cshl.org if not www.cshl.org) and mail
> server so when it is down bad things may happen anyway.

Hi Simon,

I think the name server on phage is shutdown because you can still 
ping 143.48.1.1 and get a response. The webserver seems to be 
tuxpro.cshl.org (143.48.1.12). I get this from dig @158.43.128.72 
www.cshl.org.

> Thus the zone only has one name server as far as BIND 9 and some
> other name servers are concerned.
I am BIND 8.3 by the way. Don't know if that makes a difference.
 
> Adding an NS record for the zone pointing to Adna would mean it
> is more robust when phage is unavailable, other than not knowing
> it is a nameserver adna seems correctly configured.

I agree but I don't administer the zone. 

> Maybe you tried when phage was down but other people had cached
> data?
I think so. The SOA records I was getting show the data doesn't 
expire for 5 weeks! Problem is my name-server doesn't have any data 
for cshl.org. User's at other offices can connect to this site but users 
in my office can not. So the user's here regard it as my problem ;-(. I 
bet you can go to www.cshl.org and aims.org.au?

What I need to do is get the records for cshl that other name-server 
still hold. Problem is I don't know how. 

More confusing if I debug a query sent to my name-server for 
cshl.org I see it gets back some records come back but it doesn't 
answer the inital query. It seems to be waiting for an authoritive 
answer from phage.cshl.org.

>req: nlookup(cshl.org) id 58331 type=1 class=1
>req: found 'cshl.org' as 'cshl.org' (cname=0)
>forw: forw -> [143.48.1.20].53 ds=4 nsid=29280 id=58331 7ms 
retry 4sec
>resend(addr=1 n=0) -> [143.48.1.1].53 ds=4 nsid=29280 
id=58331 9ms

Is there any way I can grap the records for cshl.org that are currently 
on top level .org server 192.5.6.36? 

Thanx.
Dp.


 
> The only other obvious potential source of trouble is that www
> is directed via a chain of CNAME's to 143.48.220.12, when an A
> record would do it in simpler fashion. Modern resolvers should
> handle this fine, but it seems an unnecessary complication,
> unless there is some hidden magic going on in the background.
 


~~
Dermot Paikkos * dermot at sciencephoto.com
Network Administrator @ Science Photo Library
Phone: 0207 432 1100 * Fax: 0207 286 8668