Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!VM1.ULG.AC.BE!PIRARD
From: PIRARD@VM1.ULG.AC.BE (Andr'e PIRARD)
Newsgroups: comp.protocols.tcp-ip
Subject: dns NOT working
Message-ID: <9105180557.AA18288@ucbvax.Berkeley.EDU>
Date: 17 May 91 18:55:17 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of Liege (Belgium), SEGI (Computing Center)
Lines: 14

In the course of trying to debug why many name servers do not resolve
my 1.32.165.139.in-addr.arpa the first time they need it and do it
all right the second time and on until some cache times out something,
I started to use nslookup to perform non recursive queries.
Now, I find that the root server C.NYSER.NET 192.33.4.12 replies nothing,
not even in NS section, to the query for vm1.ulg.ac.be A that's the
authoritative server for 165.139.in-addr.arpa.
Moreover, it replies nothing for "be" SOA or NS.

What's the right door to knock at in case of such problems?

Andr'e PIRARD         SEGI, Univ. de Li`ege        139.165 IP coordinator
B26 - Sart Tilman     B-4000 Li`ege 1 (Belgium)           +32 (41) 564932
pirard@vm1.ulg.ac.be  alias PIRARD%BLIULG11.BITNET@CUNYVM.CUNY.EDU