I have added a second email domain to my SBS 2003 box and can send and
receive without an issue.

I do have a question regarding the reverse DNS.

When I check the MX record for the new domain the Microsoft ESMTP MAIL
Service replies with the main public email domain for the SBS box.

Is this going to cause issues sending email?



Any work around?

Thanks

Kevin

"kevin" <21stcenturycommunications@newsgroup> wrote in message
news:7593aeb6-9522-4daa-8937-f8b8de6f8dd6@newsgroup

>I have added a second email domain to my SBS 2003 box and can send and
> receive without an issue.
>
> I do have a question regarding the reverse DNS.
>
> When I check the MX record for the new domain the Microsoft ESMTP MAIL
> Service replies with the main public email domain for the SBS box.
>
> Is this going to cause issues sending email?
>
> Any work around?
>
> Thanks
>
> Kevin

Kevin,

I'm not sure what you mean by:
"> When I check the MX record for the new domain the Microsoft ESMTP MAIL

> Service replies with the main public email domain for the SBS box."

Does that mean you used a telnet session to your SBS? Please elaborate on
how you checked it.

Normally, to test to see if the MX record was created correctly, we can use
nslookup and setting the query to MX, such as:

nslookup

> set q=mx

yourPublicDomainName.com
results show here

To test a reverse entry:
nslookup

> TypeInTheIpAddressOfYourMxRecord

results show here

If you use telnet to test connectivity to your server from the outside world
(such as from home), open telnet, then type in:
open mail.domain.com 25

You should see it open up to your mail server's SMTP FQDN banner, which
should match your MX record.

If receiving for multiple domains, you can simply specify that domain2.com's
MX record is set to domain1.com's MX. This will simplify setting it up, as
well as SPF records.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

kevin <21stcenturycommunications@newsgroup> wrote:

> I have added a second email domain to my SBS 2003 box and can send and
> receive without an issue.
>
> I do have a question regarding the reverse DNS.
>
> When I check the MX record for the new domain the Microsoft ESMTP MAIL
> Service replies with the main public email domain for the SBS box.
>
> Is this going to cause issues sending email?
>
> Any work around?
>
> Thanks
>
> Kevin

This is not a problem. The MX record for blah.com can specify
mail.yaddayaddayadda.com .... and the server's SMTP banner can read
server.domain.local. And the RDNS entry for the public IP can point to
something.somebodyelse.com.

On Sep 5, 9:57*am, "Lanwench [MVP - Exchange]"
<lanwe...@newsgroup> wrote:

> kevin <21stcenturycommunicati...@newsgroup> wrote:

> > I have added a second email domain to my SBS 2003 box and can send and
> > receive without an issue.

>

> > I do have a question regarding the reverse DNS.

>

> > When I check the MX record for the new domain the Microsoft ESMTP MAIL
> > Service replies with the main public email domain for the SBS box.

>

> > Is this going to cause issues sending email?

>

> > Any work around?

>

> > Thanks

>

> > Kevin

>
> This is not a problem. The MX record for blah.com can specify
> mail.yaddayaddayadda.com .... and the server's SMTP banner can read
> server.domain.local. And the RDNS entry for the public IP can point to
> something.somebodyelse.com.- Hide quoted text -
>
> - Show quoted text -

Thanks,,,

On Sep 4, 10:06*pm, "Ace Fekay [MCT]" <ace...@newsgroup>
wrote:

> "kevin" <21stcenturycommunicati...@newsgroup> wrote in message
>
> news:7593aeb6-9522-4daa-8937-f8b8de6f8dd6@newsgroup
>

> >I have added a second email domain to my SBS 2003 box and can send and
> > receive without an issue.

>

> > I do have a question regarding the reverse DNS.

>

> > When I check the MX record for the new domain the Microsoft ESMTP MAIL
> > Service replies with the main public email domain for the SBS box.

>

> > Is this going to cause issues sending email?

>

> > Any work around?

>

> > Thanks

>

> > Kevin

>
> Kevin,
>
> I'm not sure what you mean by:
> "> When I check the MX record for the new domain the Microsoft ESMTP MAIL
>

> > Service replies with the main public email domain for the SBS box."

>
> Does that mean you used a telnet session to your SBS? Please elaborate on
> how you checked it.
>
> Normally, to test to see if the MX record was created correctly, we can use
> nslookup and setting the query to MX, such as:
>
> nslookup> set q=mx
>
> yourPublicDomainName.com
> results show here
>
> To test a reverse entry:
> nslookup> TypeInTheIpAddressOfYourMxRecord
>
> results show here
>
> If you use telnet to test connectivity to your server from the outside world
> (such as from home), open telnet, then type in:
> open mail.domain.com 25
>
> You should see it open up to your mail server's SMTP FQDN banner, which
> should match your MX record.
>
> If receiving for multiple domains, you can simply specify that domain2.com's
> MX record is set to domain1.com's MX. This will simplify setting it up, as
> well as SPF records.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit among
> responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
>
> For urgent issues, please contact Microsoft PSS directly. Please checkhttp://support.microsoft.comfor regional support phone numbers.

