wareid@confucius wareid $ host gentoo.org gentoo.org has address 204.126.2.42 wareid@confucius wareid $ host www.gentoo.org www.gentoo.org has address 216.110.76.37 wareid@confucius wareid $ ping gentoo.org PING gentoo.org (204.126.2.42): 56 octets data --- gentoo.org ping statistics --- 51 packets transmitted, 0 packets received, 100% packet loss wareid@confucius wareid $ ping www.gentoo.org PING www.gentoo.org (216.110.76.37): 56 octets data 64 octets from 216.110.76.37: icmp_seq=0 ttl=44 time=189.8 ms 64 octets from 216.110.76.37: icmp_seq=1 ttl=44 time=176.1 ms 64 octets from 216.110.76.37: icmp_seq=2 ttl=44 time=184.4 ms 64 octets from 216.110.76.37: icmp_seq=4 ttl=44 time=186.0 ms 64 octets from 216.110.76.37: icmp_seq=5 ttl=44 time=179.3 ms --- www.gentoo.org ping statistics --- 6 packets transmitted, 5 packets received, 16% packet loss round-trip min/avg/max = 176.1/183.1/189.8 ms wareid@confucius wareid $ It would be great if gentoo.org resolved to something besides a dead socket. It would be wonderful if the main website was brought up when http://gentoo.org is accessed. I'm not certain if this is a simple DNS issue or something more complicated, but most people complaining about Gentoo's website being down is because they accessed gentoo.org and not www.gentoo.org Thanks, Will
the only way i know is to run port 80 on gentoo.org, redirecting to www.gentoo.org
works for me
