They appear to know about it - there's an open incident (EX397744) on the service health dashboard.
Ken. > -----Original Message----- > From: mailop <mailop-boun...@mailop.org> On Behalf Of Dan Malm via > mailop > Sent: Wednesday 6 July 2022 10:42 > To: mailop@mailop.org > Subject: [mailop] Delivery and DNS issues for Microsoft / m365 > > Hi, > > We're seeing a lot of DNS errors for *.mail.protection.outlook.com at > the moment. NS lookup for mail.protection.outlook.com resolves to two > hostnames that in turn resolve to the same IP. What IP they both > resolves to varies over time, and one or more of those IPs doesn't > respond at all on port 53, so whenever the non working IP is cached we > can't lookup MX records for m365 customers for a while. The DNS servers > we can reach also don't support edns or qname minimization... > > And when DNS doesn't fail we have a lot of deliveries respond with: > > Temporary server error. Please try again later ATTR2 [GV0CHE01FT017.eop- > che01.prod.protection.outlook.com > > I'm assuming we're not the only ones seeing these problems at the > moment? > > https://portal.office.com/servicestatus lists issues with outlook.com > but the description there doesn't seem to fit what I'm seeing. > > -- > BR/Mvh. Dan Malm, Systems Engineer, One.com _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
