Twitter Tweets about Dns as of December 11, 2009
Blunk: Probando Google Public DNS
nesaranow: Sorry about no posts. Switching servers and waiting for the DNS to propogate. Much stuff to post - stand by!
bunltd: Guess what: adding your ip to my client's server's whitelist won't fix *your* dns problem causing spam filters to trip. <--- grrr
ciscojsolse: HTTP to Twitter.com Total RTT: 1469 milliseconds
( DNS RTT: 41 ms
, TCP Connection RTT: 134 ms
, HTTP Transaction RTT: 1294 ms
)
CohesiveLogic: How To: Create PTR Entries for a Classless Reverse DNS Zone on Windows 2008 http://post.ly/EoSR
jphillips: How To: Create PTR Entries for a Classless Reverse DNS Zone on Windows 2008 http://post.ly/EoSR
VerizonBerry: Usando Google Public DNS con Conexion de Verizon Broadband en Ubuntu Karmic Koala 9.10 http://ping.fm/842CG http://bit.ly/5x75rm
ecubuntu: Usando Google Public DNS con Conexion de Verizon Broadband en Ubuntu Karmic Koala 9.10 http://ping.fm/842CG
dimepr: For Friends in Costa Rica: If your internet sucks, try Google Public DNS http://post.ly/EoR6
WikiWorldBook: Switching our DNS this w/e. Crossed fingers! I bought a luger just in case.
absolute3: ??LAN??????PC?twitter?????????iPhone???????PC???DNS????????????????DNS?????????????????????????????????????????????????
loic_d: RT @sarbogast: Google DNS does seem a lot faster: http://code.google.com/speed/public-dns/docs/using.html
reedobrien: @spaley They only know what goes through them and what is scourable on the web. DNS leaks all nonlocal traffic points, sequenced