What is Reddit's opinion of
Google Public DNS?
From 3.5 billion Reddit comments
89 reviews of this app found across Reddit:
I had this same issue with my FiOS connection (35/35) - especially when trying to view Youtube on my iPad. I switched the iPad's DNS settings to Google's Public DNS and have had great Youtube since - I suspect Verizon's DNS sucks (or YT is optimized for Google DNS)?
DNS Servers: 8.8.8.8 and 8.8.4.4
http://code.google.com/speed/public-dns/
EDIT: fixed the 2nd DNS to 8.8.4.4
It's not, actually. That's an anycasted recursive-resolving DNS server run by Level3 for ISP customers. It's not a root server, or even a very special server (although very memorable!)
Since it has a memorable address, people tend to use it as a DNS server, but third-party use has never been officially authorized. You should use google's servers instead where possible (8.8.8.8, 8.8.4.4) as they actually authorize the use.
FWIW, the root servers are:
- a.root-servers.net: IPv4 198.41.0.4 IPv6 2001:503:ba3e::2:30
- b.root-servers.net: IPv4 192.228.79.201
- c.root-servers.net: IPv4 192.33.4.12
- d.root-servers.net: IPv4 128.8.10.90 IPv6 2001:500:2d::d
- e.root-servers.net: IPv4 192.203.230.10
- f.root-servers.net: IPv4 192.5.5.241 IPv6 2001:500:2f::f
- g.root-servers.net: IPv4 192.112.36.4
- h.root-servers.net: IPv4 128.63.2.53 IPv6 2001:500:1::803f:235
- i.root-servers.net: IPv4 192.36.148.17 IPv6 2001:7fe::53
- j.root-servers.net: IPv4 192.58.128.30 IPv6 2001:503:c27::2:30
- k.root-servers.net: IPv4 193.0.14.129 IPv6 2001:7fd::1
- l.root-servers.net: IPv4 199.7.83.42 IPv6 2001:500:3::42
- m.root-servers.net: IPv4 202.12.27.33 IPv6 2001:dc3::35
Note that these cannot be used in the 'DNS servers' configuration pane for ordinary clients (they do not perform recursive resolving).
Hey guys, it's really easy to solve! You need to switch your DNS servers to google's DNS and the YouTube videos load EXTREMELY fast even on a 2mb connection! Link here!
It's not down.
It's your DNS failing to update after minecraft.net changed server. You can either wait a few days or use OpenDNS, dyndns or even simpler Google DNS as temporary DNS servers to get you back online.
Edit: or try typing
ipconfig /flushdns
into command prompt on a PC and see if that works.
First question: http://www.howstuffworks.com/dns.htm
Second question: http://code.google.com/speed/public-dns/docs/using.html#setup
Scroll down a little on the second link and there are instructions on how to configure your pc/mac.
TPB er ikke blokeret som sådan, danske DNS-servere henviser bare til stopsiden i stedet. Skift til en alternativ DNS, fx Google DNS eller OpenDNS og der er fri adgang, i hvert fald fra alle ISPer jeg har testet.
Just so you know, your redirect to Comcast (or any other provider-branded 404) is due to their tomfoolery with your DNS.
If you don't mind what's going on, ignore the rest of this, but if you don't like being forced onto a site you didn't want I suggest changing your DNS to something like Google's DNS or Verizon's (which range from 4.2.2.1 to 4.2.2.6).
Sounds like a DNS issue. Maybe switch your DNS settings from Time-Warner's DNS to Google DNS? [edit] That's what I use and it pretty much eliminates any blind spots like you describe. You can make the switch temporarily and see if it makes a difference, if you are averse to letting Google be your DNS provider.
It only appeared to be down. They were switching to movies.netflix.com for some reason, and those of you without quick DNS providers got left in the dust until the information propogated.
I have been using these DNS servers for quite a while. Last night's fiasco still hit me. Fortunately we'd already killed almost all of the sleepers in the wave and logis were apparently not on Comcast so we survived the ordeal.
Google provides a public DNS as a free service. That still didn't help last night as it was not a DNS related issue. Some router somewhere choked and died or someone rebooted it without a backup that could handle the traffic.
Just hard-code your own DNS addresses:
You can use OpenDNS: 208.67.222.222 208.67.220.220 Instructions - btw, you don't have to sign up for the free account or any account, just configure your PC to use the OpenDNS servers.
Or Google DNS: 8.8.8.8 8.8.4.4
Maybe it's time to create an alternate DNS resolving service that acts like Google Public DNS (http://code.google.com/speed/public-dns/). Domain owners can register into the service (free or donation based) and after validation can freeze their DNS records. So if a domain is seized the site is still accessible if people are using these servers as resolvers. This could give enough time for sites to rename and renumber their assets and relaunch. If a domain isn't registered through the service no caching is setup and the request just passes through to the root name servers.
Even if a site didn't register for the service it could be possible to force old records after seizure. And this would be a lot easier to do than setting up an alternate naming system that is more open and less prone to a single government action taking things down. The creation and adoption could take years for a new and more secure system to take hold. This could be setup and launched is a much quicker fashion and not force people out of the normal domain registration paradigm.
My only problem is I couldn't do it.. US citizen.. It would still be subject to seizure if I were to build the system :(
This is an OpenDNS "feature".
You have a few options: 1) Disable OpenDNS, and use an alternative --google's DNS maybe? http://code.google.com/speed/public-dns/
2) Register an OpenDNS account (if you haven't got one), and go to Dashboard -> Settings -> Advanced Settings and uncheck "Enable typo correction"
3) Set up a local dns server running dnsmasq to intercept and return proper NXDOMAINS (advanced, possibly tricky)
4) Get somebody to write a firefox addon to do 3 :P
It could simply be a DNS or cache issue.
Try changing to Google's DNS and see if it improves.
To refresh the cache, you can either clear it entirely or do a hard refresh of the webpage (CTRL+F5).
Good job on diagnosing this far. The problem is definitely your computer somewhere along the line.
The first thing you should do is set your DNS servers to OpenDNS. Here's a guide. If that doesn't work, try Google's DNS instead.
Let's take a look at your hosts file while you're here too. This will show you how to open it. Copy whatever's there to here and do not make any changes.
As everyone has already mentioned, have you considered Opera Turbo? It makes pages you visit redirect through a fast proxy that first compresses the page content before sending it to you, speeding up page loads on slower connections.
You can also enable "Enable plug-ins only on demand" in Settings > Preferences > Advanced > Content, that way you won't have to worry about loading background data for things like videos on page loads until you want to watch it...
And you can also use FanBoy's AdBlock list to stop your browser from downloading ads on many a webpage. It also cleans up your view. :)
Lastly, you can use a different DNS server if your ISP's is slow, you can get information about using Google's DNS, which tends to be one of the faster DNS servers around here.
I hope this helps..!
It may be an issue with the DNS servers that your ISP is using. In this case the server is not able to resolve the host address for the domain you are trying to access. There are many free DNS services you can use to bypass this.
First I would check by using a proxy like http://hidemyass.com to see if you can connect when proxies. If you are able to get through while connected through proxy then you may want to change your DNS. Google Public DNS is free and has configuration instructions if you would like to try this.
Since you mentioned IE I'm assuming your'e on Windows. You can try flushing your current DNS cache (the stuff that your computer remembers about domain names) by opening a command prompt (start->run) and typing "ipconfig /flushdns".
All of this is operating under the assumption that you have cleared your internet cache and still can't get through.
You can change your computer's DNS to use Google's servers or something like Norton DNS or Comodo SecureDNS.
Worth a shot.
Google runs their own DNS servers. What kind of security issues are you asking about? Whether OpenDNS or Google, your sites can be logged.
>8.8.8.8
>8.8.4.4
You're clearly experiencing a DNS or name resolution issue--assuming you are in fact connected to the internet. Ignore the browser for a moment and try to ping an IP that Facebook should resolve to, try 69.63.189.16
What DNS servers are you using? You could try the ones that Level3 operates (4.2.2.1, 4.2.2.2, etc) or even Google's (8.8.4.4, 8.8.8.8)
Have you tried more than one browser? Do they all take you to the same place? I'd check your /etc/hosts file. If it isn't that, you could be bouncing off a poisoned DNS cache. Try setting the DNS on your router to Google's DNS servers and see if that helps. Good luck.
Their IP changed due to switching to a different host or something. You either need to clear your DNS cache or if your ISP is still caching the old address, switch to a DNS provider that updates more frequently (like Google).
If it's only affecting the app store, then it's either packet loss somewhere between you and Apple's servers, or DNS failures.
Try switching to Google DNS. This fixes a lot of peoples' problems since many ISPs have horrible DNS. If it's packet loss (there's ways to test this) you can call your ISP and complain, but if it's happening outside their network they can't do anything about it.
Try changing your DNS server from your ISP's to Google's DNS server. http://code.google.com/speed/public-dns/docs/using.html Try it on one computer first and if it works change your router settings to use it so it will work on all computers. It doesn't hurt to use it and is actually quicker then most ISP's so you might as well leave it even if it doesn't fix your problem. If that doesn't work, next time a website doesn't work right, open command promt and type in "tracert [website url]" ex: tracert youtube.com and post results here.
You could try changing the DNS servers. DNS lookup tends to be the slowest part of your overall bandwidth. Check out this page at Google in regards to their public dns service. It should explain how to change this on your computer. It could very well speed up loading times.
Wow. You've done damned near everything I can think of. Is your Apple ID and primary email address verified on the Apple ID site?
This next suggestion is silly considering you have an 18Mbps connection, but does switching your DNS servers to Google's make any difference?
What OS are you using?
Google has instructions for Windows7 and Linux on how to change your dns settings to use their servers.
Have you checked your hosts file? Make sure there are no funny entries for SoulBounce.com. Also you can try pinging these websites to see if dns is resolving an IP for them at all.
When I ping soulbounce.com it resolves to 67.23.250.31, if your computer cannot resolve it or ends up with a much different number then you may have a DNS problem.
If you need help with checking your hosts file or with pinging a domain, let me know.
Hacé lo que dice recor. DNS alternativo (Google 8.8.8.8, alternativo 8.8.4.4)
There were some cases where using a non-ISP-provided DNS would lead to CDNs routing your requests to a far-away server, slowing down things like Netflix streaming. Google has an FAQ about this, and it looks like they've deployed distributed DNS servers to mitigate this issue.
In any case, RCN is cool and they will turn off the DNS hijacking for you if you ask.
It sounds like its not your laptop. It's christmas day so there is probably 1000% more traffic than your ISP usually deals with. All internet traffic on your connection may be suffering.
Also Mojang's auth servers are cloud based with Amazon. The servers that you may be connecting to could be over loaded for the same reasons that your ISP may be over loaded.
It's a long shot, but you could try configuring Google Public DNS.
While I personally don't care too much about the whole "data mining" thing, here is Google's website that lists everything.
Other comparisons are drawn between OpenDNS and Google DNS here and here.
Makes me think it might have to do with DNS, then, and not your actual network connection. If you're using a router (sounds like you are), try either Google DNS or OpenDNS.
You could also try pinging (with the command above) 74.125.47.147
This is one of Google's many IPs. If you get a response from the IP, then the problem is definitely with DNS.
You might try running this test. It might be able to tell you if Time-Warner is affecting your connection.
I don't know if that will give you any useful info.
Also, I'd try setting the DNS servers on your router to the Google DNS servers 8.8.8.8 and 8.8.4.4 and see if that helps at all. You can also set these manually in your network connections if you don't want to fool with the router. http://code.google.com/speed/public-dns/
What is the exact error when you are getting the failed update when connected via internet?
One thing that could cause it is DNS problems, try change the DNS server under network setting to googles
Out of curiosity, have you tried using something like Google DNS? If it's an 'initial connection' issue it could be either shoddy DNS service from your ISP or that the router isn't handing off the information properly.
More information on how to set that up HERE
So, to answer your question, you could technically stockpile IP addresses to sites you need access to. Just hope that the IP addresses are static, most large sites are.
Otherwise, you can look into alternate DNS resolution, such as Google's public DNS:
Try changing the DNS settings on your computer. For instance, use Google's DNS: http://code.google.com/speed/public-dns/ If it goes away, you can switch your router to use Google's DNS or Open DNS. (Note that this has its own problems, for instance with content delivery networks, because they use your location to find the closest server to you.)
Open a command prompt (Start > Search all programs and files > cmd , Hit Enter).
In command prompt, type "ping twitter.com" (no quotes).
It should return an output that looks like this:
Pinging twitter.com [199.59.149.230] with 32 bytes of data: Reply from 199.59.149.230: bytes=32 time=20ms TTL=251 Reply from 199.59.149.230: bytes=32 time=20ms TTL=251 Reply from 199.59.149.230: bytes=32 time=20ms TTL=251 Reply from 199.59.149.230: bytes=32 time=20ms TTL=251
Ping statistics for 199.59.149.230: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 20ms, Average = 20ms
If it doesn't, try "ping 199.59.149.230". If that returns a response, then there's something wrong with your DNS server.
Try switching to Google DNS.
If it does return a response, open your browser and navigate to Twitter.com, like you usually would.
Once it tries to load and reports back that the connection has timed out, hold CTRL and hit F5. This will perform a hard refresh, essentially clearing anything in the cache related to Twitter.com
Still having issues?
If you're on Chrome, try opening your options and on the "Under the hood" tab, click Change proxy settings. In the window that pops up, click LAN Settings and make sure nothing in that window is enabled and that there are no entries under "Address".
If you're on Firefox, you can still check your proxy settings, but I doubt they'd be affected in a similar fashion.
If a proxy address is found, you may have been compromised by spyware.
Finally, run Spybot S&D, make sure Microsoft Security Essentials is installed, and try changing browsers.
3 ideas for culprits:
If the router is shitty, any significant P2P traffic will knock it out. This means bittorrent and any similar app. If this is the case, then you need a router that doesn't suck. I recommend the linksys WRT54GL flashed with OpenWRT.
Ive seen some routers that can't stand up to you using the Microwave to cook food while its going. Load webpage, works great. Start toasting a bagel, not a single thing loads. Bagel finished, web works again. If this is the case, time to invest in a new wireless access point supporting wireless G or N.
Your ISP's DNS server may suck. This happened alot to me with comcast. Use google's DNS (http://code.google.com/speed/public-dns/).
It may be your ISP's DNS server. I recommend trying out Google DNS or OpenDNS. Both Websites have walk-throughs on how to change it (very simple).
http://code.google.com/speed/public-dns/ http://www.opendns.com/
This may not be the issue, but you could try different DNS servers like Google Public DNS.
But I have issues very similar to yours and they're simply due to my ISP being teh suck. And I live next door to them..
And any IP level block is almost certainly going to be implemented by modifying DNS. Which is also trivial to circumvent. Google will even walk you through the process here.
You can opt out here: http://nxr.shaw.ca/
I use Google DNS because it's much faster. As a bonus, when Shaw's DNS servers go down, I still get internet :)
Have you tried statically setting the DNS servers to google's ( 8.8.8.8 and 8.8.4.4 )?
It sounds like this is the only computer from the network that isn't permanently attached, so my guess is you're looking for content on a CDN, when your computer uses the DNS cached from earlier, you end up in the wrong place.
There's also ipconfig /flushdns and arp -d which may help.
Some ideas:
ipconfig /flushdns in command prompt.
Reset your router if you have one.
change your DNS server in internet connection properties from DHCP aquired to 8.8.8.8 (Google public DNS)
ultimately, just wait.
but it should work if you try those steps out.
Ok, so you're setup correctly.
oh... wow that's hilarious. I just read up on openDNS, and yeah this is because your building uses a bone-headed IT setup. Looks like your entire building is running NAT over probably one IP Address, and thus you change the opendns settings for that IP, and BOOM everyone in the building must bend over and take it.
Use google's free DNS offering. http://code.google.com/speed/public-dns/ or lookup any other free DNS Service.
I suggest also writing a letter to the management company that owns your buidling detailing in MORON-LEVEL language what this entails. Be sure to write as much like a lawyer as you can when you do this, but do not make any legal threats :).
If you're using a non-ISP DNS server like open DNS or google you may have problems with streaming since your ISP will route you to the closest content distribution node and the public servers will more likely than not, give you a distribution node that's not optimal.
Even if it's not a DNS issue, Comcast may not be entirely at fault. MLB or their content distribution network may be cheeping out by not having a node near you, forcing the stream to go longer routes on the busy internet backbones.
If you can stream netflix or another service in HD during prime time but not MLB then it's MLB's fault. If you can't stream HD during prime time then it's either a DNS issue or Comcast sucks.
My ISP probably already logs the shit out of me, so I'm not really worried about someone subpoenaing Google to get my information when they'd have an easier time breaking Windstream's arm. I'm also not really worried about Google using my information, because I've used Gmail, Google Voice, Picasa, without anything happening to that much more important information.
Please post your operating system and browser. If you're on Windows, a possible [](/solution) is to cleanup your hosts file.
Another option would be to try another DNS, maybe Google's public DNS server.
Your ISP has set the DNS servers that it sent your router, which in turn sends them to you when you do a DHCP request upon boot. But the DNS server is clearly messed up (or is being deliberately filtered by the ISP). Change your DNS servers to Google's public DNS servers, and it will fix this problem. Here's the instructions to change them. http://code.google.com/speed/public-dns/docs/using.html
I don't believe that is correct. Google's Public DNS IPs don't direct you to a "central" DNS server, otherwise you'd be getting unacceptable latency (for DNS's) from anywhere more than a timezone away.
From Google's public DNS FAQ:
> How does Google Public DNS know which data center to send me to? Google Public DNS uses anycast routing to direct all packets to the closest DNS server. For more information on anycast routing, see the Wikipedia entry.
Above that question is a list of all of their nameservers and the closest airport: http://code.google.com/speed/public-dns/faq.html#locations
I think what happens it that some ISP's DNS are poorly distributed or poorly implemented and CDNs end up resolving a huge number of customers to the same node, while Google's datacenters are usually less frequently used, and CDNs resolve Google DNS users to a mostly unused node that might be a little farther away. Google talks about the issue here: http://code.google.com/speed/public-dns/faq.html#cdn They even proposed an upgrade to the protocol that allows the node selection to be based on the original user's IP instead of the DNS resolver IP.
Regardless of the technical details, the above solution has fixed the problem for a good proportion my friends that I'm inclined to recommend it whenever I see it.
Someone would've specifically added 8.8.8.8 and 8.8.4.4 to the DNS tab of the Advanced settings of your network interface in System Preferences, or added it to your router's DNS settings.
If no one else changes/administers your network, and you haven't done this yourself, you're probably not using Google DNS servers.
Try this fix, google dns, Just upgraded my internet and youtube was still slow as shit, saw this in another thread complaining about youtube buffering slowly, since I changed that youtube loads like I shoved a jalapeno up its ass.
Also eh ads, I've never seen those. (Adblock plus, my isp has a cap on internet, why pay to stream 1mb+ of bullshit ads per page?)
No it doesn't. Only if there were significant interference and according to him, downloads are good, so there is none of that.
The problem is somewhere else. Maybe it's a slow DNS server. OP could try Google's DNS servers and see if that makes a difference.
Check your hosts file to see if there are any entries in there that might be causing this. http://malektips.com/spyware_adware_0017.html
Or try changing the DNS address. http://code.google.com/speed/public-dns/
Try this
http://euw.leagueoflegends.com/board/showthread.php?p=40257#post40257
Edit since the link in that post to public dns guide isn't working, you could try with Google Public DNS http://code.google.com/speed/public-dns/
Could be corrupt dns settings.
Use: http://www.corenetworkz.com/2009/08/how-to-enter-dns-settings-in-linksys.html
to find where the settings go and use either opendns or google Dns settings.
http://www.opendns.com/ http://code.google.com/speed/public-dns/
In Chrome can you access it by the IP rather than the domain name? Try http://63.228.223.104 and if that loads it is probably a DNS issue. I would go into your router config and point to different DNS servers, such as Google's public DNS.
Also, standard router troubleshooting applies:
- If possibly, bypass your router to see if the page loads. This will tell you for certain if it is the router or your ISP that is causing the issue.
- Reboot the router (unplug power for 10 seconds) and try again.
- Reset router to factory settings (will lose all configuration.. port forwarding, etc) and try again.
- Upgrade router to latest firmware and try again.
I used to get 404's on sites I KNEW were valid (and legal) but then I started using Google's DNS. If you don't like/trust Google, Open DNS works great.
Let's take DNS out of the equation for a moment. Open up a command prompt (cmd.exe), and type "ping 8.8.8.8". If you get a reply your internet connect works just not DNS. If this is the case, set you DNS server to 8.8.8.8 and 8.8.4.4 . If this doesn't work, type " tracert 8.8.8.8 ", and tell us what it reports.
Censurfridns.dk has an excellent censorship-free DNS for any fellow Danes (or other people in the neighborhood)
Opendns and Google also offer censorship-free DNS services (but they won't if SOPA passes)
Is it just me or wouldn't everyone just start connecting to DNS servers outside of the country? Problem solved?
I used to use Google Public DNS for a long time because my ISP's was shit.
Google hosts a DNS which is better than OpenDNS (though it has no 'features') in terms of performance.
The fastest DNS I've found is Level3, however you are not supposed to use it unless you are a customer. (Not stopping me.)
Google: 8.8.8.8 and 8.8.4.4
Level 3: 4.2.2.1 - 4.2.2.5 (Pick 2 or 3.)
You may have already tried this, but you could use a different DNS...Google has one. Also, use an ethernet connection if you can; I always had issues with the wifi.
Here are the google dns ip addreses;
Google Public DNS IP addresses (IPv4)
8.8.8.8
8.8.4.4
You can find instructions for changing the dns settings in OS X midway down on this page. You will want to follow the wireless (airport) settings instructions.
http://code.google.com/speed/public-dns/docs/using.html
You could just leave these settings on the google settings after you are done or you can just change them for testing purposes and remove the settings afterwards.
You can try one of two things:
Set the DNS servers manually on your router to Google DNS, or just set the DNS servers on your computer manually. If it's actually a problem with the DNS servers, this might fix the issue.
http://code.google.com/speed/public-dns/
Out of curiosity, is there a reason you switch your router off? Power/security issues?
Your computer can't recognize i.imgur.com, which means there's a DNS problem somewhere. You could try restarting your router, and if that doesn't work then try changing your DNS settings to either Google Public DNS or OpenDNS.
I had the same problem, step three alone fixed it for me:
Ok, I HAVE A SOLUTION TO THIS. (any ISP's who use deep packet inspection or hijack dns request's will have this issue, this solution should work for you aswell, the opt out option will most likely be else where though.)
One, Switch to google dns (both ipv4 and ipv6) http://code.google.com/speed/public-dns/ (this part is probably optional, i haven't tried it without it.)
Two, browse to http://assist.mediacomcable.com/mediacomassist_pnf.../motd.dm.origin.com/en_US.html or just put in a website that doesn't exist.
Three, On the bottom right you will see a message that states "OPT OUT OF THIS SERVICE" Open the link and change the first option to disabled and then save it.
Four, Open origin, you should only be prompted for login but if the page continues to appear, clear your cache for internet explorer, and delete "c:\users\%user%\app data\local\origin\webcache" (fire fox cache shouldn't matter.)
Are you getting an ISP redirect page when you try to start-up Origin? I had that problem with Mediacom and you can actually edit how your ISP intercepts pages by scrolling the redirect page until you find the settings down in the lower right.
It might be something else though, not sure what you're seeing.
Edit: Additional info
Ok, I HAVE A SOLUTION TO THIS. (any ISP's who use deep packet inspection or hijack dns request's will have this issue, this solution should work for you aswell, the opt out option will most likely be else where though.)
One, Switch to google dns (both ipv4 and ipv6) http://code.google.com/speed/public-dns/ (this part is probably optional, i haven't tried it without it.)
Two, browse to http://assist.mediacomcable.com/mediacomassist_pnf.../motd.dm.origin.com/en_US.html or just put in a website that doesn't exist.
Three, On the bottom right you will see a message that states "OPT OUT OF THIS SERVICE" Open the link and change the first option to disabled and then save it.
Four, Open origin, you should only be prompted for login but if the page continues to appear, clear your cache for internet explorer, and delete "c:\users\%user%\app data\local\origin\webcache" (fire fox cache shouldn't matter.)
I'm assuming you're using Windows. To quickly flush your DNS cache run the following (Win+R):
cmd /k ipconfig /flushdns
This will clear out all existing DNS entries in your cache, forcing your computer to rebuild them.
If you keep having DNS problems, you can set up your computer to force it to use Google Public DNS to resolve your URLs.
Well, if it's really a DNS problem, then change the servers you are using on the router (or your PC) to Google's servers: http://code.google.com/speed/public-dns/docs/using.html
Comast's and Verizon's activation pages also come up when you reset the router because it loses the login info for DSL/Cable.
Thats strange, check your DNS settings:
change the dns and use these settings
Are you seperated by a router? plug your computer right into the modem, and try
Make sure you run a virus scan
I had this problem last night.
RADS error, something about the HTTP connection (I don't remember the exact phrasing).
Here's how I fixed it:
1) Do not run the repair tool (as some LoL forum posts indicated), it will cause you to redownload most of the patches.
2) Change your network connection settings to use google's public DNS server instead of your ISP's.
How to switch to Google DNS. Since this worked for me, it's likely that some ISPs have bad DNS entries for the LoL servers for some reason (LoL switched IPs without updating public DNS entries, blah blah I forget the network details exactly... something like that). For the record, my ISP is Broadstripe.
Hope this helps.
Edit: Didn't see you guys were EU. Not sure if this is the issue in that case :/. May be worth a try anyway, just write down your old settings in case it doesn't work.
Couldn't say. Presumably they use different name servers which give them different replies for some obscure reason.
In Unix you can use host and dig to poke at the name servers directly from the command line to get more details. The configured name servers are in /etc/resolv.conf (not sure where you see it in Windows, by getting something's properties I suppose). You'll see the DNS traffic in Wireshark too of course.
Also Google has a public DNS which you can use if you don't trust the one(s) you've got.
Oh, you might want to try to use the Google Public DNS servers 8.8.8.8 and 8.8.4.4. That will let you see if they are using DNS to jack your connection. If you really want to know what they're doing, download wireshark, take a capture of you attempting to access a blocked site and post the results here. That should make things pretty clear.
Try changing your DNS provider. DNS must be resolved before every internet request, so if you're hitting your wireless router for this (DNS relay) it might slow things down, and it is even possible that your ISP DNS sucks too.
OpenDNS or you like Google you can use their name servers.
Or it could be something totally different that has gone wrong, but this is pretty easy to try.
Well, you could always turn off "Check for SSL certificate revocation".
Other than that, try a clean reinstall of Firefox.
Test other browsers. If it happens in Chrome, you may want to switch DNS servers: http://code.google.com/speed/public-dns/
DNS is the service that translates the human readable URL to machine readable IP address. Typically, this is provided by your ISP, some sometimes their default service just sucks. Try Google's alternative.
Yeah... well. I'm not seeing anything useful. The best I can do is offer some suggestions for debugging:
On the router (these settings are modified through the router's admin panel by visiting 192.168.0.1 or 192.168.1.1):
- Switch the security protocol (using WPA2 was known to cause problems on Snow Leopard; I experienced this myself)
- Make sure the router's firmware is updated
- Check the router's network settings: if it is broadcasting Wireless-N only or mixed in the 2.4Ghz band, try dropping it to G.
- Turn off frame burst if it is enabled
- Ensure that the router is broadcasting on an uncluttered channel (check your local WiFi traffic first)
- Verify that no other machines using the same connection have the same behavior. If they do, it may indicate a problem with the router. As routers age -- sometimes quickly due to heat buildup -- they tend to act wonky.
On your machine:
- Try turning off IPv6. See your network preferences.
- Check your DNS server settings. If some web sites are causing the trouble but not others, that may be a DNS issue. Try using different DNS servers: you can try using Google's public DNS servers
- Try flushing your DNS cache: open Terminal and type: "sudo dscacheutil -flushcache" (without the quotes).
- Keep an eye on your logs (from Console) to look for any unusual network behavior. If you find something odd, Google it.
Good luck.
What browser do you use?
If Firefox, try Chrome. Or, vice-versa.
Also, try power-cycling your modem (unplug, wait 10 seconds, plug back in).
Your ISP might also be to blame. You can try Google's DNS and see if browsing improves.
It could be the memory on your PC. How much do you have? What are you running? XP or Windows 7?
Another thing you can try is changing the DNS servers. Roadrunner's is horrible. You can change it in your router or your browser.
Use OpenDNS:
208.67.222.222
208.67.220.220
or Google DNS:
8.8.8.8
8.8.4.4
Read how to set it up here:
http://code.google.com/speed/public-dns/docs/using.html
QUICK TIP: When you go to YouTube from Reddit, just click and change the aspect ratio (even higher aspect ratio videos will load faster). The Akamai CDN hosts more than one version, and most people only access the version that users link to. This tip will show better results than simply changing your DNS from your ISP to Google DNS or OpenDNS.
It could be your DNS provider. Try this http://code.google.com/speed/public-dns/. You can also try completely uninstalling your browser with revo uninstaller and reinstalling it. You should probably scan your computer for viruses as well. I'm not an expert but this is the stuff I would try first.
It's a Rogers DNS server issue, not a purposeful attack on IMDb by Rogers. Set up Google Public DNS on your computer if you need a fix before Rogers gets their act together (takes 3 minutes to set up and doesn't require a download).
just for the heck of it try setting your dns in whatever web browser you are using to googles (8.8.8.8 and 8.8.4.4), http://code.google.com/speed/public-dns/ there is some instructions if you don't know how to do that. Not sure if it will make a difference, but you never know.
I was having some trouble with some online games with Teksavvy cable. This was when they were just rolling it out. I fixed the problem by switching to Google's Public DNS servers. Now everything runs perfectly!
I fixed it by using Googles public DNS. Info here
Now that I'm using their DNS imgur links work fine and the having to reload a failed page should stop. With out it imgur links still don't work today, though they did yesterday.
More info here: http://code.google.com/speed/public-dns/
I use Google DNS - I haven't noticed any difference, I changed mine to google during the Comcast debacle.