http://gentoo.org/ does not work while http://www.gentoo.org/ does. Reproducible: Always Steps to Reproduce: 1. Enter http://gentoo.org/ 2. 3. Actual Results: Page does not load Expected Results: Should redirect to http://www.gentoo.org/
It works for me. Please give us more information.
It works fine. You probably had a bad connection to one of the web nodes or the node was under load. In my opinion, not a bug. Although, one could argue that we need another node in the mix..
I'm having this problem since last night (>16 hours ago). Also, I just renewed my IP address and changed my DNS and the problem still remains. http://204.74.99.100/ gentoo@livecd ~ $ wget --timeout=60 http://gentoo.org/ --2009-10-03 20:16:44-- http://gentoo.org/ Resolving gentoo.org... 204.74.99.100 Connecting to gentoo.org|204.74.99.100|:80... failed: Connection timed out. Retrying. gentoo@livecd ~ $ ping gentoo.org PING gentoo.org (204.74.99.100) 56(84) bytes of data. ^C --- gentoo.org ping statistics --- 137 packets transmitted, 0 received, 100% packet loss, time 136326ms gentoo@livecd ~ $ traceroute gentoo.org traceroute to gentoo.org (204.74.99.100), 30 hops max, 40 byte packets 1 192.168.1.1 (192.168.1.1) 0.753 ms 1.517 ms 1.792 ms 2 200.3.60.11 (200.3.60.11) 21.920 ms 25.760 ms 27.744 ms 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
You're redirected to www.gentoo.org by a Location directive in the HTTP response header. Wget follows by default: (-S option added to show http response header): $ wget -S http://gentoo.org --2009-10-04 19:58:33-- http://gentoo.org/ Resolving gentoo.org... 204.74.99.100 Connecting to gentoo.org|204.74.99.100|:80... connected. HTTP request sent, awaiting response... HTTP/1.1 301 Moved Permanently Date: Sun, 04 Oct 2009 17:58:32 GMT Server: UltraDNS Client Redirection Server Last-Modified: Sun, 04 Oct 2009 17:58:32 GMT Accept-Ranges: none Connection: close Content-type: text/html Location: http://www.gentoo.org/ Location: http://www.gentoo.org/ [following] --2009-10-04 19:58:33-- http://www.gentoo.org/ Resolving www.gentoo.org... 209.177.148.229, 209.177.148.228 Connecting to www.gentoo.org|209.177.148.229|:80... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Date: Sun, 04 Oct 2009 17:58:32 GMT Server: Apache ETag: "36aa-4ac8dfd8" Content-Length: 46279 Last-Modified: Sun, 04 Oct 2009 17:48:08 GMT Vary: Accept-Encoding Keep-Alive: timeout=15, max=100 Connection: Keep-Alive Content-Type: text/html; charset=utf-8 Length: 46279 (45K) [text/html] Saving to: `index.html' 100%[===================================>] 46,279 31.8K/s in 1.4s 2009-10-04 19:58:36 (31.8 KB/s) - `index.html' saved [46279/46279]
Well, this still doesn't work for me from my computer at home (Argentina) and neither bugs.gentoo.org worked out this morning. If I try from a remote server in the US it works OK though. I assume bugs.gentoo.org could be unrelated. $ wget -S --timeout=20 http://gentoo.org --2009-10-04 15:08:21-- http://gentoo.org/ Resolving gentoo.org... 204.74.99.100 Connecting to gentoo.org|204.74.99.100|:80... failed: Connection timed out. Retrying. --2009-10-04 15:08:42-- (try: 2) http://gentoo.org/ Connecting to gentoo.org|204.74.99.100|:80... failed: Connection timed out. Retrying. --2009-10-04 15:09:04-- (try: 3) http://gentoo.org/ Connecting to gentoo.org|204.74.99.100|:80... failed: Connection timed out. Retrying. --2009-10-04 15:09:27-- (try: 4) http://gentoo.org/ Connecting to gentoo.org|204.74.99.100|:80... failed: Connection timed out. Retrying. --2009-10-04 15:09:51-- (try: 5) http://gentoo.org/ Connecting to gentoo.org|204.74.99.100|:80... failed: Connection timed out. Retrying. --2009-10-04 15:10:16-- (try: 6) http://gentoo.org/ Connecting to gentoo.org|204.74.99.100|:80... failed: Connection timed out. Retrying. ^C
Reopening, as the base URL uses the UltraDNS redirector, so we'd have to confirm with them.
Juan: can you please provide run a traceroute to "pdns1.ultradns.net" and include the output here.
Robin, Here you go: $ traceroute pdns1.ultradns.net traceroute to pdns1.ultradns.net (204.74.108.1), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 1.310 ms 1.817 ms 2.608 ms 2 200.3.60.11 (200.3.60.11) 23.764 ms 25.398 ms 29.370 ms 3 host89.200-117-76.telecom.net.ar (200.117.76.89) 35.456 ms 37.318 ms 41.243 ms 4 host177.200-117-126.telecom.net.ar (200.117.126.177) 43.332 ms 47.604 ms 49.189 ms 5 host162.190-225-252.telecom.net.ar (190.225.252.162) 51.253 ms 53.141 ms 55.114 ms 6 bai3-telecom-argentina-1.bai.seabone.net (195.22.220.109) 59.204 ms 26.066 ms 25.911 ms 7 ge-9-4.r02.miamfl02.us.bb.gin.ntt.net (129.250.11.241) 158.009 ms * * 8 ae-1.r20.miamfl02.us.bb.gin.ntt.net (129.250.4.161) 179.983 ms xe-2-0-0.r20.miamfl02.us.bb.gin.ntt.net (129.250.2.104) 169.938 ms 172.029 ms 9 as-2.r21.asbnva01.us.bb.gin.ntt.net (129.250.2.184) 207.894 ms 209.769 ms 213.766 ms 10 * * * 11 ge-6-7.r05.asbnva01.us.ce.gin.ntt.net (168.143.105.74) 221.656 ms 225.493 ms 227.507 ms 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
Juan, Since when has this been happening? And is it still continuing?
Shyam, I've found this last Friday, that would be 2009-10-02, and yes, this doesn't seem to be fixed yet.
This is still not fixed Regards.
Please retest. This however will shortly become irrelevant when we move away from UltraDNS.
Created attachment 256135 [details] traceroute to gentoo.org related domains traceroute to gentoo.org related domains
301 redirection works ok now from http://gentoo.org/. http://204.74.99.100/ doesn't take me to http://www.gentoo.org/. http://89.16.167.134/ doesn't show me http://www.gentoo.org/. The traceroute commands for domains gentoo.org and pdns1.ultradns.net still don't work.
Reopening as reminder to myself.
(In reply to comment #12) > Please retest. > This however will shortly become irrelevant when we move away from UltraDNS. > Now irrelevant. Closing bug.
