8.8.8.8 blocked ?

qdada

qdada

Expert Member
Joined
Nov 19, 2003
Messages
1,428
Reaction score
18
Location
Sunninghill
My telkom experience has been pretty decent, however things are starting to change.

I noticed only a month ago that when I specify googles dns server in my connection settings, they do not work at all. Has anyone been experiencing this ?

In addition today, google does not resolve whether I use Telkoms own DNS servers or googles.
I am on an uncapped account, I do not know if I am throttled though I did check the usage tracker tool. All I see on that tool is a green bar graph hovering aound 20 % (it is a guess) but no specifics regarding my actual usage only the fact that i am on an uncapped account.

So anyone ?
 
qDot said:
In addition today, google does not resolve whether I use Telkoms own DNS servers or googles.
Click to expand...

This has been happening fairly often to me (cannot connect to websites, addresses not resolving, etc.) regardless of DNS server for the last 3 months or so. I am also uncapped and not throttled.

Try unplugging your router from the power socket for a full 5-10 minutes. I find that normally fixes it for me, a regular reboot of the router does not.

I'm not sure what the exact cause of this is. It could be my router. I've had to throttle dropbox as I've noticed it kills my 4Mbps line (not resolving, etc.) if left unthrottled, for some reason. My brother has a 10Mbps uncapped line in the same area as me and has also noticed weird problems with his line today, including being unable to access Google services (e.g. Youtube or normal Google Search) on TI, but without problems when using Afrihost.
 
There are problems with TI's routing. Can't get to most sites now, in addition to Google's. Switching to Axxess/Afrihost/FNB with the same DNS works.
 
Its a Telkom issue. Had it at home last night for about an hour, and lunchtime today at the office. Most other websites working OK, not Google. Changed to different ADSL ISP and problem solved
 
@OP, if you are using Windows OS, try flushing the dns cache "ipconfig /flushdns"

Also reset your router after clearing the cache. That normally does the trick.

Not entirely sure about Linux or Mac OS. Think restarting the network interface clears the cache(?)
 
Bryn26 said:
I use Google's DNS. Should I not?
Click to expand...

I don't see a problem with using Google's DNS. It's a public DNS after all.
If you are concerned about something, you can check the FAQ section: https://developers.google.com/speed/public-dns/faq
The only thing is that it does not support any service level agreements. So unless you are running a company using just Google's DNS, I wouldn't worry. :)

Also forgot to mention to OP, try do a trace route to see if it's not something timing out between you and 8.8.8.8 or 8.8.4.4.
 
Bryn26 said:
I use Google's DNS. Should I not?
Click to expand...

Nothing inherently wrong with using whichever DNS you'd like, but a geographically closer one would be better, like say 196.25.1.1 (SAIX).

E.g.
I'm pinging 8.8.8.8 at 200ms. This means that if I go to any website, there would be an additional 200ms for each resource which requires a DNS lookup, and thats only for the IP lookup, not the connection to said resource.

However, using SAIX's, that would only require an additional 4ms (my ping to there) for the lookup.

So suppose www.example.com has links to pics on www.other.com and www.another.com.

www.example.com -> +200ms
www.other.com -> +200ms
www.another.com -> +200ms

for altogether 600ms, just for the ip lookups (okay things can be done concurrently to minimise this number, but the point still stands), whereas SAIX would take altogether 12ms.
 
@battletoad Very good explanation, thank you.
 
Google is f'd today for some connections. Not sure whats going on but something is def up.
 
battletoad said:
Nothing inherently wrong with using whichever DNS you'd like, but a geographically closer one would be better, like say 196.25.1.1 (SAIX).

E.g.
I'm pinging 8.8.8.8 at 200ms. This means that if I go to any website, there would be an additional 200ms for each resource which requires a DNS lookup, and thats only for the IP lookup, not the connection to said resource.

However, using SAIX's, that would only require an additional 4ms (my ping to there) for the lookup.

So suppose www.example.com has links to pics on www.other.com and www.another.com.

www.example.com -> +200ms
www.other.com -> +200ms
www.another.com -> +200ms

for altogether 600ms, just for the ip lookups (okay things can be done concurrently to minimise this number, but the point still stands), whereas SAIX would take altogether 12ms.
Click to expand...

Thanks for the info. I get 178ms to 8.8.8.8 and 38ms to 196.7.7.7 (Afrihost), so I guess I should switch over.
 
How does this impact the DNS settings you use for Unotelly? Should you have a default backup DNS for non-Unotelly lookups? I know if the lookup is not part of Unotelly's list it just passes the request on, but I can't remember to where?
 
furpile said:
How does this impact the DNS settings you use for Unotelly? Should you have a default backup DNS for non-Unotelly lookups? I know if the lookup is not part of Unotelly's list it just passes the request on, but I can't remember to where?
Click to expand...

Unotelly's DNS is crap for general use. I know because I tried it. I only use Unotelly's DNS on the devices that need it, and leave the router with a normal DNS.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X