oursite.net has no MX record

Posted on 2009-12-23
Medium Priority
Last Modified: 2012-05-08
After we upgrading from Domino to Exchange 2007, the MX record in DNS to the new server was overlooked until today.  The MX record was deleted for the old server and a new one added for the new server to the DNS.  We are concerned as "there is not parent MX folder" (our AD admin reference).  He tried force replicating and that did not resolve.  

> host -t mx oursite.net
oursite.net mail is handled by 10 oldsername.oursite.net

# our AD admin made change in the DNS
> host -t mx oursite.net
oursite.net has no MX record
(tried flushing nslookup, same result)

Anyone experience this or know the solution?

Thank you,
Question by:hdgh
  • 2
  • 2

Expert Comment

ID: 26116100
I may be going about this the wrong way, so if I am, just ignore me.  There is a 24-48 hour delay for external DNS records to update, so it may take some time for the change to process depending on the DNS server you hit in your query.  How long ago did you make the change?

Expert Comment

by:Mark Pavlak
ID: 26116134
To be quite honest I would not be concerned about this.  an MX record as it is used for mail delvery, is primarily used for external resolution or server to server comms.  Internally your email client and server ie exchange and outlook will find each other via a records.  as long as you have an a record for the new exchange server then you should not have any problems.

Author Comment

ID: 26116809
thanks for the replies guys !

The record was changed on the internal DNS so the change should be instantaneous.   Our external MX records are good.

The concern is for our internal *NIX server and IBM i ( as/400) servers.

Are we just being too paranoid ?

Expert Comment

by:Mark Pavlak
ID: 26119761
Maybe and maybe not.  If the AS 400's are end mail by domainlookup via an smtp service then no you are not.  If it is sending mail via being told a DNS/IP name then yes you are.  If the case is the latter then the server will know its mail server and will communicate via what ever port is configured (25 of course is the standard) and the mail server is going to listen on that port.  Hope this helps

Accepted Solution

hdgh earned 0 total points
ID: 26206644
our Ad admin informed me that this is no longer an issue. It appears our DNS just took an aweful long time to update ( sounds like someone has homework to do !!).

Thanks for the replies

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Question has a verified solution.

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

If you have come across a situation where you need to find some EDB mailbox recovery techniques, then here you will find the same. In this article, we will take you through three techniques using which you will be able to perform EDB recovery. You …
Transferring FSMO roles is done when an admin wants to split roles between certain Domain Controllers or the Domain Controller holding the Roles has been forcefully demoted using dcpromo / forceremoval
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
Suggested Courses

839 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