Tonygret
asked on
MX records, local Mail Server and web being Moved
I have a mail server located in the physical building of the domain and want to move it off site. By that I mean I have a mail server abc.com and a domain abc.com that also manages DNS (active directory). I do not have any MX records set up in my domain because when email is sent from any user it goes directly to the in house/ on site mail server.
I am moving the mail server off site for various reasons. My question is, when we make the change to the off site server, how do I make the MX record point outside the domain? Is it as simple as creating an MX record in DNS and pointing to the new IP?
I also want to make the http: web traffic for abc.com go to the new server as well. I am not sure how to do this since all PCs in the domain point to abc.com for DNS and Active Directory.
Thank you in advance for your help!!!
I am moving the mail server off site for various reasons. My question is, when we make the change to the off site server, how do I make the MX record point outside the domain? Is it as simple as creating an MX record in DNS and pointing to the new IP?
I also want to make the http: web traffic for abc.com go to the new server as well. I am not sure how to do this since all PCs in the domain point to abc.com for DNS and Active Directory.
Thank you in advance for your help!!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
acbrown,
That makes perfect sense. The clients are indeed connecting directly to the server which i already named mail.abc.com and I added the local and internet dns A records to point to mail.abc.com for pop and smtp connections.
For http traffic, the new A record www.abc.com makes sense also. I will simply redirect internal requests for abc.com to the www.abc.com using IIS redirect. I think that should solve both probelms.
Thank you!
That makes perfect sense. The clients are indeed connecting directly to the server which i already named mail.abc.com and I added the local and internet dns A records to point to mail.abc.com for pop and smtp connections.
For http traffic, the new A record www.abc.com makes sense also. I will simply redirect internal requests for abc.com to the www.abc.com using IIS redirect. I think that should solve both probelms.
Thank you!
There is no consistency at MS for the TLD recommendation. The SBS people push for "local",..while others do not. Some are strongly opposed to it,...and others don't care either way. "Local" is not actually an official reserved name,..many think it is, but it is not. There is an official list, and it is very short.
.test
.example
.invalid
.localhost
Reserved Top Level DNS Names
http://www.ietf.org/rfc/rfc2606.txt
TLDs such as "local" have been known to cause problems as far up the food chain as the Root Servers due to the names being allowed to "leak" to the Internet. Older MAC OS's also could not handle a TLD longer than 3 characters.
The philosophy is actually shifting to using registered names in AD even if you don't actually have the name exposed anywhere publicly. Then you never have to worry about any name conflicts in FQDNs between internal AD name choices and Public Name choices.