On Wednesday, March 25, 2015, several DNS servers were having trouble resolving domain names. I first noticed this when visiting Daring Fireball. I was not able to load the site on my iPhone, which is on T-Mobile network. By 4:00 p.m. Pacific Daylight Time, I was still unable to access Daring Fireball on my iPhone. I took the screenshot and tweeted:
If I had to guess, it might be DNS issue with T-Mobile. @gruber
Two hours later I noticed that I still couldn’t access Daring Fireball. This time I was using the office network; connected through AT&T DSL. We could only get AT&T in this particular area. Then I tweeted to John Gruber:
It seems @daringfireball is still down. @gruber
Within 3 minutes, Gruber replied:
@iVeryAm No, my site is up. There are internet-wide routing problems, alas: http://www.internethealthreport.com
When I arrived at a colleague’s residence, I was able to to load Daring Fireball site through Verizon FiOS.
Later on, Ben Drago replied:
@gruber@iVeryAm It looks like Google’s DNS servers are not resolving http://daringfireball.net . Working OK w/ @OpenDNSpic.twitter.com/O9SSCGuFb3
I tested a few DNS servers and some of them were having the same issues with Google DNS.
At the time of this post, the issue persists on some DNS servers.
