Link to home
Start Free TrialLog in
Avatar of Snowbella Kilangit
Snowbella Kilangit

asked on

No MX records were found in DNS for SMTP domain

The remote connectivity analyser gives this message..."No MX records were found in DNS for SMTP domain". What does this mean and how can I resolve?
Avatar of John
John
Flag of Canada image

Are you using Exchange?   Two tools to use are:

1.  http://mxtoolbox.com/  (MX Toolbox)  and

2 http://www.intodns.com/  (Into DNS

You may need your ISP to set up the record for you. Make a request to them.
Avatar of Snowbella Kilangit
Snowbella Kilangit

ASKER

I used mxtoolbox and this is the result : "Loop detected! We were referred back to 'ip address"

And www.intodns.com came back with a whole bunch of information

This was working fine until recently. Does this mean ISP has changed /removed records?
Does this mean ISP has changed /removed records?

That is a possibility. They should not have without notifying you. But the ISP manages these records, so you should ask them.
By the way internal email works fine and we can send email out to the internet, but not receive email from the internet

I am also waiting on response from registry as the domain expired. But apart from that...is there anything else I am missing
You should get the domain back in order before contacting the ISP. That could be the reason the MX records were removed.
Thank you, I will wait to get the domain back.

Just additional information, the exchange server is in-house not at the ISP...what else do I need to do to confirm, mx records were not removed by another disgruntled admin user?

Thank you in advance
I have serviced in-house Exchange but had to work through the domain supplier to implement the MX records.

Confirm with the domain that you (and only you in IT) and perhaps the business manager are the only people who can change MX or other ISP records (SPF records come to mind).
Ok thank you so I will wait to take back the domain, talk to the isp to see if they removed the mx records.

How about the configuration in the in-house exchange server, how can I check nothing has changed there or on the DNS Server?
The server will look to / see the information kept by the domain. So long as it is set up with proper mail address, it should work.

Once the ISP has put back the records, look at MX Toolbox and Into DNS again to see if anything is missing. Not likely, because (s you said) it was working.
Thank you I will check and post back here
ASKER CERTIFIED SOLUTION
Avatar of David Johnson, CD
David Johnson, CD
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Because the domain is expired the registrar can sell it to someone else  

As long as you are quick, you can normally get the domain back. A reputable domain holder will wait (sometimes as long as 30 days). So even though it is not working (which is why we identified way back the reason for the MX record being disabled), you should be able to get your domain back and get working again in short order.
Thank you David and John.

The old incumbent had the renewal reminders sent to his private email. I had no access. I have changed all this. Registrar is waiting on Registry for a response...thats where its at, at the momen

Yes that is what I intend to do now pay for 5 to 10 years.

I will check with the ISP as suggested

I was just wondering if there was something else I needed to check in-house...that may have changed.
All that you have to do is once your domain is back in control to setup the dns records.. Why they have to go to IANA I have no idea they must be a fly-by-night operation I would consider transferring the domain in 60 days
Thank you David
to receive email the sender looks for MX , so if MX is not found no mail wil be delivered.

again us lookup tool to determine if MX exists - go to http://www.dnsstuff.com/

and choose Domainreport - fill in your domain as found on the internet.
oeps I gave missed the passage where domain was expired .... sorry