Path: utzoo!attcan!uunet!ginosko!xanth!tadguy
From: tadguy@cs.odu.edu (Tad Guy)
Newsgroups: comp.windows.x
Subject: Re: Re^2: Where is comp.sources.x archived for FTP (except uunet.uu.net)
Message-ID: <TADGUY.89Jul9113310@hathor.cs.odu.edu>
Date: 9 Jul 89 15:33:10 GMT
References: <8907061427.AA19048@ATHENA.MIT.EDU>
	<TADGUY.89Jul7230119@hathor.cs.odu.edu> <1060@unocss.UUCP>
Sender: news@cs.odu.edu
Organization: Old Dominion University, Norfolk, VA
Lines: 28
In-reply-to: fritz@unocss.UUCP's message of 8 Jul 89 12:21:46 GMT

In article <1060@unocss.UUCP> fritz@unocss.UUCP (Tim Russell) writes:
   >The message is pretty clearly saying that the problem is with your
   >domain servers.  

   That would be fine if I thought it were true, but it isn't.  I regularly
   send mail to myself to zeus.unl.edu from Carnegie-Mellon's machines with
   no problem, yet, wonder of wonders, uunet doesn't know about me.

Sending mail usually involves converting a name (such as zeus.unl.edu)
into an IP address (such as [129.93.1.10]).  However, what UUNET is
doing is converting the IP address back into a name -- completely
different operations.

A quick look using nsq (or nslookup) reveals that the primary name
server for domain UNL.EDU is RELAY.CS.NET.  However, there is *NO*
registered name server for domain 93.129.IN-ADDR.ARPA, which is where
the PTR query (used in reverse lookups) needs to succeed.  You (or
your administrator) need to arrange for a server for this domain (it
appears that RELAY.CS.NET is already setup to handle it) and notify
HOSTMASTER@SRI-NIC.ARPA when it's ready.

       Personally, I think if uunet is going to allow anonymous FTP, they
   should allow just that, and dispense with this crap about only allowing
   anonymous FTP from recognized sites.  

If it makes sites correct their name server configurations, it's worth it.

	...tad