Hmmmmm...Perhaps it has just been MISPLACED since it cannot be found.*GiGGLeS**;)
The Messenger website wasn't working yesterday either.
maybe it has contracted crabs or prehaps the annoying sounds of the courthouse drove it to running away or maybe the bush admin took it away under the patroit act or worse yet rosie odonell thought it looked tasty and ate it remember guns kill people like spoons make rosie fat!
It's a conspiracy. The libs - or is it the conservatives? - are trying to keep us from getting our daily dose of accident reports and society news. I can't believe I'm going to have to pick up a PAPER copy of the Update! FEAR!!!!
I ate at Yesterdays today and I couldn't find my server either.
Yes, yes, problems abound with WCMessenger.com's DNS... Seems to work with some DNS servers and not with others (including Spring/Embarq). In the meantime you can access the site using http://188.8.131.52/ - Hope that helps.
Adding 184.108.40.206 www.wcmessenger.comto Windows\hostsfile helps some (update archives still won't work)!
This seems to help:127.0.0.1 localhost220.127.116.11 www.wcmessenger.com18.104.22.168 www.wcmessenger.com/update/update/
The guy that works on the server at the Mess is a total moron!!!
The traceroute (for embarq)is:# Wednesday, June 13, 2007 19:33:23: TraceRoute# Generated by CyberKit [Version 3.0 beta 1 Build 06/09/2001-2] (Copyright © 1996-2001 by Luc Neijens)Host: 22.214.171.124Tasks: 5Timeout: 5 secsDelay: 500 msStart Hop: 1End Hop: 30Packets: 5Packet Size: 32Don't Fragment: NoResolve Hostnames: YesICMP Implementation: Raw SocketsMode: Normal#1 192.168.2.1 (Unavailable): TTL Exceeded in Transit, ttl=64, 4.9 ms#2 192.168.1.1 (Unavailable): TTL Exceeded in Transit, ttl=253, 3.7 ms#3 126.96.36.199 (tx-67-76-48-1.dyn.embarqhsd.net): TTL Exceeded in Transit, ttl=253, 19.8 ms#4 188.8.131.52 (tx-71-48-163-249.sta.embarqhsd.net): TTL Exceeded in Transit, ttl=251, 19.7 ms#5 184.108.40.206 (sl-gw37-fw-8-2.sprintlink.net): TTL Exceeded in Transit, ttl=249, 26.5 ms#6 220.127.116.11 (sl-bb21-fw-4-0.sprintlink.net): TTL Exceeded in Transit, ttl=250, 26.7 ms#7 18.104.22.168 (sl-crs1-fw-0-2-0-0.sprintlink.net): TTL Exceeded in Transit, ttl=249, 27.8 ms#8 22.214.171.124 (sl-st20-dal-12-0-0.sprintlink.net): TTL Exceeded in Transit, ttl=248, 26.9 ms#9 126.96.36.199 (Te-3-3.car3.Dallas1.Level3.net): TTL Exceeded in Transit, ttl=247, 28.8 ms#10 188.8.131.52 (ae-31-53.ebr1.Dallas1.Level3.net): TTL Exceeded in Transit, ttl=246, 39.9 ms#11 184.108.40.206 (ae-1-100.ebr2.Dallas1.Level3.net): TTL Exceeded in Transit, ttl=246, 28.6 ms#12 220.127.116.11 (ae-3.ebr2.LosAngeles1.Level3.net): TTL Exceeded in Transit, ttl=245, 58.9 ms#13 18.104.22.168 (ae-21-56.car1.LosAngeles1.Level3.net): TTL Exceeded in Transit, ttl=245, 59.9 ms#14 22.214.171.124 (ge1-1.cr01.lax01.mzima.net): TTL Exceeded in Transit, ttl=242, 70.7 ms#15 126.96.36.199 (xe1-0.cr01.lax02.mzima.net): TTL Exceeded in Transit, ttl=243, 63.5 ms#16 188.8.131.52 (ge2-lunarpages.cust.lax02.mzima.net): TTL Exceeded in Transit, ttl=241, 70.9 ms#17 184.108.40.206 (www.wcmessenger.com): Echo Reply, ttl=50, 59.7 msOut 18, in 17, loss 5%, times (min/avg/max) 3.7/37.5/70.9
I have a question. That tells us what?
traceroute is a computer network tool used to determine the route taken by packets across an IP network. An IPv6 variant, traceroute6, is also widely available.Perhaps Embarq has been cache poisoned(?):DNS cache poisoning is a technique that tricks a Domain Name Server (DNS server) into believing it has received authentic information when, in reality, it has not. Once the DNS server has been poisoned, the information is generally cached for a while, spreading the effect of the attack to the users of the server.Normally, an Internet-connected computer uses a DNS server provided by the computer owner's Internet Service Provider, or ISP. This DNS server generally serves the ISP's own customers only and contains a small amount of DNS information cached by previous users of the server. A poisoning attack on a single ISP DNS server can affect the users serviced directly by the compromised server or indirectly by its downstream server(s) if applicable.
Here's the word from our Embarq/Sprint representative: apparently last Friday a redback was damaged in Killeen. They've been able to get it limping along, but are waiting for new hardware to arrive this Tuesday. Until then, they are unable to update their DNS records, which points to the Messenger's new server, which just happened to change that same Friday. Hence, Sprint/Embarq can't find the Messenger. If you're having problems, you might try using http://www.opendns.com/ free servers, or just http://www.megaproxy.com/freesurf/
Oh RATS, I was hoping for a conspiracy!
Post a Comment