Free Allegiance Forums

Posted: **Thu Mar 25, 2010 9:02 pm**

bad file/hostname

Posted: **Thu Mar 25, 2010 9:05 pm**

Try again? Working over here...

TB

Posted: **Thu Mar 25, 2010 9:23 pm**

# ping alleg.net
PING alleg.net (204.16.202.184) 56(84) bytes of data.
64 bytes from 204.16.202.184: icmp_seq=1 ttl=118 time=52.1 ms
64 bytes from 204.16.202.184: icmp_seq=2 ttl=118 time=43.3 ms
64 bytes from 204.16.202.184: icmp_seq=3 ttl=118 time=56.2 ms
64 bytes from 204.16.202.184: icmp_seq=4 ttl=118 time=52.8 ms
64 bytes from 204.16.202.184: icmp_seq=5 ttl=118 time=66.6 ms
64 bytes from 204.16.202.184: icmp_seq=6 ttl=118 time=60.6 ms
64 bytes from 204.16.202.184: icmp_seq=7 ttl=118 time=74.7 ms
64 bytes from 204.16.202.184: icmp_seq=8 ttl=118 time=60.3 ms
64 bytes from 204.16.202.184: icmp_seq=9 ttl=118 time=65.5 ms
64 bytes from 204.16.202.184: icmp_seq=10 ttl=118 time=60.1 ms
64 bytes from 204.16.202.184: icmp_seq=11 ttl=118 time=60.1 ms
64 bytes from 204.16.202.184: icmp_seq=12 ttl=118 time=71.6 ms
64 bytes from 204.16.202.184: icmp_seq=13 ttl=118 time=60.3 ms
64 bytes from 204.16.202.184: icmp_seq=14 ttl=118 time=61.9 ms
64 bytes from 204.16.202.184: icmp_seq=15 ttl=118 time=60.3 ms
64 bytes from 204.16.202.184: icmp_seq=17 ttl=118 time=84.4 ms
64 bytes from 204.16.202.184: icmp_seq=18 ttl=118 time=63.8 ms
64 bytes from 204.16.202.184: icmp_seq=19 ttl=118 time=63.0 ms
64 bytes from 204.16.202.184: icmp_seq=20 ttl=118 time=61.1 ms
64 bytes from 204.16.202.184: icmp_seq=21 ttl=118 time=63.0 ms
64 bytes from 204.16.202.184: icmp_seq=22 ttl=118 time=64.4 ms
64 bytes from 204.16.202.184: icmp_seq=23 ttl=118 time=63.2 ms
64 bytes from 204.16.202.184: icmp_seq=24 ttl=118 time=57.9 ms
64 bytes from 204.16.202.184: icmp_seq=25 ttl=118 time=62.3 ms
^C
--- alleg.net ping statistics ---
25 packets transmitted, 24 received, 4% packet loss, time 26301ms
rtt min/avg/max/mdev = 43.338/62.114/84.425/7.642 ms

Posted: **Thu Mar 25, 2010 9:49 pm**

Is up now, odd

Posted: **Thu Mar 25, 2010 10:40 pm**

I've reviewed the logs and don't see any loss of connectivity within 30mins of your post.
Considering that the 47 active players are still logged in, I can only assume that whatever connectivity problem you encountered was on your end and not the server's.

--TE

Posted: **Thu Mar 25, 2010 10:49 pm**

ditto: Bad Request (Invalid Hostname)

Posted: **Thu Mar 25, 2010 11:52 pm**

What is the exact URL you are trying to visit when receiving that error?

--TE

Posted: **Fri Mar 26, 2010 12:48 am**

http://www.alleg.net/

I'm also using google's DNS ( http://code.google.com/speed/public-dns/ )

Posted: **Fri Mar 26, 2010 12:50 am**

I've set my ubuntu-server BIND9 configuration to fetch from OpenDNS, working fine.

Posted: **Fri Mar 26, 2010 6:19 am**

This appears to be a DNS caching/propagation issue. The DNS entries on both of our nameservers were updated yesterday, but it seems some people are still getting the old value.

www.alleg.net should be pointing to 204.16.202.178

This problem should fix itself soon, probably by the time you wake up.

--TE

Free Allegiance Forums

Alleg.net is down