I use MXTOOLBOX.COM to check the mx records ... My question was if my
mailserver was xxx.com and my email domain was yyy.org and my server
responds to mxtoolbox that yyy.org mailserver responded with xxx.com
whould this be a issue.

according to lanwrench this should not be a issue.

Thanks

> On Sep 4, 10:06*pm, "Ace Fekay [MCT]" <ace...@newsgroup>

> wrote:

>> "kevin" <21stcenturycommunicati...@newsgroup> wrote in message
>>
>> news:7593aeb6-9522-4daa-8937-f8b8de6f8dd6@newsgroup
>>

>>> I have added a second email domain to my SBS 2003 box and can send and
>>> receive without an issue.

>>

>>> I do have a question regarding the reverse DNS.
>>> When I check the MX record for the new domain the Microsoft ESMTP MAIL
>>> Service replies with the main public email domain for the SBS box.
>>> Is this going to cause issues sending email?
>>> Any work around?

>>

>>> Thanks

>>

>>> Kevin

>>
>> Kevin,
>>
>> I'm not sure what you mean by:
>> "> When I check the MX record for the new domain the Microsoft ESMTP MAIL
>>

>>> Service replies with the main public email domain for the SBS box."

>>
>> Does that mean you used a telnet session to your SBS? Please elaborate on
>> how you checked it.
>>
>> Normally, to test to see if the MX record was created correctly, we can use
>> nslookup and setting the query to MX, such as:
>>
>> nslookup> set q=mx
>>
>> yourPublicDomainName.com
>> results show here
>>
>> To test a reverse entry:
>> nslookup> TypeInTheIpAddressOfYourMxRecord
>>
>> results show here
>>
>> If you use telnet to test connectivity to your server from the outside world
>> (such as from home), open telnet, then type in:
>> open mail.domain.com 25
>>
>> You should see it open up to your mail server's SMTP FQDN banner, which
>> should match your MX record.
>>
>> If receiving for multiple domains, you can simply specify that domain2.com's
>> MX record is set to domain1.com's MX. This will simplify setting it up, as
>> well as SPF records.
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit among
>> responding engineers, and to help others benefit from your resolution.
>>
>> Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
>> Microsoft Certified Trainer
>>
>> For urgent issues, please contact Microsoft PSS directly. Please
>> checkhttp://support.microsoft.comfor regional support phone numbers.

>
> I use MXTOOLBOX.COM to check the mx records ... My question was if my
> mailserver was xxx.com and my email domain was yyy.org and my server
> responds to mxtoolbox that yyy.org mailserver responded with xxx.com
> whould this be a issue.
>
> according to lanwrench this should not be a issue.
>
> Thanks

I agree with Lanwench. No problem at all. Many companies have hosted
Exchange, or hosting multiple domain emails, and work fine.

I would just make sure your SPF record for the additional domains
reflect they can come from your current IP address without indicating
domain names, this way it's a bit more generic and will cover all
domains that send mail from this IP. One example, which works fine
(used this format at a large corporation with multiple domain names):

v=spf1 ip4:YourWanIpAddress/32 -all


Ace

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.

Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

kevin <21stcenturycommunications@newsgroup> wrote:

> On Sep 5, 9:57 am, "Lanwench [MVP - Exchange]"
> <lanwe...@newsgroup> wrote:

>> kevin <21stcenturycommunicati...@newsgroup> wrote:

>>> I have added a second email domain to my SBS 2003 box and can send
>>> and receive without an issue.

>>

>>> I do have a question regarding the reverse DNS.

>>

>>> When I check the MX record for the new domain the Microsoft ESMTP
>>> MAIL Service replies with the main public email domain for the SBS
>>> box.

>>

>>> Is this going to cause issues sending email?

>>

>>> Any work around?

>>

>>> Thanks

>>

>>> Kevin

>>
>> This is not a problem. The MX record for blah.com can specify
>> mail.yaddayaddayadda.com .... and the server's SMTP banner can read
>> server.domain.local. And the RDNS entry for the public IP can point
>> to something.somebodyelse.com.- Hide quoted text -
>>
>> - Show quoted text -

>
> Thanks,,,

No problem. If you do run into trouble with mail delivery, the other admins
are being way too overzealous about 'security' and are not well-read in the
RFCs for SMTP mail.