Thanks Paul! I chose my words poorly. I should have said authoritative NSes. This affects comcast.com, xfinity.com, and xfinity.net as well as comcast.net as I originally reported. Unsure of any other domains. -- | Jeremy Chadwick jdc_at_koitsu.org | | UNIX Systems Administrator PGP 0x2A389531 | | Making life hard for others since 1977. | On Thu, Mar 30, 2023 at 10:14:44PM -0600, Paul Ebersman via Outages wrote:
outages> Looks like Comcast's public-facing DNS servers aren't outages> responsive. [...] outages> comcast.net. 172800 IN NS dns101.comcast.net. outages> comcast.net. 172800 IN NS dns102.comcast.net. outages> comcast.net. 172800 IN NS dns103.comcast.net. outages> comcast.net. 172800 IN NS dns104.comcast.net. outages> comcast.net. 172800 IN NS dns105.comcast.net.
These are their auth servers, including for comcast.net. Confirmed the IPs for them are pingable but they time out for any DNS query.
The comcast recursive servers at 75.75.75.75 are still working but SERVFAIL for queries that ask dns10x.comcast.net. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages