{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by NeckPUNCHattack:
3/7/2015 3:27:17 PM
116
MARIONBERRY FIX plus BANJO FIX (If you used Google DNS fix and you get Banjo, try this)
I'm making a new topic to reach out to people using the google DNS fix. Keep in mind, the google fix will not work for everyone since some people will receive banjo error codes. I've included ways to get back online, along with the google DNS method.
Okay, so you can use OpenDNS OR google in place of you current ISP's DNS to get you back on destiny if you keep receiving error codes & servers are down messages.
Go into Settings > Network > select manual DNS.
If you want Google DNS, enter 8.8.8.8 as the primary number and 8.8.4.4 as the secondary (it can be reversed and it'll work just the same).
If you want to use OpenDNS, enter 208.67.220.220. into primary and 208.67.222.222 into secondary.
Some people are now receiving BANJO errors after using the google DNS values, so I recommend the OpenDNS if you fall into that category. Once the values have been entered, your xbone, ps4, etc. will check connection after you hit B to back out to the dashboard and it'll say the connection is good.
Restart your xbone (or ps4) BEFORE trying to jump back into destiny otherwise it won't work.
Google might be a bit faster, but OpenDNS is more secure and has been around a bit longer (if that sort of thing matters to you). Hope this info helps and gets you back online Guardians!!
btw..... this is sounding like a comcast/xfinity issue, so if you can't get online and you have this ISP, you might wanna manually change your DNS to the values listed above. Good Luck!!
[b]EDIT:[/b] OpenDNS seems to be more reliable than google DNS. If it doesn't work for ya after you've entered the primary/secondary numbers, try swapping secondary for primary and primary for secondary. That seems to be able to resolve the issue in some cases. Hopefully that'll work for everyone who's still unable to get it goin.
EDIT #2: I'm glad to know that these methods have helped out a bunch of people!! Now, keep in mind that changing your DNS to one of the provided numbers is only meant to be a temp fix for when you can't get online due to these error codes & should be changed back to your original DNS settings (done by selecting automatic settings in the DNS menu) after the problems go away. This is a helpful fix to get back online in Destiny when certain cable companies experience ip/dns problems or when Bungie's servers act up with error codes, but this shouldn't be a permanent fix. Just want everyone to be aware of that.
Also, [u]please keep in mind that this won't fix everyone's problems[/u]. Some people who have been messaging me from around the world have said it works great (more so using OpenDNS), but some people will still experience the same error codes. This could be due to your location or a variety or other factors. I just want to make some people aware that this temp fix might not help everybody. Sorry, but that's just how these things work sometimes :(
-
2 RepliesI suggest for everyone to use namebench and/or dns benchmark to find the best local dns servers for their area. Once you perform a namebench test it will give you all the servers in a local area with fastest and most reliable at the top. I always use the top 2 choices as primary and secondary. I also experiment and go down the list if I don't feel like anything has changed. I used this method back when mw3 1st came out and the lag and hit detection were horrible and it helped reduce alot of the bs I was having. The Google servers I was using weren't the best for my area, some local Verizon server 110 miles away was like 24 percent faster with less errors. I'm only saying to use these sites to help find servers that are local or closer to where you are located. Having a server across the country usually makes things a bit worse due to ping time and packet loss due to the long distance traveled and back. Granted this communication is faster than the mind can comprehend and happens in hundredths and thousandths of seconds (pretty cool when you think about a signal from your computer hitting a server like 2k miles away and back in like 30 miliseconds. Not actual speed but using as an example, would probably be more like 100ms + unless on like Google fiber)
