{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/29/2014 11:23:05 AM
8
-
As far as I know, I'm not the only one who have got help from manually configuring the DNS-settings. I'll try to replicate the problem (Server Connection Error) by using a lower tier DNS-server as soon as I get home (2 hours). However I can guarantee this solution works, but propably this won't help all Destiny players.
-
and for Xboks one You can enter?
-
I don't have an XBOX, so can't really say. Try changing your DNS, it won't break your console.
-
I'm not going to change every DNS setting on every system I own just because of one single game. Everything worked fine so far - even Destiny till yesterday. This needs to be fixed by Bungie and certainly not by me. And it can't be the PSN - since xbox(one) users have the same problems.
-
Edited by EternalMonkeyDNS: 10/29/2014 3:05:00 PMDon't bother setting all of the DNSs on every device. For example windows can find the DNS-settings automatically. Just make a new WLAN connection (from your console) and define DNS manually [u]there only.[/u]
-
Edited by Ayu ready: 10/30/2014 9:04:06 AMThanks, but I'm not sure I can have different DNS-Settings, since I use a wired connection. I still hope Bungie is working on a solution to this. But not giving any updates (since yesterday), isn't very customer-friendly. Edit: It seems to work again for me - without doing much. ^^ BUNGIE UPDATE 11:40 AM PDT 10/29: We pushed an update last night that significantly reduced the number of MONKEY errors users were seeing. We will continue to investigate as the hit rate for this error continues to decline. Just as I had hoped for. :) THX
-
Thanks my friend. My friends said that solved this problem already
-
Nope, did nothing. Its new to me cause it slipped to Type 3 NAT but it stuck me with the marionberry code as usual. =/
