Re: more than two MX record

Sorry, that's my mistake.... I read mail.mydomain.com and
mailbox.mydomain.com as 2 separate domains.... :)

1 domain, 2 MX records.
2 possible scenarios:
1) both MX records have same preference number (10 for instance)
2) new MX record has a higher preference

In case #1 above, traffic will be load-balanced between the 2 (dns
round-robin) - that's not something you want.

In case#2, the new MX record will only be used as a failover when the first
one doesn't respond. You don't want either.

Take a step back from the MX record approach....

What you want is for the mail host from a particular domain send all
messages to a particular IP address that'll bypass your filters. In this
case, you should talk to the postmaster/mail admin from the sending domain
and have them configure it so. If they're using Exchange, they can simply
create a SMTP Connector for your domain, and deliver mail to the second IP
address (insert the IP address or fqdn as a smarthost on that Connector). If
they're using other MTAs like Postfix, it is just as easily accomplished.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"naguaramipana" <naguaramipana@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D2FE575E-22B0-4F9A-B3EC-60EE3C9740B3@xxxxxxxxxxxxxxxx
B

Thanks for battle with me on this.

I only have one domain(mydomain), my MX record is mail.mydomain.com, I
think this is pretty standar.-

I would like to create another MX record mailbox.mydomain.com to point to
the second ip address and therefore to my router number two

Thanks

"Bharat Suneja [MVP]" wrote:

If you are using separate domains as you explained, it'll work. The
customers needing to bypass the filter will need to send to the second
domain that can directly send messages to your Exchange server. On your
server, you will need to create Recipient Policy for that domain so
Recipients have the necessary email addresses from the new domain as
proxyAddresses.

However, given this scenario, when your internal Recipient replies to an
email, it will go out using the default email address, irrespective of
which
email address it was received on. When remote Recipients reply to those
responses, they will go to the default email address domain, and thus be
subjected to the filters.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"naguaramipana" <naguaramipana@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:08267493-D1C4-4BB0-AA9C-C1646597B4B8@xxxxxxxxxxxxxxxx
B.

Thanks
so in other words the following scenario wont work

on my ISP site
MX record mail.domain.com->xxx.xxx.xxx.xx1
MX record mailbox.domain.com ->xxx.xxx.xxx.xx2
on my site
router #1 xxx.xxx.xxx.xx1->spam firewall-> exchange server
router #2 xxx.xxx.xxx.xx2->exchange server

client side
outgoing server mailbox.domain.com
incoming server mailbox.domain.com

every other client
outgoing preferred ISP
incoming preferred ISP
pointing of course to mail.domain.com

please advise

"Bharat Suneja [MVP]" wrote:

Don't think most MTAs have any support for using specific MX records,
so
as
posted earlier I don't think that particular approach will work.

All you need to do is allow your router to forward SMTP traffic
inbound
on
the second/new IP to the Exchange server directly, then have the
postmaster
in the sending organization hard-code that in their system - you can
do
it
by IP address or insert an A record mapping to that IP address in your
external DNS. If the sending domain is using Exchange, all they need
to
do
is set up an SMTP Connector for your domain, and specify the second IP
address/fqdn as a smarthost.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"naguaramipana" <naguaramipana@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:8961B913-1830-47CC-A3E6-617539EFA85F@xxxxxxxxxxxxxxxx
B.

Thanks for the prompt reply.

here is were I am.- I have two static public ip from my isp, then I
have
two routers one for each ip address, my isp holds my external dns
and
Mx
record.

1) my now in service MX record mail.domain.com points to router
number
one
and from here my router sends all email for my domain to a spam
firewall
and
from here all goes to my exchange server
2) I want certain user outside my network to use a second MX record
mailbox.domain.com and get that mx record pointing to my second IP
address
which goes to the second router and from here directly to my same
exchange
server.

is this possible, what do you think

Thanks


"Bharat Suneja [MVP]" wrote:

Yes, you can add an additional A record mapping another fqdn to the
second
IP, and point a new MX to it.

What are you trying to accomplish with this?

- If you add this with the same priority/preference number as the
existing
one, these will load-balance (DNS round-robin). h
- If you add the second one with a higher number, mail will only be
routed
to it if the first one fails.

If the outside user wants to send to the second/new IP address, it
will
need
to be hard-coded in the sender's environment - if they use
Exchange,
they
will need to setup a SMTP Connector for your address space and
specify
the
second/new IP as a smarthost.

In that case, you do not need to add a new MX record (which will
allow
outside email to bypass your spam firewall at some point.. ).

Perhaps a better way to do this:
- Create an additional SMTP virtual server for that org, mapping
the
second
external IP address to it on your firewall
- Create smtp/ip filters to accept connections only from that Org's
ip
address(es)
- Optionally, set up SMTP authentication on the VS

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
www.exchangepedia.com/blog
----------------------------------------------


"naguaramipana" <naguaramipana@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:4894FB49-941B-418B-8D37-FDC05FED8E77@xxxxxxxxxxxxxxxx
Hi gurus

I have and exchange 2000 server, two statics ip, two routers.-
each
router
has it own Ip address.- my mx record points to one of my public
IP
and
all
email comes through this using one of my router, then my router
push
all
email to my spam firewall and my firewall push those emails to
my
exchange
server.

I want some of my outside user to send email using the other
router
and
bypass my spam firewall.
do I just create another MX record pointing to the next static ip
and
use
my
router to forward those email directly to my exchange server

my MX record mail.domain.com can I create the second MX record
like
mailbox.domain.com and route this to exchange directly. let my
user
know
what
the incoming and outgoing server mx record is?


Thanks guys












.

Relevant Pages

  • Re: more than two MX record
    ... the second ip address and therefore to my router number two ... domain that can directly send messages to your Exchange server. ... outside email to bypass your spam firewall at some point.. ...
    (microsoft.public.exchange.admin)
  • Re: Advice needed - running Exchange
    ... the router to your nic ... You'll need to have your ISP create two additional DNS records for your ... delivery is set to the Exchange mailbox, ... I currently only have one NIC in my SBS server ...
    (microsoft.public.windows.server.sbs)
  • Re: more than two MX record
    ... domain that can directly send messages to your Exchange server. ... All you need to do is allow your router to forward SMTP traffic inbound ... outside email to bypass your spam firewall at some point.. ...
    (microsoft.public.exchange.admin)
  • Re: External interface on Exchange 2003
    ... the router once it's done. ... Exchange 5.5 in the environment. ... move everything over to the new server. ... up to the external interface is forwarding everything to the W2k box (I ...
    (microsoft.public.exchange.admin)
  • Re: more than two MX record
    ... outgoing server mailbox.domain.com ... outgoing preferred ISP ... All you need to do is allow your router to forward SMTP traffic inbound on ... If the sending domain is using Exchange, ...
    (microsoft.public.exchange.admin)