DNS Routing Problem on Wednesday, March 25, 2015.

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. 

DaringFireball T-Mobile DNS

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  is still down. 

Within 3 minutes, Gruber replied:

 No, my site is up. There are internet-wide routing problems, alas: 

Daring Fireball is still down

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:

 It looks like Google’s DNS servers are not resolving . Working OK w/ 

Ben Drago Google DNS has a problem

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.