
24 Oct
2014
24 Oct
'14
4:34 a.m.
Since about midnight (Eastern) Comcast's DNS (75.75.75.7[5,6]) has been giving timeouts and the occasional 'no route to host' from Vermont. Switched our resolvers to use Google's Public DNS (via the same Comcast line) and all services returned to normal. Packet traces aren't interesting (just outbound traffic, no responses) and traceroutes to the cdn usually succeed. dns.comcast.net reports no problems. Queries at the command line sometimes succeed, sometimes fail, sometimes take a long time to finish. -Bill