Gmail hosted business accounts DNS Fail error trying to deliver

This is an odd problem we are currently having with just Gmail business accounts. We are having no issues receiving email from any other domains. These hosted business accounts are all getting this error:

DNS Error: 5253683 DNS type 'mx' lookup of domainname.com responded with code SERVFAIL

What's even more odd is that some of the mailboxes from a hosted account can email us while others can't.

Our domain record on MXTOOLBOX doesn't show any obvious errors with our DNS.

Our email is hosted by a cloud service.
supportmailAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AlanConsultantCommented:
Hi SupportMail,

Please can you describe in more detail what is happening here.

You state that, 'We are having no issues receiving email from any other domains.' so it appears you are talking about receiving emails from correspondents who are using Gmail to host their email.

However, you also talk about a DNS error which implies that you are talking about sending email out - presumably to correspondents that are using hosted Gmail?

Please can you clarify, as your statements appear to directly contradict each other, but I am presumably just misunderstanding.

Thanks,

Alan.
0
supportmailAuthor Commented:
Issue is just receiving email from Gmail hosted business accounts, and not all accounts. Some come in just fine, even from the same domain. One users email delivers and another's doesn't from the same hosted  account.

This is the error they are getting.

DNS Error: 5253683 DNS type 'mx' lookup of domainname.com responded with code SERVFAIL

We are sending emails with no issue to any domain. Sorry for the confusion.
0
AlanConsultantCommented:
Hi SupportMail,

So you are saying that a correspondent is using hosted Gmail, and trying to send email to you.

They are getting a delivery failure report, and it includes the line:

DNS Error: 5253683 DNS type 'mx' lookup of domainname.com responded with code SERVFAIL 

Open in new window


If so, what do you get when you do a lookup of your DNS records using Google's DNS (8.8.8.8)?

What do you get for MXs and TXT records (SFP etc)?

Do they differ from what your authoritative nameserver(s) give out?

Alan.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

supportmailAuthor Commented:
Doing an MX Lookup using Nslookup for the Google DNS shows exactly what it should.

mydomain.com    MX preference = 30, mail exchanger = us-smtp-inbound-2.mimecast.com
mydomain.com    MX preference = 10, mail exchanger = us-smtp-inbound-1.mimecast.com

This is all that returned using set q=mx

Using MXtoolBox.com gives DNS Record Published but not found.

This is DNS check using MXToolbox

NS ns.mydomain.com 168.85.177.85
AT&T Services, Inc. (AS7018)
11 hrs   56      
NS ns2.mydomain.com 168.85.177.75
AT&T Services, Inc. (AS7018)
11 hrs   52      
NS ns3.cl.bellsouth.net 205.152.32.8
BellSouth.net Inc. (AS6389)
       
NS ns2.cl.bellsouth.net 205.152.16.8
BellSouth.net Inc. (AS6389)
       
NS ns1.cl.bellsouth.net 205.152.0.8
BellSouth.net Inc. (AS6389)
         
Result

 At least one name server failed to respond in a timely manner
Failure detail: 205.152.244.188 <br/>Failure detail: 205.152.144.188 <br/>Failure detail: 205.152.0.8   More Info  
 Local NS list does not match Parent NS list
205.152.32.8 was reported by the parent, but not locally<br/>205.152.16.8 was reported by the parent, but not locally<br/>205.152.0.8 was reported by the parent, but not locally  More Info  
 Name Servers are on the Same Subnet
168.85.177  More Info  
 SOA Serial Number Format is Invalid
ns.mydomain.com reported Serial 467943698 : Suggested serial format is YYYYmmddss where ss is a two-digit sequence number within the day.
0
AlanConsultantCommented:
Hi SupportMail,

Apologies for the delay in getting back to you.

I am wondering if it was just a timing issue, and the DNS records have now propogated fully,

Please can you retry your lookup on MXtoolBox.com and see if they are now correct?

If you want me to test from here, either post your actual domain name here, or feel free to send it to me privately, and I will test from my end to see what I get.


Thanks,

Alan.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
supportmailAuthor Commented:
AT&T had two new DNS zone servers that they never told us about. We updated those and we are good to go.
0
AlanConsultantCommented:
Great - Glad to hear its all okay now.

Don't forget to close the question.

Thanks,

Alan.
0
supportmailAuthor Commented:
AT&T finally got back to us and said they had two other zone servers we needed to update.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Clients

From novice to tech pro — start learning today.