It seems like a good idea to use Google's public DNS 188.8.131.52 and 184.108.40.206 because it's really fast -- much faster than my own ISP's DNS! -- and probably more reliable, too. That seems like a ...
are servers 220.127.116.11 (or 18.104.22.168) located on location, or are they distributed throughout the world? what I am interested in is, if I issue DNS request from austria, will I get reply from US or from ...
Is there any downside to using a public DNS service like Google's 22.214.171.124/126.96.36.199 for corporate network DNS service, as in making it the network connection's DNS server for an AD DC? It seems like if ...
I was looking up info on using Google DNS for our website but found info on using Google Public DNS for our local computers. Anyone know if how much faster it is? Or a good way to measure it?
Back when google first released their 188.8.131.52 and 184.108.40.206 dns servers I did some profiling, and they are way faster for our location. A more recent test confirms this is still the case. However, after ...
Last night we were having some serious server events. At first it appeared that our issue was with google (220.127.116.11). We would run ping and at some point we would have some packet loss. At about the ...
This is a problem that has plagued my office for a few months now. It has bounced between our ISP (Comcast), our IT contractor, and even our VOIP contractor, each of which has "fixed" it at least ...
I noticed very strange but consistent performance behavior from Google Public DNS 18.104.22.168. Even-though a DNS record was cached, the response time was in the range of 20-30ms, which seems high. When I ...