"Todd J Heron" <todd_heron_no_spam@hotmail.com> wrote in message
news:%232eGzb0MFHA.1436@TK2MSFTNGP10.phx.gbl...
> "ISAjack" <ISAj***@discussions.microsoft.com> wrote in message
> news:608F233A-C8EA-4391-BAAF-40032DC21393@microsoft.com...
> >I have installed Exchange Server 2003 on a computer that I have named
> >"server" (the full name is server.yacek.local). In front of "server" I
have
> >an ISA server that has a static IP.  I also have a registered domain name
> >(yacek.net).  How should the MX record at my ISP look like?
>
> The A record maps a name to an IP.  The MX record maps what's known as the
> mail exchanger to fully-qualified host name of the server providing SMTP
> services for your domain.   This could be a mail server reachable directly
> on the Internet (such as inside a DMZ) or could simply be the external IP
of
> a gateway device (such as a router/firewall/ISA server) which is
> port-forwarding SMTP requests inside the network perimeter to the mail
> server.  So basically it's just a record typed mapped to a fully-qualified
> host name.  This fully-qualified host name must in turn be resolvable
based
> on a regular A record for that fully-qualified name.  It's a two-part
> process.
>
> .local is not a valid TLD yet on the Internet (and may never be although
> it's possible in the future).   You'll need to register an actual TLD with
> your Registrar first before your mail server can be "seen" on the
Internet.
> If you domain name was yacek.com, with a mail server named

> you would need two records in DNS zone yacek.com which looked like this:
>
> (Same as parent folder)     Mail Exchanger(MX)  [10] server.yacek.com
> server                                Host (A)                     <static
> IP>
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> --------------------------------------------------------------------------
--
> This posting is provided "as is" with no warranties and confers no rights
>

"Bill" <william.d.sherw***@verizon.net> wrote in message
news:etNm2isNFHA.2356@TK2MSFTNGP14.phx.gbl...
> Could I ask a follow-up to this?  This thread is the "Setup" to the
problem
> we're having:
>
> Since the server's internal name and domain are server.yacek.local, then
> *that* is what will appear in the header for all outgoing messages to the
> internet.  My understanding is that if you are sending email to a server
> that requires a successful reverse ns lookup before they will accept you
> email, then the server.yacek.local name in the header will not provide
that
> successful reverse lookup because it doesn't match the server.yacek.com
(or
> mail.yacek.com) entry in DNS.  Is there a way to force the server to
present
> the server.yacek.com name so the reverse lookup is successful?  I ask
> because we apparently have several customers with AOL email addresses and
I
> am constantly hearing from salesmen and detailers that cannot mail those
> customers.  It all bounces back to us.
>
> Thanks for any suggestions/help.
> Bill
>
> (Sorry to but into your thread - but I figgered it might help us both).
>
>
> "Todd J Heron" <todd_heron_no_spam@hotmail.com> wrote in message
> news:%232eGzb0MFHA.1436@TK2MSFTNGP10.phx.gbl...
> > "ISAjack" <ISAj***@discussions.microsoft.com> wrote in message
> > news:608F233A-C8EA-4391-BAAF-40032DC21393@microsoft.com...
> > >I have installed Exchange Server 2003 on a computer that I have named
> > >"server" (the full name is server.yacek.local). In front of "server" I
> have
> > >an ISA server that has a static IP.  I also have a registered domain
name
> > >(yacek.net).  How should the MX record at my ISP look like?
> >
> > The A record maps a name to an IP.  The MX record maps what's known as
the
> > mail exchanger to fully-qualified host name of the server providing SMTP
> > services for your domain.   This could be a mail server reachable
directly
> > on the Internet (such as inside a DMZ) or could simply be the external
IP
> of
> > a gateway device (such as a router/firewall/ISA server) which is
> > port-forwarding SMTP requests inside the network perimeter to the mail
> > server.  So basically it's just a record typed mapped to a
fully-qualified
> > host name.  This fully-qualified host name must in turn be resolvable
> based
> > on a regular A record for that fully-qualified name.  It's a two-part
> > process.
> >
> > .local is not a valid TLD yet on the Internet (and may never be although
> > it's possible in the future).   You'll need to register an actual TLD
with
> > your Registrar first before your mail server can be "seen" on the
> Internet.
> > If you domain name was yacek.com, with a mail server named
> server.yacek.com,
> > you would need two records in DNS zone yacek.com which looked like this:
> >
> > (Same as parent folder)     Mail Exchanger(MX)  [10] server.yacek.com
> > server                                Host (A)
<static
> > IP>
> >
> > --
> > Todd J Heron, MCSE
> > Windows Server 2003/2000/NT; CCA
>
> --------------------------------------------------------------------------
> --
> > This posting is provided "as is" with no warranties and confers no
rights
> >
>
>