fallingdove
Member
Can't wait to try this. My Xbone OS is slow as molasses.
Ran this last night after seeing it on r/xboxone and surprisingly my Charter DNS is the fastest.
Unsure if it's because my router is awesome, but I'm pleasantly pleased.
It's also interesting to learn that changing DNS settings is what resolves many people's issues with the OS being sluggish. I never experienced that, and now understand why.
You're missing the main point that by redirecting the request to another server further away from your ISP, you're increasing the round trip time. If your ISP is 10 miles away and Google's nearest DNS server is 1000 miles away, the quickest lookup would be to use the ISP.
Okay, so I have to download namebranch right, on the featured tab? Then run some tests?
There's a featured section there with downloads. Anyway, I'm on windows 8, so I just download this: namebench-1.3.1-Windows.exe right?What featured tab? Just go on the link I provided and download the tool and don't worry about messing around with the options.
There's a featured section there with downloads. Anyway, I'm on windows 8, so I just download this: namebench-1.3.1-Windows.exe right?
Bookmarked to test out later tonight. Thanks OP!
BTW, would this work on my Ps4 as well?Yes, that should be it.
Make sure you post your results and I'll add you to the testimonials.
BTW, would this work on my Ps4 as well?
There are variables other than location at play - server load, server performance, faulty hardware, bad configuration, others.
Charter's DNS servers went down a month or two back over the weekend and left thousands without internet service, sort of. As I found out, it was the DNS servers that were down, nothing else. I changed my DNS to Google's and it fixed the issue. Once Charter fixed the DNS servers, I switched them back. I even tweeted out the temporary fix for others and helped quite a few people with the same issue.
Your request is not forwarded from your ISP's DNS to the DNS you've selected. It's direct (routed). If it was forwarded, then you would be completely SOL if the ISP's DNS went down, which is not the case.
Maybe he meant the ISP gateway <-> DNS distance, but either way it shouldn't matter as Google most likely uses some anycast voodoo with DNS servers all over the world.
Wow. So it helped speed my xbox up a lot. I honestly did not expect it to be that helpful. Somehow my NAT is open now...
Haha thanks lolYou have been added to the testimonial section.
Haha thanks lol
Btw, I have FiOS in case anyone was wondering/keeping track
You're missing the main point that by redirecting the request to another server further away from your ISP, you're increasing the round trip time. If your ISP is 10 miles away and Google's nearest DNS server is 1000 miles away, the quickest lookup would be to use the ISP.
And that is wrong. You doubled down on it later.If you use Google's, the DNS lookup goes to your ISP anyway it'd is then forwarded to Google's DNS server.
The number one reason isps don't want you to do that is support calls. If their dns goes down, they know about it and can quickly route those affected to a voice message explaining the outage. If somebody else's dns goes down, they don't know and they end up having you take up a tech's time for something that was out of their control.
I don't know about the One but the 360 didn't cache anything in terms of dns and each one of those boxes ends up in a dns call.
Note that using DNS servers other than your ISP can mess with what CDNs you download stuff from.
I did the test and i got these results, does it mean that i've to put 62.101.93.101 as DNS?
With only 2.7% faster it's not much worth it, but yes.
Streaming wouldn't be improved by DNS
Note that using DNS servers other than your ISP can mess with what CDNs you download stuff from.