Re: Split domain routing or masking?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Sorry, what you're trying to accomplish, or at least the way you want to
(conditional message routing based on IP address returned by DNS) doesn't
make sense to me.

I would recommend the SMTP Connector approach by adding adding address
spaces for which mail should be forwarded to securewan.com.

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


"Jay" <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C8FCE9F-0239-4CC1-B805-62470021F2A8@xxxxxxxxxxxxxxxx
I might have to rehash the question to be more clear ;)

I believe the key lies in that the SECUREWAN.COM DNS has records for all
the
dedicated links to all the other organizations... therein we can somehow
set
our Exchange server to query the SECUREWAN.COM DNS... if it returns a
10.10.x.x address, then route mail here. Otherwise, route it through the
Internet. That's a concept, but how, if possible, can it be executed?
Other
ideas?

Simple diagram: http : //img124.imageshack.us/my.php?image=networklr5.gif

[ Remove Spaces From Link ]

"Bharat Suneja [MVP]" wrote:

Don't see how you could tell Exchange to route messages for a certain
(I'm
assuming physical) network to certain hosts, without consideration for or
actually knowing which address spaces. Exchange/SMTP don't care about the
network, just the address spaces and where to route them to. Either it's
DNS
or routed to specific hosts.

Unless you have domain.SECUREWAN.com, domain2.SECUREWAN.com - then you
can
route *.securewan.com.

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


"Jay" <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6A284FC5-A850-4DD7-879B-793E33387D4C@xxxxxxxxxxxxxxxx
Right but this would require an entry for every domain and subsequent
domain
in the SECUREWAN.COM network... a lot of work when the number of
organizations increase?

Again, the idea is that email sent to any domain part of the
SECUREWAN.COM
network is routed through SECUREWAN.COM. The domains themselves are
actual
routable addresses so by default they will be routed through the
internet...
and we wouldn't want that.

"Bharat Suneja [MVP]" wrote:

Not sure what you mean by "masked".
To route outbound mail for particular destination domains to a
particular
server/set of servers, create a SMTP Connector, add the destination
domains
in the Address Space, add destination host(s) as smarthost(s).

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


"Jay" <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:75A01151-95C3-485C-BC53-7C29349F28ED@xxxxxxxxxxxxxxxx
I would like suggestions to see if this is feasible or possible by
any
means...

My W2K3 organization has a primary domain of MYOWN.COM. All mail is
handled
through and Exchange 2003 server. Now I would like to coop with a
network
called SECUREWAN.COM.

SECUREWAN.COM consists of several other conglomerates like
HISOWN.COM
and
HEROWN.COM.

SECUREWAN.COM has their own domain/DNS/etc.

I would like this to happen... mail going to the SECUREWAN.COM users
like
HISOWN.COM and HEROWN.COM are ALWAYS routed to the SECUREWAN.COM
network
and
masked. For example, user BOB@xxxxxxxxx emails to
SHELLY@xxxxxxxxxxxxx
the
mail would not go through the internet but directly through to
SECUREWAN.COM
network... the email becomes from BOB@xxxxxxxxxxxxxxxxxxx and goes
effectively to SHELLY@xxxxxxxxxxxxxxxxxxxxx When SHELLY@xxxxxxxxxx
replies
to
that email or anyone else part of the SECUREWAN.COM conglomerate
emails
us,
it passes through the SECUREWAN.COM network and the sender email is
masked
accordingly.

Is this possible/feasible, and if so, any concepts on how to
accomplish
this
without modifying existing infrastructure? I have thought of
leveraging
the
DNS server in the SECUREWAN.COM but not certain how. My firewall can
effectively route emails based on sender. I can possibly make
SECUREWAN.COM
do the masking, but the point is any emails to the conglomerates
should
pass
through the SECUREWAN.COM and dropped/queued otherwise. All other
outgoing/incoming mail not for/from the conglomerates will be going
through
the internet. Any ideas?






.

Relevant Pages

  • Re: Split domain routing or masking?
    ... I believe the key lies in that the SECUREWAN.COM DNS has records for all the ... our Exchange server to query the SECUREWAN.COM DNS... ... 10.10.x.x address, then route mail here. ... network, just the address spaces and where to route them to. ...
    (microsoft.public.exchange.design)
  • Re: Dialup in Lucid
    ... Do you manually configure your own DNS? ... applications fail to work over the network. ... Have you checked your route ... Are there other network interfaces ...
    (Ubuntu)
  • Re: Split domain routing or masking?
    ... Don't see how you could tell Exchange to route messages for a certain network to certain hosts, without consideration for or actually knowing which address spaces. ... but the point is any emails to the conglomerates should ...
    (microsoft.public.exchange.design)
  • Re: Unable to reach MSN and Microsoft
    ... I changed the new DCs IP to the intended address within my network and replaced the old 2003 DCs. ... Turns out that my new DC had registered the 192.168.1.x address into DNS as qwest.net. ... From the trace route you can see it is outside of my box. ...
    (microsoft.public.windows.server.networking)
  • Re: network config
    ... just only change the network parameter(IP, dns, gateway, route, ...
    (comp.os.vms)