anyone else found this is not working today, is it 3BB or is access being blocked in Thailand

8.8.4.4 is working

Working with TOT

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 18 ms 20 ms 22 ms node-6bl.pool-*-*.dynamic.totbb.net [*.*.*.*]
3 16 ms 16 ms 17 ms 172.17.52.1
4 27 ms 27 ms 55 ms 10.227.53.213
5 26 ms 51 ms 26 ms hundred-gi-0-7-0-1.cwt-gw-01.totisp.net [203.114.118.138]
6 29 ms 24 ms 32 ms HUN-gi-0-5-0-1.cwt-core-01.totiig.net [180.180.255.61]
7 41 ms 51 ms 129 ms ten-gi-0-4-0-19.hyi-core.totiig.net [203.190.251.130]
8 47 ms 48 ms 48 ms 72.14.220.162
9 47 ms 47 ms 47 ms 216.239.47.109
10 53 ms 49 ms 49 ms 66.249.94.235
11 50 ms 49 ms 49 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

yes it seems to be working now for some reason, no idea what happened, I also pinged it earlier when it wasn't working and got a good ping - wierd

You can also use the other Google DNS of 8.8.4.4...maybe best just to use 8.8.8.8 and 8.8.4.4 as your primary and secondary DNS.

But to tell you the truth, I use to use Google DNS years back when on TOT and now on True and found it rarely helped me with any of my internet issues. And when using some of those DNS benchmarking programs it showed me using my ISP's DNS was faster.

A handy app is DNS jumper, lets you select from a wide range of DNS to find fastest

or you can add your own, its quick and easy,and free.

regards worgeordie

Personally, I would stay away from any DNS with ping times lower than 200ms. I don't believe in faster than light communication speeds. This issue has been discussed in another thread. Look if up if interested.

In any case, most name resolvers cache the entries from DNS queries, Windows excessively so. 200-300ms response from a DNS will not slow down your browsing. It is more important that the servers are always available. I don't fully trust the Google DNS, and use Open DNS servers, 208.67.222.220 and 208.67.220.222. Or to be extra sure that results are correct, fire up my own DNS running on one of my Linux servers and querying the top root servers. That gives sub ms ping times!

Personally, I would stay away from any DNS with ping times lower than 200ms. I don't believe in faster than light communication speeds. This issue has been discussed in another thread. Look if up if interested.

In any case, most name resolvers cache the entries from DNS queries, Windows excessively so. 200-300ms response from a DNS will not slow down your browsing. It is more important that the servers are always available. I don't fully trust the Google DNS, and use Open DNS servers, 208.67.222.220 and 208.67.220.222. Or to be extra sure that results are correct, fire up my own DNS running on one of my Linux servers and querying the top root servers. That gives sub ms ping times!

Actually, if I recall, the OpenDNS servers are 208.67.222.222 and 208.67.220.220.

Personally, I would stay away from any DNS with ping times lower than 200ms. I don't believe in faster than light communication speeds. This issue has been discussed in another thread. Look if up if interested.

In any case, most name resolvers cache the entries from DNS queries, Windows excessively so. 200-300ms response from a DNS will not slow down your browsing. It is more important that the servers are always available. I don't fully trust the Google DNS, and use Open DNS servers, 208.67.222.220 and 208.67.220.222. Or to be extra sure that results are correct, fire up my own DNS running on one of my Linux servers and querying the top root servers. That gives sub ms ping times!

Actually, if I recall, the OpenDNS servers are 208.67.222.222 and 208.67.220.220.

Yep, correct.......................

There are more than two resolvers on Opendns. The less known are more likely to return the results faster. An these don't give you superluminal ping times.

C:\>nslookup 208.67.222.220

Name: resolver3.opendns.com
Address: 208.67.222.220


C:\>nslookup 208.67.220.222

Name: resolver4.opendns.com
Address: 208.67.220.222

on 3bb, 8.8.8.8 is dead for me. Ping timeout.