Comcast DNS

554 posts

Comcast DNS

Comcast DNS

@ComcastDNS

Philadelphia, PA Katılım Ocak 2012
11 Takip Edilen404 Takipçiler
Comcast DNS
Comcast DNS@ComcastDNS·
@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.
English
0
0
6
0
Jeff Finkelstein
Jeff Finkelstein@BoulderJeff·
Comcast's 75.75.75.75 DNS server is down and not resolving, and is taking down a big portion of the web. #comcastdown
English
1
0
0
0
Johnathon Mohr
Johnathon Mohr@johnathonm·
@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
English
1
0
0
0
Sean
Sean@seanjmccurdy·
@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?
English
2
0
0
0
Michael Zimmerman
Michael Zimmerman@mwzimmerman·
@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.
English
7
0
4
0
Eric Richards
Eric Richards@EricRichards22·
Sigh. Comcast seems to be doing some hinky things with DNS today. Cloud everything is great until your pipe to the cloud gets sketchy
English
1
0
0
0
Comcast DNS
Comcast DNS@ComcastDNS·
@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).
English
0
5
6
0
Comcast DNS
Comcast DNS@ComcastDNS·
@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.
English
1
0
0
0
Comcast DNS
Comcast DNS@ComcastDNS·
@trfry What is the domain name? Also, what is the error message you're seeing?
English
0
0
0
0
Comcast DNS
Comcast DNS@ComcastDNS·
@LeThirst We are not aware of any issues currently, but I did pass this on to one of our internal contacts that may have a better insight.
English
0
0
0
0
Comcast DNS
Comcast DNS@ComcastDNS·
@andrew_michels stream.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.
English
1
0
1
0
Andy Michels
Andy Michels@andrew_michels·
@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.
English
1
0
0
0