C Y
asked on
Does exchange need MX records configure in internal DNS?
Hi expert,
I'm planning migration to migrate mdaemon into exchange 2016.
My current email environment has a mail gateway that act as edge server and redirect email into mdaemon server, in Internal DNS they have a MX records point to mdaemon internal IP with mdaemon.company.com.
For my exchange 2016, in order to work properly, do i need to add MX records for exchange server as well? fyi, i have setup autodiscover in both internal and external DNS, using microsoft test analyzer they seem to be working properly... do i still need to setup the MX records?
FYI, in future the mdaemon ip will be used by exchange server..
any advise much appreciated!
I'm planning migration to migrate mdaemon into exchange 2016.
My current email environment has a mail gateway that act as edge server and redirect email into mdaemon server, in Internal DNS they have a MX records point to mdaemon internal IP with mdaemon.company.com.
For my exchange 2016, in order to work properly, do i need to add MX records for exchange server as well? fyi, i have setup autodiscover in both internal and external DNS, using microsoft test analyzer they seem to be working properly... do i still need to setup the MX records?
FYI, in future the mdaemon ip will be used by exchange server..
any advise much appreciated!
Agree with Mahesh
You ONLY need MX records for delivering E-mail with a server that is not in the domain that is intended to receive E-mail.
If you need to receive SMTP mail:
mail@example.com to be delivered at mailserver.example.org (A record)) needs an MX record in example.com
mail@example.org to be deliverd at mailserver.example.org (A record) needs an MX record in example.org
mail@example.net to be delivered at example.net (A record)
Any local system already connecting to mailserver.example.org to start a mail session does not need an MX record.
(MX records are used by SMTP servers to find other servers responsible for a domain.)
If you need to receive SMTP mail:
mail@example.com to be delivered at mailserver.example.org (A record)) needs an MX record in example.com
mail@example.org to be deliverd at mailserver.example.org (A record) needs an MX record in example.org
mail@example.net to be delivered at example.net (A record)
Any local system already connecting to mailserver.example.org to start a mail session does not need an MX record.
(MX records are used by SMTP servers to find other servers responsible for a domain.)
One addition ... You don't need an MX, but you might need an AutoDiscover
Ah that depends on what tries to connect... Outlook etc. need Autodiscover.
Non microsoft tools will largely ignore autodiscover. And may need correct naming and/or MX.
Non microsoft tools will largely ignore autodiscover. And may need correct naming and/or MX.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Your edge servers are used to receive email from internet, so in public DNS you must be having MX pointing to edge server
For mail flow between Exchange and MDaemon internal smtp connectors would be required which can directly talk with each other
U don't need MX in internal network for that