Solved

New MX Records

Posted on 2016-09-21
12
60 Views
Last Modified: 2016-09-23
Hello,
We have just switched our internet connection from cable to fiber. This required a public IP address change. I updated the MX records with our domain host but I am now getting  442 4.4.2 Connection Dropped  errors. Not all mail is doing this but a significant amount. I have several iPhone users who are now not getting mail on their phones but other iPhone users do. I realize it takes a little while to propagate the servers with the new records but it has been over 6 hours. Any help with this would be appreciated.

Thank you
0
Comment
Question by:daskas27
  • 6
  • 5
12 Comments
 
LVL 14

Accepted Solution

by:
Todd Nelson earned 500 total points
Comment Utility
MX records are not necessarily related to the IP address used for OWA and autodiscover.  But in your case, they may be related.

FYI ... Public DNS propogation can take up to 72 hours.

Did you firewall NAT rules get updated?

Keep in mind too with regard to DNS propogation that not all users and phone services use the same DNS hosts and name services.  That could be why you are seeing a varied experience.

My advice ... be patient.
0
 

Author Comment

by:daskas27
Comment Utility
Thank you. Yes, NAT was updated. I guess you are right. Patience has never been one of my virtues.
0
 
LVL 23

Expert Comment

by:Erik Bjers
Comment Utility
You can change the TTL on your records to force faster update across the web but without this they can take a long time to replicate.
0
 

Author Comment

by:daskas27
Comment Utility
Hello, All the online tools for looking up mx records and reverse dns show correctly now. However, mail is still staying in the Exchange queue. Do I have to do anything on the Exchange server like stop and start the transport or something?
0
 
LVL 14

Expert Comment

by:Todd Nelson
Comment Utility
Can you perform a successful telnet outside of your network from the Exchange server?  You might need to install the Windows telnet client on the Exchange server.

telnet outlook.com 25

Open in new window


If not, then the firewall or ISP is blocking outbound SMTP traffic.
0
 

Author Comment

by:daskas27
Comment Utility
The firewall logs show no blocking and I can mail to some domains almost immediately, such as yahoo.
0
IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 
LVL 14

Expert Comment

by:Todd Nelson
Comment Utility
Any NDRs?

I'm assuming Exchange here...

Run this command to see what the errors (if any) are associated with the messages in the queue.

Get-Message | ft -auto DateReceived,FromAddress,Subject,LastError

Open in new window


It may be a lot of info posted to the console, so you can run this command to export the data to a CSV file.

Get-Message | SelectObject DateReceived,FromAddress,Subject,LastError | Export-Csv C:\MessageQueueErrors -NoTypeInformation

Open in new window

0
 

Author Comment

by:daskas27
Comment Utility
I can't see all the output from the first command. the second returned an error, "The term 'SelectObject' is not recognized as the name of a cmdlet, etc..
0
 
LVL 14

Expert Comment

by:Todd Nelson
Comment Utility
Sorry... Use "select-object" instead.
0
 

Author Comment

by:daskas27
Comment Utility
Yes. It shows me the same thing the message queue shows. a bunch of 421 4.4.2. connection dropped errors.
0
 
LVL 14

Expert Comment

by:Todd Nelson
Comment Utility
How is outbound mail flow configured for your environment?

Exchange >> Smarthost >> Firewall >> Internet?
Exchange >> Firewall >> Internet?
Exchange >> Firewall >> Smarthost >> Internet?

Do you have some sort of content filter between Exchange and the external recipients?

I'm going to ask again ... Can you perform a successful telnet outside of your network from the Exchange server?  Don't check from the firewall.  Check from the Exchange server.
0
 

Author Closing Comment

by:daskas27
Comment Utility
Thank you. It was actually the firewall configuration.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Resolve DNS query failed errors for Exchange
"Migrate" an SMTP relay receive connector to a new server using info from an old server.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video discusses moving either the default database or any database to a new volume.

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now