Why would enabling reverse DNS for NATed dorm connections be a security
issue? (Just to clarify, I'm talking about the external IP address of
the gateways, not dorm computers)

Story behind it:
A while ago I was trying to connect anonymously to
ftp.gtlib.cc.gatech.edu, but I couldn't connect because it said that
reverse DNS wasn't enabled at my end (from the dorms).  I verified from
2 external locations that the address didn't resolve back to BYU (or
anywhere) and then submitted a request to OIT.  After a message telling
me they didn't support FTP, I called them back and said that the problem
was reverse DNS.  They said they purposely don't enable reverse DNS for
connections that are NATed from resnet because it is a security issue. 
However, sometimes the gateway I go through DOES have reverse DNS set
for its IP (think of the analogy to the weakest link in a chain being
the part that breaks).  I really can't figure out OIT sometimes.  Maybe
they thought I meant all computers should be given unfirewalled public
IPs (which I wish were an option for those who wanted it), but I was
quite clear in my description.

____________________
BYU Unix Users Group 
http://uug.byu.edu/ 
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to