Avatar of flynny
flynny
Flag for United Kingdom of Great Britain and Northern Ireland asked on

why change remote.domain.com mx record

Hi all,

Just a quick question.

I had a client asking for their remote.domain.com mx record to be change to point to remote.domain.com

Why would they need to or want to do this? because the mail.domain.com is pointint to a different IP address?

Their IT guy is not very helpful and I was wondering out of interest?
NetworkingSBS

Avatar of undefined
Last Comment
flynny

8/22/2022 - Mon
strivoli

There might be 3 reasons:
a. If the resulting IP changes and they didn't change ISP (for example) then they want to receive mail on another server.
b. If the resulting IP changes and they changed ISP then they need to change the IP in order to continue receiving mail on the same server.
c. If the resulting IP DOESN'T change then they might want to clear out their naming convention.
David Atkin

Hello,

Its probably so that Exchange passes the reverse DNS checks.
duncanb7

it might be the reason he wants his email delivery process done  internally within
its organization.

Take a look at this article
http://smtp25.blogspot.hk/2007/07/can-you-run-mail-server-without-mx.html

Hope understand your question completely, if not , please point it out


Duncan
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
donnk

Could be few reasons:

1. SSL Certificate
2. Redundancy (multiple MX records)
3. 1 less DNS record to worry about.
4. Reverse DNS (spam check)as Scorpeo says.
5. The IT guy likes messing with you!!
flynny

ASKER
Thanks guys,

the mail.domain.com is pointing to IP A
with MX record pointing to this server as its the mail server


whilst remote.domain.com has been changed to point to IP
with the mx pointing to this server.

regarding the answers;

1. SSL Cert? Why would pointing the MX record back here help with this please?

2. Redundancy - Again why would this be the case?

4. Reverse DNS I Can see why but this is not the mail server?

Thanks in advance guys.
SOLUTION
David Atkin

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
donnk

"2 - It wouldn't truely be redundant.  The record would but if its pointing to the same place so wouldn't help in the event of their server being down."

Not necessarily, could be multiple mail servers behind that IP with the firewall deciding which to deliver too.


Is the mail server an exchange box ?
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
David Atkin

@Donnk - Good point, I hadn't thought of that.
flynny

ASKER
the mail server on mail.domain.com and IP a is a SBS running an exchange mail server and handling all of the sites mail.

I'm not sure what the secondary site could be. The SSL would make sense if the remote wasn't pointing to the second IP.

Scorpeo, regarding point 3 - what use would haveing an mx record setup for a web server hold?
ASKER CERTIFIED SOLUTION
David Atkin

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
flynny

ASKER
many thanks guys.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23