Frank is correct. Bill, please send over a traceroute to 75.75.75.75 and 75.75.76.76 and I'll forward that information to the DNS infrastructure team. Thanks, John On Fri, Oct 24, 2014 at 6:04 AM, Frank Bulk via Outages <outages@outages.org
wrote:
Bill,
I believe Comcast has anycasted their DNS servers, so if you could provide a traceroute to each IP then if Comcast personnel are lurking they can better guess which one it is.
Frank
*From:* Outages [mailto:outages-bounces@outages.org] *On Behalf Of *Bill McGonigle via Outages *Sent:* Friday, October 24, 2014 4:34 AM *To:* outages@outages.org *Subject:* [outages] Intermittent Comcast DNS issues from VT
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
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages