PIRARD@VM1.ULG.AC.BE (Andr'e PIRARD) (05/18/91)
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
Piet.Beertema@MCSUN.EU.NET (05/18/91)
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. I just queried c.nyser.net for the soa and ns records for a number of other top level domains and just got "noerror", but no information. Looks like their nameserver is messed up. What's the right door to knock at in case of such problems? nyser.net. 86309 SOA nisc.nyser.net. zort.nisc.nyser.net. ( In this case zort@nisc.nyser.net, I'd say. I'm including him (her?) in the Cc. Piet