Update on DigitalOcean’s connectivity issue with 4.2.2.2

Tue, Sep 2, 2014

This is the followup post of the following report: []1

Seems that DigitalOcean haven’t fixed anything yet. 8 days since my last post. This page https://status.digitalocean.com/ show no information regarding this issue. Other people also reported similar behavior. Come on, do something DigitalOcean!

Here is the latest benchmarks from my server to 3 different DNS provider: 4.2.2.2 (Level3), 8.8.8.8 (Google) and 208.67.222.222 (OpenDNS). I issued 10 dig queries for google.com, each of them 10 seconds apart. 6/10 queries sent to 4.2.2.2 are timed out. None of them happen for 8.8.8.8 and 208.67.222.222

tuananh@codepie:~$ for i in {1..10}; do dig google.com @4.2.2.2 | grep 'connection timed out'; sleep 10; done;
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
tuananh@codepie:~$ for i in {1..10}; do dig google.com @8.8.8.8 | grep 'connection timed out'; sleep 10; done;
tuananh@codepie:~$ for i in {1..10}; do dig google.com @208.67.222.222 | grep 'connection timed out'; sleep 10; done;