• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 233
  • Last Modified:

After DNS reset not all domains can send email to our Domain, why?

Hello,
I had to reset my DNS for some changes lately twice. I had a third party create a new web-site for the company and after an entire weekend on their DNS server we almost received no email. I switched it back to the old DNS servers (Register.com) and email started coming in slowly. Now it has been 2 weeks and DNS report and Register.com see that our DNS is working fine, but I still have a few clients that can not email the company(of course our big clients) . Our email does reach them with no issues, but their email never reaches us. Any ideas?
Thanks for any help!
Jim
0
Jlipko
Asked:
Jlipko
  • 4
  • 3
1 Solution
 
Chris DentPowerShell DeveloperCommented:

Hi Jim,

You'd need to see what they're resolving the MX records to (or indeed if they're resolving them at all).

If the MX is resolving correctly connectivity to Port 25 on your mail server should be tested (from theirs).

Chris
0
 
JlipkoAuthor Commented:
Here is info from someone who can not email us, I don't see what is wrong.



Results for nslookup  -querytype=mx pahutch.com

 

Server:  ns3.hisemailserver.net
Address:  64.7.11.21




Non-authoritative answer:

pahutch.com     MX preference = 0, mail exchanger = mail.pahutch.com

pahutch.com     MX preference = 5, mail exchanger = mail2.pahutch.com

 

pahutch.com     nameserver = dns249.d.register.com

pahutch.com     nameserver = dns107.a.register.com

pahutch.com     nameserver = dns109.b.register.com

pahutch.com     nameserver = dns237.c.register.com

mail.pahutch.com        internet address = 209.74.14.199

mail2.pahutch.com       internet address = 209.74.14.200

dns109.b.register.com   internet address = 216.21.232.109

dns249.d.register.com   internet address = 216.21.236.249

 

Results for Nslookup mail.pahutch.com

 

Server:  ns3.hisemailserver.net
Address:  64.7.11.21

 

Non-authoritative answer:

Name:    mail.pahutch.com

Address:  209.74.14.199

 

The telnet results were both 220
0
 
Chris DentPowerShell DeveloperCommented:

That doesn't give them much excuse :) Can they successfully send to you now then?

What do they get the bounce message?

Chris
0
Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

 
JlipkoAuthor Commented:
Thanks Chris,
They can not send to us nor can a few other clients - this particular client subs out their email but from the nslookup and the telnet it appears to be fine.  However maybe their providers DNS is cached (holding the old DNS Server numbers)?  Just a guess.  I am going tosee if there is a common issue with third party email services with the other clients that can't email us.
Thanks, Jim
0
 
Chris DentPowerShell DeveloperCommented:

Okay Jim, that seems a good enough approach :)

From what you've got above everything looks fine in DNS. Getting hold of a few NDRs would be extremely useful. Have you been able to reproduce the issue from another mail provider at all (Gmail, Hotmail, etc)?

You can find some fairly odd behaviour with those large web mail services as they cache MX records for a lot longer than normal. Makes it a little bit intolerant of change, but "a lot longer" is a few days longer, rather than weeks.

I did check the DNS configuration whe you first posted, nothing is wrong. All delegations are correct and all MX records are consistent.

Chris
0
 
JlipkoAuthor Commented:
I am still waiting on some of those block to run the nslookup and telnet test, I'll let you know the results.
0
 
JlipkoAuthor Commented:
Update:  This was never resolved I ended up hosting the Website.  Then last year we had another company create a new site and we host it at Hostgator.com and have had no issues with DNS.  I am guessing the other hosting company redirected all of our ports not just port 80.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now