Could not send email to office 365
Hello folks, Have you ever seen DNS issues on Office 365? MX record of Office 365 is example.mail.eo.outlook.com. I can get the MX record, however, I could not get the A record of the MX record, got Timeout. Does anyone have the same issue? Sincerely, Yuji
The company I work for has been having Outlook connectivity issues (intermittent for only a few end users) for the past 7 days for Office 365. We are in an upgrade status (on the 18th days or so; have been told it can last 30 days) and they changed our MX records without formal notification. We updated those on a Thursday or Friday and it worked until the following Monday where we observed it again, then magically fixed itself late afternoon that Monday. We had some more reports yesterday. The Microsoft technical support has not been helpful troubleshooting this for us. I am hoping it is related to our upgrade status but I cannot get an answer from anyone. -- Thanks, Joe On Wed, May 1, 2013 at 2:21 AM, ISHII, Yuji <you@ugec.net> wrote:
Hello folks,
Have you ever seen DNS issues on Office 365?
MX record of Office 365 is example.mail.eo.outlook.com. I can get the MX record, however, I could not get the A record of the MX record, got Timeout.
Does anyone have the same issue?
Sincerely, Yuji
I am also having the some issues going on 3 weeks now. I cannot access my e-mail via Outlook and my MX records keep changing. It is nuts support has been unable to help. ________________________________________ From: JoeSox Sent: Wednesday, May 01, 2013 9:24 AM To: nanog@nanog.org Subject: Re: Could not send email to office 365 The company I work for has been having Outlook connectivity issues (intermittent for only a few end users) for the past 7 days for Office 365. We are in an upgrade status (on the 18th days or so; have been told it can last 30 days) and they changed our MX records without formal notification. We updated those on a Thursday or Friday and it worked until the following Monday where we observed it again, then magically fixed itself late afternoon that Monday. We had some more reports yesterday. The Microsoft technical support has not been helpful troubleshooting this for us. I am hoping it is related to our upgrade status but I cannot get an answer from anyone. -- Thanks, Joe On Wed, May 1, 2013 at 2:21 AM, ISHII, Yuji <you@ugec.net> wrote:
Hello folks,
Have you ever seen DNS issues on Office 365?
MX record of Office 365 is example.mail.eo.outlook.com. I can get the MX record, however, I could not get the A record of the MX record, got Timeout.
Does anyone have the same issue?
Sincerely, Yuji
Ryan, Is your Office 365 account also in an upgrade status? If not, have you completed the upgrade? -- Thanks, Joe On Wed, May 1, 2013 at 8:42 AM, Ryan Finnesey <ryan@finnesey.com> wrote:
I am also having the some issues going on 3 weeks now. I cannot access my e-mail via Outlook and my MX records keep changing. It is nuts support has been unable to help. ________________________________________
It was in upgrade status for about 15 days. We had to open a separate ticket to fix the "upgrade" but even after they completed the upgrade I was unable to connect. -----Original Message----- From: JoeSox [mailto:joesox@gmail.com] Sent: Wednesday, May 1, 2013 12:28 PM To: nanog@nanog.org Subject: Re: Could not send email to office 365 Ryan, Is your Office 365 account also in an upgrade status? If not, have you completed the upgrade? -- Thanks, Joe On Wed, May 1, 2013 at 8:42 AM, Ryan Finnesey <ryan@finnesey.com> wrote:
I am also having the some issues going on 3 weeks now. I cannot access my e-mail via Outlook and my MX records keep changing. It is nuts support has been unable to help. ________________________________________
After our "upgrade", we started to see the body of received PLAIN TEXT emails truncated at less than 256 bytes, which frequently truncated emails in the middle of a word, the fix was a "setting change". Since being standardized in 1982 with RFC 822, you would think PLAIN TEXT emails would just work "out of the box". Tony -----Original Message----- From: Ryan Finnesey [mailto:ryan@finnesey.com] Sent: Wednesday, May 01, 2013 11:42 AM To: JoeSox; nanog@nanog.org Subject: RE: Could not send email to office 365 I am also having the some issues going on 3 weeks now. I cannot access my e-mail via Outlook and my MX records keep changing. It is nuts support has been unable to help. ________________________________________ From: JoeSox Sent: Wednesday, May 01, 2013 9:24 AM To: nanog@nanog.org Subject: Re: Could not send email to office 365 The company I work for has been having Outlook connectivity issues (intermittent for only a few end users) for the past 7 days for Office 365. We are in an upgrade status (on the 18th days or so; have been told it can last 30 days) and they changed our MX records without formal notification. We updated those on a Thursday or Friday and it worked until the following Monday where we observed it again, then magically fixed itself late afternoon that Monday. We had some more reports yesterday. The Microsoft technical support has not been helpful troubleshooting this for us. I am hoping it is related to our upgrade status but I cannot get an answer from anyone. -- Thanks, Joe On Wed, May 1, 2013 at 2:21 AM, ISHII, Yuji <you@ugec.net> wrote:
Hello folks,
Have you ever seen DNS issues on Office 365?
MX record of Office 365 is example.mail.eo.outlook.com. I can get the MX record, however, I could not get the A record of the MX record, got Timeout.
Does anyone have the same issue?
Sincerely, Yuji
We have fixed the problem. I had to complete a clear install of Outlook and remove the credentials that where on the computer in the control panel under credential manager. This may also fix/help with your issue. Cheers Ryan -----Original Message----- From: Tony Patti [mailto:tony@swalter.com] Sent: Wednesday, May 1, 2013 1:19 PM To: Ryan Finnesey; 'JoeSox'; nanog@nanog.org Subject: RE: Could not send email to office 365 After our "upgrade", we started to see the body of received PLAIN TEXT emails truncated at less than 256 bytes, which frequently truncated emails in the middle of a word, the fix was a "setting change". Since being standardized in 1982 with RFC 822, you would think PLAIN TEXT emails would just work "out of the box". Tony -----Original Message----- From: Ryan Finnesey [mailto:ryan@finnesey.com] Sent: Wednesday, May 01, 2013 11:42 AM To: JoeSox; nanog@nanog.org Subject: RE: Could not send email to office 365 I am also having the some issues going on 3 weeks now. I cannot access my e-mail via Outlook and my MX records keep changing. It is nuts support has been unable to help. ________________________________________ From: JoeSox Sent: Wednesday, May 01, 2013 9:24 AM To: nanog@nanog.org Subject: Re: Could not send email to office 365 The company I work for has been having Outlook connectivity issues (intermittent for only a few end users) for the past 7 days for Office 365. We are in an upgrade status (on the 18th days or so; have been told it can last 30 days) and they changed our MX records without formal notification. We updated those on a Thursday or Friday and it worked until the following Monday where we observed it again, then magically fixed itself late afternoon that Monday. We had some more reports yesterday. The Microsoft technical support has not been helpful troubleshooting this for us. I am hoping it is related to our upgrade status but I cannot get an answer from anyone. -- Thanks, Joe On Wed, May 1, 2013 at 2:21 AM, ISHII, Yuji <you@ugec.net> wrote:
Hello folks,
Have you ever seen DNS issues on Office 365?
MX record of Office 365 is example.mail.eo.outlook.com. I can get the MX record, however, I could not get the A record of the MX record, got Timeout.
Does anyone have the same issue?
Sincerely, Yuji
----- Original Message -----
From: "Tony Patti" <tony@swalter.com>
After our "upgrade", we started to see the body of received PLAIN TEXT emails truncated at less than 256 bytes, which frequently truncated emails in the middle of a word, the fix was a "setting change".
Since being standardized in 1982 with RFC 822, you would think PLAIN TEXT emails would just work "out of the box".
This is Microsoft, Tony. They don't understand text, and would prefer that all emails be a MIME attachment of a Word document. Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274
Just another day for them.. Office 365 has been broken for us for a long time. I've been thinking about a rackspace hosted exchange instead.. Have you guys looked into alternatives? Sent from my T-Mobile 4G LTE Device -------- Original message -------- From: JoeSox <joesox@gmail.com> Date: 05/01/2013 6:27 AM (GMT-08:00) To: nanog@nanog.org Subject: Re: Could not send email to office 365 The company I work for has been having Outlook connectivity issues (intermittent for only a few end users) for the past 7 days for Office 365. We are in an upgrade status (on the 18th days or so; have been told it can last 30 days) and they changed our MX records without formal notification. We updated those on a Thursday or Friday and it worked until the following Monday where we observed it again, then magically fixed itself late afternoon that Monday. We had some more reports yesterday. The Microsoft technical support has not been helpful troubleshooting this for us. I am hoping it is related to our upgrade status but I cannot get an answer from anyone. -- Thanks, Joe On Wed, May 1, 2013 at 2:21 AM, ISHII, Yuji <you@ugec.net> wrote:
Hello folks,
Have you ever seen DNS issues on Office 365?
MX record of Office 365 is example.mail.eo.outlook.com. I can get the MX record, however, I could not get the A record of the MX record, got Timeout.
Does anyone have the same issue?
Sincerely, Yuji
http://email-guru.com/ ? --- () ascii ribbon campaign against html e-mail /\ www.asciiribbon.org
-----Original Message----- From: Warren Bailey [mailto:wbailey@satelliteintelligencegroup.com] Sent: Wednesday, 01 May, 2013 10:12 To: JoeSox; nanog@nanog.org Subject: Re: Could not send email to office 365
Just another day for them.. Office 365 has been broken for us for a long time. I've been thinking about a rackspace hosted exchange instead.. Have you guys looked into alternatives?
Sent from my T-Mobile 4G LTE Device
-------- Original message -------- From: JoeSox <joesox@gmail.com> Date: 05/01/2013 6:27 AM (GMT-08:00) To: nanog@nanog.org Subject: Re: Could not send email to office 365
The company I work for has been having Outlook connectivity issues (intermittent for only a few end users) for the past 7 days for Office 365. We are in an upgrade status (on the 18th days or so; have been told it can last 30 days) and they changed our MX records without formal notification. We updated those on a Thursday or Friday and it worked until the following Monday where we observed it again, then magically fixed itself late afternoon that Monday. We had some more reports yesterday. The Microsoft technical support has not been helpful troubleshooting this for us. I am hoping it is related to our upgrade status but I cannot get an answer from anyone. -- Thanks, Joe
On Wed, May 1, 2013 at 2:21 AM, ISHII, Yuji <you@ugec.net> wrote:
Hello folks,
Have you ever seen DNS issues on Office 365?
MX record of Office 365 is example.mail.eo.outlook.com. I can get the MX record, however, I could not get the A record of the MX record, got Timeout.
Does anyone have the same issue?
Sincerely, Yuji
Yes we are just working out our licensing agreement and moving Exchange back in house. From talking with people BPOS (Exchange 2007) was a mess. We were on Office 365 with Exchange 2010 without issue service worked very well. Then they upgraded us to Exchange 2013 and it is just broken we are unable to connect. I thought the problem is fixed but now it is back. -----Original Message----- From: Warren Bailey [mailto:wbailey@satelliteintelligencegroup.com] Sent: Wednesday, May 1, 2013 12:12 PM To: JoeSox; nanog@nanog.org Subject: Re: Could not send email to office 365 Just another day for them.. Office 365 has been broken for us for a long time. I've been thinking about a rackspace hosted exchange instead.. Have you guys looked into alternatives? Sent from my T-Mobile 4G LTE Device -------- Original message -------- From: JoeSox <joesox@gmail.com> Date: 05/01/2013 6:27 AM (GMT-08:00) To: nanog@nanog.org Subject: Re: Could not send email to office 365 The company I work for has been having Outlook connectivity issues (intermittent for only a few end users) for the past 7 days for Office 365. We are in an upgrade status (on the 18th days or so; have been told it can last 30 days) and they changed our MX records without formal notification. We updated those on a Thursday or Friday and it worked until the following Monday where we observed it again, then magically fixed itself late afternoon that Monday. We had some more reports yesterday. The Microsoft technical support has not been helpful troubleshooting this for us. I am hoping it is related to our upgrade status but I cannot get an answer from anyone. -- Thanks, Joe On Wed, May 1, 2013 at 2:21 AM, ISHII, Yuji <you@ugec.net> wrote:
Hello folks,
Have you ever seen DNS issues on Office 365?
MX record of Office 365 is example.mail.eo.outlook.com. I can get the MX record, however, I could not get the A record of the MX record, got Timeout.
Does anyone have the same issue?
Sincerely, Yuji
On 01/05/13 10:21, ISHII, Yuji wrote:
Hello folks,
Have you ever seen DNS issues on Office 365?
MX record of Office 365 is example.mail.eo.outlook.com. I can get the MX record, however, I could not get the A record of the MX record, got Timeout.
Does anyone have the same issue?
Sincerely, Yuji
This may be a red herring, but I've heard of some dropping of DNS queries for the names within outlook.com domains where the queries are all coming from source port 53 (i.e. your recursive server doesn't use query source port randomization). Might be worth checking what the recursive server you're using is doing? See https://www.dns-oarc.net/oarc/services/porttest Cathy
On 2013-05-02, at 02:42, Cathy Almond <cathya@isc.org> wrote:
This may be a red herring, but I've heard of some dropping of DNS queries for the names within outlook.com domains where the queries are all coming from source port 53 (i.e. your recursive server doesn't use query source port randomization
... or there's a NAT or some other box in front of the recursive server which re-writes the source port...
). Might be worth checking what the recursive server you're using is doing?
Joe
Our Technical Support is reporting a big jump in Outlook connectivity issues about 5-10 minutes ago. Our resolvers are testing fine. -- Thanks, Joe On Thu, May 2, 2013 at 4:53 AM, Joe Abley <jabley@hopcount.ca> wrote:
On 2013-05-02, at 02:42, Cathy Almond <cathya@isc.org> wrote:
This may be a red herring, but I've heard of some dropping of DNS queries for the names within outlook.com domains where the queries are all coming from source port 53 (i.e. your recursive server doesn't use query source port randomization
... or there's a NAT or some other box in front of the recursive server which re-writes the source port...
). Might be worth checking what the recursive server you're using is doing?
Joe
Just an update if list members are still experiencing this issue. I spoke on the phone with Escalation Manager for Microsoft North America and they had meetings today and their Engineering team is putting a game plan together to roll out a fix for the Outlook connectivity issues. They were debating to roll-out to the group of effected customers or one-by-one. From the data I provided to them it looks like something to do with their NSPI RPC endpoint environment. They told me I should receive a call tomorrow but call them Friday if I do not receive a call. Hopefully, everyone else experiencing this issue is being taken care of as this is the main concern with Cloud services is the lack of response times on major issues. -- Thanks, Joe On Thu, May 2, 2013 at 10:16 AM, JoeSox <joesox@gmail.com> wrote:
Our Technical Support is reporting a big jump in Outlook connectivity issues about 5-10 minutes ago. Our resolvers are testing fine. -- Thanks, Joe
On Thu, May 2, 2013 at 4:53 AM, Joe Abley <jabley@hopcount.ca> wrote:
On 2013-05-02, at 02:42, Cathy Almond <cathya@isc.org> wrote:
This may be a red herring, but I've heard of some dropping of DNS queries for the names within outlook.com domains where the queries are all coming from source port 53 (i.e. your recursive server doesn't use query source port randomization
... or there's a NAT or some other box in front of the recursive server which re-writes the source port...
). Might be worth checking what the recursive server you're using is doing?
Joe
I'm an engineer on the Microsoft Office365 Exchange Online ("outlook.office365.com") network team. I'm gathering forensics specific to IPv6 reports -- are people still experiencing IPv6-related issues? I am interested solely in failures that are IPv6 connection issues to "outlook.office365.com". If you have a clear repro of an IPv6 connection failure, please message me off-list with at least a traceroute. (Please don't deluge me with non-IPv6-related issues -- I'm a network guy working on this one report.) Jason (dot) Sherron [at] Microsoft (dot) com -----Original Message----- From: JoeSox [mailto:joesox@gmail.com] Sent: Wednesday, May 8, 2013 4:35 PM To: nanog@nanog.org Subject: Re: Could not send email to office 365 Just an update if list members are still experiencing this issue. I spoke on the phone with Escalation Manager for Microsoft North America and they had meetings today and their Engineering team is putting a game plan together to roll out a fix for the Outlook connectivity issues. They were debating to roll-out to the group of effected customers or one-by-one. From the data I provided to them it looks like something to do with their NSPI RPC endpoint environment. They told me I should receive a call tomorrow but call them Friday if I do not receive a call. Hopefully, everyone else experiencing this issue is being taken care of as this is the main concern with Cloud services is the lack of response times on major issues. -- Thanks, Joe On Thu, May 2, 2013 at 10:16 AM, JoeSox <joesox@gmail.com> wrote:
Our Technical Support is reporting a big jump in Outlook connectivity issues about 5-10 minutes ago. Our resolvers are testing fine. -- Thanks, Joe
On Thu, May 2, 2013 at 4:53 AM, Joe Abley <jabley@hopcount.ca> wrote:
On 2013-05-02, at 02:42, Cathy Almond <cathya@isc.org> wrote:
This may be a red herring, but I've heard of some dropping of DNS queries for the names within outlook.com domains where the queries are all coming from source port 53 (i.e. your recursive server doesn't use query source port randomization
... or there's a NAT or some other box in front of the recursive server which re-writes the source port...
). Might be worth checking what the recursive server you're using is doing?
Joe
Jason Sherron <jason.sherron@microsoft.com> wrote: Hello Jason,
I'm an engineer on the Microsoft Office365 Exchange Online ("outlook.office365.com") network team. I'm gathering forensics specific to IPv6 reports -- are people still experiencing IPv6-related issues? I am interested solely in failures that are IPv6 connection issues to "outlook.office365.com".
Looks okay from my POV now. Thanks for fixing it, can you share the root cause? This issue had rather interesting symptoms. Bernhard
Hi Jason, My business mysteriously stabilized after speaking with the Escalation Manager of North America, last week. Next, health status statement said it was a false-positive on May 9th. Yesterday, speaking with the tech to close my case, he had a hunch engineering fixed something but he made it clear that he was only guessing. I never was able to get a real cause of this issue for the company I work for or the reported other companies in North America reporting the issue. Troubleshooting never led me down an IPv6 path but others might have, or maybe that was the root cause on the Microsoft side. -- Thanks, Joe On Tue, May 14, 2013 at 11:02 AM, Jason Sherron <jason.sherron@microsoft.com
wrote:
I'm an engineer on the Microsoft Office365 Exchange Online (" outlook.office365.com") network team. I'm gathering forensics specific to IPv6 reports -- are people still experiencing IPv6-related issues? I am interested solely in failures that are IPv6 connection issues to " outlook.office365.com".
If you have a clear repro of an IPv6 connection failure, please message me off-list with at least a traceroute. (Please don't deluge me with non-IPv6-related issues -- I'm a network guy working on this one report.)
Jason (dot) Sherron [at] Microsoft (dot) com
-----Original Message----- From: JoeSox [mailto:joesox@gmail.com] Sent: Wednesday, May 8, 2013 4:35 PM To: nanog@nanog.org Subject: Re: Could not send email to office 365
Just an update if list members are still experiencing this issue. I spoke on the phone with Escalation Manager for Microsoft North America and they had meetings today and their Engineering team is putting a game plan together to roll out a fix for the Outlook connectivity issues. They were debating to roll-out to the group of effected customers or one-by-one. From the data I provided to them it looks like something to do with their NSPI RPC endpoint environment. They told me I should receive a call tomorrow but call them Friday if I do not receive a call. Hopefully, everyone else experiencing this issue is being taken care of as this is the main concern with Cloud services is the lack of response times on major issues. -- Thanks, Joe
On Thu, May 2, 2013 at 10:16 AM, JoeSox <joesox@gmail.com> wrote:
Our Technical Support is reporting a big jump in Outlook connectivity issues about 5-10 minutes ago. Our resolvers are testing fine. -- Thanks, Joe
On Thu, May 2, 2013 at 4:53 AM, Joe Abley <jabley@hopcount.ca> wrote:
On 2013-05-02, at 02:42, Cathy Almond <cathya@isc.org> wrote:
This may be a red herring, but I've heard of some dropping of DNS queries for the names within outlook.com domains where the queries are all coming from source port 53 (i.e. your recursive server doesn't use query source port randomization
... or there's a NAT or some other box in front of the recursive server which re-writes the source port...
). Might be worth checking what the recursive server you're using is doing?
Joe
participants (11)
-
Bernhard Schmidt -
Cathy Almond -
ISHII, Yuji -
Jason Sherron -
Jay Ashworth -
Joe Abley -
JoeSox -
Keith Medcalf -
Ryan Finnesey -
Tony Patti -
Warren Bailey