@BoulderJeff Hey, Jeff. We're seeing no issues with the resolvers across our footprint. If there's a specific name that is problematic or other details you can provide, we're happy to take as look.
@ComcastDNS Hello, I have been dealing with an issue for weeks and dealt with so many parties. Many calls, and even have drilled and captures probably 14 abuse, cpi,csc. The list goes on Iana took it seriously, level 3 agent. Anyway, I need help with a record. @comcastcares
@ComcastDNS I need help! Nobody at business support seams to know anything about your nameservers. Our domain is using NS1.COMCASTBUSINESS.NET for its nameserver - how do we make DNS changes? Is there a control panel somewhere?
@ComcastDNS and @Register_com Have you teams made any progress on the register.com DNS outage on the Comcast Network? We would appreciate an update. Thank you.
@mwzimmerman@Register_com@mwzimmerman@Register_com
We've had issues reported with register.com and we've verified via third party tools that their authoritative Name Servers appear to be unreachable from various locations even outside of the Comcast network.
@ComcastDNS We are seeing an issue with 75.75.75.75 resolving addresses for an entire domain hosted at @Register_com name servers. The addresses resolve with other DNS servers without issue. Would you be able to take a look? If you PM me, I can send you the domain.
@jpmens@wupeka I do see that 8.8.8.8 returns AD from many locations. Our resolvers are correctly returning SERVFAIL across our footprint. Other validating resolvers also return SERVFAIL (1.1.1.1/9.9.9.9/etc).
@Tekneek Comcast's own resolvers (75.75.75.75, etc) as well as Google's (8.8.8.8, etc) and Cloudflare's (1.1.1.1, etc) all perform DNSSEC validation and have no issues. This may be a problem with your resolver.
@andrew_michelsstream.radio.co is resolving properly in DNS across our entire footprint. If you wish to switch back to our resolvers and are still having issues we could help you troubleshoot further.
@ComcastDNS I couldn’t access stream.radio.co at all when connected to my home network (after always being able to). Phone and online support couldn’t figure it out. I just set my DNS servers to Google’s and am now able to access the URL without issue.
@ComcastDNS@comcast@comcastcares Thanks... I tweeted you because you seemed like the farthest-into-the-network twitter account. My ESPN is showing up just fine. 🤣😇