Olego2 Posted September 23, 2010 Posted September 23, 2010 Hello, I'm hosting my domain, Olego.com; and I believe I have set up the nameservers appropriately: www is a CNAME pointing to olego.com; olego.com is pointing at 216.218.192.170--the IP given to me by "Advanced DNS Zone Editor". Here's the weirdness: on Opera and IE, both http://olego.com and http://www.olego.com work. On Firefox, http://olego.com works, but http://www.olego.com is redirected to http://www.helionet.org/index/! What's weirder: in Telnet* both olego.com:80 and www.olego.com:80 give me "META HTTP-EQUIV='refresh' CONTENT='0;URL=/cgi-sys/defaultwebpage.cgi'" So here are my questions: what's going on? :-) ~Olego~ *If you want to access the page in Telnet, run "telnet olego.com 80", then when the screen clears, type "GET / HTTP/1.0", and press Enter twice.
Byron Posted September 23, 2010 Posted September 23, 2010 On Firefox, http://olego.com works, but http://www.olego.com is redirected to http://www.helionet.org/index/! Clear your cache in Firefox. What's weirder: in Telnet* both olego.com:80 and www.olego.com:80 give me "META HTTP-EQUIV='refresh' CONTENT='0;URL=/cgi-sys/defaultwebpage.cgi'" Don't know why that's happening unless it's because your domain isn't pointed to our nameservers? ----------------------------- Escalating... @djbob: Concerning this djbob. What's weirder: in Telnet* both olego.com:80 and www.olego.com:80 give me "META HTTP-EQUIV='refresh' CONTENT='0;URL=/cgi-sys/defaultwebpage.cgi'" Is this normal?
Olego2 Posted September 23, 2010 Author Posted September 23, 2010 Clear your cache in Firefox. D'oh, I didn't think that Firefox's cache would be THAT persistent. Okay, that fixed that, thanks! :-) However, the second part is still a mystery. When I telnet to olego.com:80, and GET /cgi-sys/defaultwebpage.cgi, spoofing the Referer to be http://olego.com--I get the "HelioHost Account Queued" page. I would expect that having the referer would generate a 301 Moved permanently... So how do browsers do it? ~Olego~ P.S. I'm still testing the waters with free hosting, so I'm duplicating the DNS in GoDaddy, rather than point the nameserves to HelioHost. What if HelioHost's DNS Daemon goes down, and my e-mail doesn't get through?
Ashoat Posted September 24, 2010 Posted September 24, 2010 Mail servers generally try to deliver an email multiple times before bouncing it. As for the telnet stuff: telnet uses basic TCP/IP instead of HTTP for communication. To clarify the request, HTTP includes the requested URL to the IP in its request to that IP. TCP/IP doesn't include this information; as such, it ends up just rawly requesting a page from 216.218.192.170. That's what telnet is doing, and that's why you're getting what you're getting.
Olego2 Posted September 24, 2010 Author Posted September 24, 2010 TCP/IP doesn't include this information; as such, it ends up just rawly requesting a page from 216.218.192.170. Thanks for the clarification! (About telnet and about e-mail delivery.) I tried to telnet to olego.com:80, and specifying, as one of the headers, Host: olego.com\n\n. And it worked! So now I'm not worried about DNS anymore. :-) ~Olego~
Recommended Posts