[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] MX with External Mail Server
- Subject: RE: [cobalt-users] MX with External Mail Server
- From: "Jay Fesco" <jay@xxxxxxxxxxxx>
- Date: Wed May 23 21:30:05 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
<SCHNIP>
> Why an MX to mail.domain.com for www.domain.com?
> Why not an MX to mail.otherdomain.com for domain.com?
My line should have read 'mail.domain.com for domain.com'.
> On my RaQ2 I have a domain pointing the domain.com MX to
> sitemail.everyone.net and the site is set to accept mail for the domain.
No
> problems.
</SCHNIP>
My assumption (probably bad, but I couldn't spend more time on it than I
already had) was that since their internal server is set up to expect mail
to 'somebody@xxxxxxxxxx' I needed to make the domain name consistent in my
DNS.
We inherited this site and mail config from a previous vendor, and the
Website domain and Exchange Server internal domain definition were already
set up with the same domain.com name.
I think what you are saying is that it doesn't matter what I 'name' the A
record in my DNS for the external mail server as long as the IP address is
correct. Once I found that the problem was in 'accepting mail' for the
domain on my server and corrected that, I left it alone (the old 'it ain't
broke' axiom). So now I have a (possibly) confusing setup where an A record
that 'looks' like an internal domain actually points outside of my server.
I could have named it 'Fred' and it would work as well - correct?
Thanks, Dan!
Jay Fesco