The erroneous name resolution to 18.104.22.168 has been corrected. Please let us know if you can connect normally to StarCraft II, and can see and join all multiplayer options.
Sorry, the problem still exists for me.
I feel like we're going round in circles here, but I've tested everything again and nothing seems to have changed from two weeks ago.
Using my ISP's DNS (iiNet) and no host file modifications, I have these problems when using the US server:
* I get an error when I click on a game in my map history
* I get an error when downloading any new maps (e.g. custom or arcade games)
* I can play quick matches, but I think this is only because I downloaded the content before this problem started happening. Other people are getting errors here too.
As soon as I change my DNS to 22.214.171.124 (Google) or add "126.96.36.199 us.depot.battle.net" to my hosts file, the problems go away.
Using my ISP's DNS, us.depot.battle.net resolves to 188.8.131.52, which is wpc.edgecastcdn.net. Using google's DNS, us.depot.battle.net resolves to 184.108.40.206, which is site-rrc--grp-ldr--gc1.wpc.nossl.ms.na.att-acdn.net.
Using my ISP's DNS, accessing http://us.depot.battle.net:1119/000000test.txt gives me "404 - Not Found". Using Google's DNS (or after modifying my hosts file), accessing http://us.depot.battle.net:1119/000000test.txt gives me "00 Test successful."
Accessing http://220.127.116.11:1119/000000test.txt or http://18.104.22.168:1119/000000test.txt both give me "404 - Not Found".
I submitted a ticket with this information last week (except the bit about the http URLs) and got this response:
We understand that many players are frustrated by the situation and are blaming Blizzard for the DNS issue. If they are unable to use the DNS workaround hopefully the issue will be resolved on their end soon.
As a customer support representative we are unfortunately not able to discuss what caused the issue with the DNS change, simply because we have not been given that information by our server technicians.
The DNS issue is only affecting Australia, New Zealand, and Southeast Asia countries. What we have been told is that our ISP has fully investigated the issue and have determined it is not something that we will be able to resolve. However, our ISP has contacted the affected providers to notify them of what is happening. Our server technicians do want to see that this is resolved as soon as possible and will do what they can do make sure that happens.
In my opinion this is a cop out. Surely you (Blizzard) have to pay a lot of money to your network providers to provide a service such as battle.net to countries all over the world. Surely that money includes a support contract and some sort of SLA? Surely it can't be that hard to work together with your network providers to find a solution? Surely this sort of problem shouldn't still be going on two weeks after it's been reported?
Let's just hope it gets fixed before March 12th.