OK, in OIT's defense the e-mail that is sent to OIT goes to a
group of knowledgeable trained students, but sometimes lacking in
expertise.  If you want more detailed information you should ask the
student in the call center if you could get the name of the product
manager for the product that is giving you stress. (wired network
access, DNS, etc...)  
        n this case the product manager is Roger Timmerman, ext.
(2-1602) call him or send him and email (preferred) [EMAIL PROTECTED] with
your detailed question.  For something more technical than "my internet
doesn't work" this would be a good path to navigate OIT.

I have also forwarded this message to Roger Timmerman so that he is
aware of the problem. 



-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan Cox
Sent: Friday, March 05, 2004 12:41 AM
To: BYU Unix Users Group
Subject: Re: [uug] Enabling reverse DNS a security issue?

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

Reply via email to