• Welcome to Computer Association of SIUE - Forums.
 

siue.edu != www.siue.edu

Started by Peter Motyka, 2006-08-09T01:09:25-05:00 (Wednesday)

Previous topic - Next topic

Peter Motyka

So, I noticed SIUE has some television campaigns going on (http://www.siue.edu/news/img/tvadsfinal1sm.mov, http://www.siue.edu/news/img/tvadsfinal2sm.mov) that flash a URL at the end of the short, siue.edu.

Problem is, putting siue.edu into a browser doesn't work.  Seems the siue.edu TLD points to 146.163.5.4, a host not running a web server.  I believe this should be pointing to 146.163.252.16 if the intention was navigating to siue.edu via a web browser would land you at the same place as www.siue.edu.

Somebody might want to let OIT know about this.
SIUE CS Alumni 2002
Grad Student, Regis University
Senior Engineer, Ping Identity
http://motyka.org

Bryan

For a while they had it setup correctly, seems to have fallen off again.  
Bryan Grubaugh
Quickly aging alumni with too much time on his hands
Business Systems Analyst, Scripps Networks.

R. Andrew Lamonica

I e-mailed Dan Chace about this and now it has been fixed.

http://siue.edu == http://www.siue.edu

Tyler

Still appears to not be the same here.

Belleville, Charter Cable Modem
Retired CAOS Officer/Overachiever
SIUE Alumni Class of 2005

Jerry

Worked ok from my Netzero dial-up.

However forwarded to this URL: http://oitmpu2.isg.siue.edu/

 
"Make a Little Bird House in Your Soul" - TMBG...

Bryan

still doesn't work for me in St. Louis, on charter.


Going to the page still makes me cringe though.
Bryan Grubaugh
Quickly aging alumni with too much time on his hands
Business Systems Analyst, Scripps Networks.

R. Andrew Lamonica

I think there may still be a small problem.  However, I believe that it is just a firewall one.  

In the latest DNS record siue.edu maps to 146.163.5.4 which is not the webserver (146.163.252.16).  However, from on campus 146.163.5.4's port 80 (the HTTP port) can be reached and it does an HTTP redirect to http://www.siue.edu.  This is probably what OIT wants to happen.  However, port 80 on 146.163.5.4 seems to be firewalled from off-campus computers so anyone visiting from outside of campus still gets a "cannot reach server" error.

This is probably just a firewall issue that was missed when they tested the change.  I have made this mistake so many times I finally purchased an off-site server to test from.