DNS and routing Jay 12.07.2007 21:18:02 [posted here as DNS may be a possible design consideration instead of mail] 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[ at ]MYOWN.COM emails to SHELLY[ at ]HEROWN.COM... the mail would not go through the internet but directly through to SECUREWAN.COM network... the email becomes from BOB[ at ]MYOWN.SECUREWAN.COM and goes effectively to SHELLY[ at ]HEROWN.SECUREWAN.COM. When SHELLY[ at ]HEROWN.COM 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?

Re: DNS and routing "SimonR" <srae23[ at ]gmail.com> 13.07.2007 08:36:57 This sounds more like an Exchange question than a DNS issue. Is Exchange used by all the organizations on the SECUREWAN.COM network? If so, you should be able to set up routing groups to handle this scenario. As far as the address rewriting goes, you may be able to use the Exchange 2003 address rewrite tool to achieve this. I haven't tried this myself but it may be worth a look. -- Simon Rae MCSE 2003, CCA "Jay" <Jay[ at ]discussions.microsoft.com> wrote in message news:3C035265-B60A-46A3-A3B5-0B8F0FF614D1[ at ]microsoft.com... [Quoted Text] > [posted here as DNS may be a possible design consideration instead of > mail] > > 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[ at ]MYOWN.COM emails to SHELLY[ at ]HEROWN.COM... the > mail would not go through the internet but directly through to > SECUREWAN.COM > network... the email becomes from BOB[ at ]MYOWN.SECUREWAN.COM and goes > effectively to SHELLY[ at ]HEROWN.SECUREWAN.COM. When SHELLY[ at ]HEROWN.COM 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?