Solved

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

Posted on 2008-06-19
7
223 Views
Last Modified: 2013-12-05
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
Comment
Question by:Jlipko
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 71

Accepted Solution

by:
Chris Dent earned 500 total points
ID: 21823330

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
 
LVL 1

Author Comment

by:Jlipko
ID: 21832098
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
 
LVL 71

Expert Comment

by:Chris Dent
ID: 21832437

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

What do they get the bounce message?

Chris
0
Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

 
LVL 1

Author Comment

by:Jlipko
ID: 21833213
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
 
LVL 71

Expert Comment

by:Chris Dent
ID: 21833917

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
 
LVL 1

Author Comment

by:Jlipko
ID: 21875211
I am still waiting on some of those block to run the nslookup and telnet test, I'll let you know the results.
0
 
LVL 1

Author Comment

by:Jlipko
ID: 38386981
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

MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Occasionally you run into the website or two that will not resolve properly using your own DNS servers.  Some people simply set up global forwarders for their DNS server.  I don’t recommend doing this because it can cause problems resolving addresse…
On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
In an interesting question (https://www.experts-exchange.com/questions/29008360/) here at Experts Exchange, a member asked how to split a single image into multiple images. The primary usage for this is to place many photographs on a flatbed scanner…

730 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