$ host 128.187.241.182 182.241.187.128.in-addr.arpa domain name pointer byu172550wks.rn.byu.edu.
I've never had reverse dns lookup problems, but then maybe I've been lucky. It seems silly though; it's no secret that 128.187.x.x is BYU and they can't even hope to hide that from an attacker. And as you can see above the naming scheme they choose when they do reverse dns isn't much more informative than just an IP. You might try reopening the ticket and telling them that sometimes it does work. Then you've got them cornered - if it's not supposed to work then they're incompetent because it sometimes does, and it will probably go higher in the form of a bug report if nothing else. /* Quoth Ryan Cox <[EMAIL PROTECTED]> on Fri, 5 Mar 2004 at 00:41 -0700 in <[EMAIL PROTECTED]> */ > After reading your response, I decided to post my conversations with > OIT. Here's what was submitted to IT Tracker: > > Summary E: reverse DNS doesn't work for BYU resnet IP addresses > > Problem Description: > I was unable to anonymously connect from my dorm to an ftp server > (ftp.gtlib.cc.gatech.edu) because the server requires reverse DNS > lookups to work. The outbound IP address was 128.187.247.202, and I > verifed that it doesn't resolve from two outside locations. Is there > some reason that reverse DNS isn't set up? If there isn't, it would help > if the DNS records were added. > > ----------- > > after that, I get a response that "closes" the issue with this: > Ryan: > > We do not support FTP on our network. I am sorry, but I cannot help you > with this problem. > > ----------------------------- > > then... holding back, I reopened and responded with: > > This has nothing to do with FTP. The issue is reverse DNS, which allows > IP addresses to be mapped back to domain names. The Georgia Tech FTP > server I was trying to connect to requires this reverse mapping to work > or I cannot connect. I am wondering why BYU does not map its IP > addresses back to domain names. To recreate this problem, simply FTP to > ftp.gtlib.cc.gatech.edu and log in as anonymous. Again, this has nothing > to do with ftp, but the problem manifested itself there. > > ----------------------------- > > Finally, someone called me up, asked me to post the log of the FTP > conversation, and then asked around (which is what I expect them to do) > when he wasn't quite sure what reverse DNS was. I was pleased to talk > with this guy because even though he didn't know about DNS, he at least > asked someone who did instead of saying simply "we don't support > [whatever it is that you are talking about]", and then he asked a > higher-up why reverse DNS wasn't allowed. After that I got the response: > > I was informed that reverse DNS will NOT work with the NATed IP > addresses of the ResNet halls for security measures. I called back Ryan > and told him that. > > ---------- > > But I'm still not sure if there really are any security implications > that would justify this. After all, if the server at the IP address > that is mapped to is properly configured and firewalled, then what's the > problem? They don't forward any ports or anything. > > btw, I especially liked the "He is just trying to do some crazy stuff" > quote. > > ____________________ > BYU Unix Users Group > http://uug.byu.edu/ > ___________________________________________________________________ > List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list > -- .O. Hans Fugal | De gustibus non disputandum est. ..O http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach --------------------------------------------------------------------- GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460
signature.asc
Description: Digital signature
____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
