I have an internal SMTP server that needs to receive mail relayed from my
exchange server. my exhange smtp mail is @company.com. I want to create a
smtp connector that relays all mail sent to @mail.company.com to another non
exchange SMTP server for an internal application.

What do i need to set up in DNS for the A record mail.company.com to work?

For RESOLUTION by clients these are virtually indistinguishable but
if you DELEGATE to a Child Zone you can put the DNS for that
child zone on a different DNS server (set) and have it (possibly)
administrated
by different Admins.

If you make the name a SubDomain within the parent name Zone (i.e., Same
Zone) then you will have those names on EXACTLY the same set of DNS
servers as the main or parent zone since it is literally part of that zone.

Zones are the Administrative Divisions of the DNS namespace -- subdomains
are commonly Delegate to different zones but that is NOT a requirement.

"Brillmike" <brillmike@yahoo.com> wrote in message
news:95366F92-1709-421A-BFA0-1FC38D1694E2@microsoft.com...
>I have an internal SMTP server that needs to receive mail relayed from my
> exchange server. my exhange smtp mail is @company.com. I want to create a
> smtp connector that relays all mail sent to @mail.company.com to another
> non
> exchange SMTP server for an internal application.

That is NOT (really) a DNS question but a configuration in your Exchange
server
(and in you other SMTP Server).

> What do i need to set up in DNS for the A record mail.company.com to work?

Simply that. If you need an "A record" then you add an A record, so
presumably
you meant something else by the question, perhaps what I covered above OR
you may need to ask a follow-up question to clarify....


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com (phone on web site)

If you use LinkedIn then tell me where you know me from when linking:

http://www.linkedin.com/in/herbmartin

I do allways make another zone for subdomain. It is more flexible. I suggest
you to use let say company.com zone for everything in this zone. And
mail.company.com zone for things related to mail.company.com.
Especiali if you wil create MX recrod for mail.company.com.
I always do a new zone and I have no problems.

Luka


"Herb Martin" <news@learnquick.com> wrote in message
news:e2lERqq5HHA.5184@TK2MSFTNGP03.phx.gbl...
>
> For RESOLUTION by clients these are virtually indistinguishable but
> if you DELEGATE to a Child Zone you can put the DNS for that
> child zone on a different DNS server (set) and have it (possibly)
> administrated
> by different Admins.
>
> If you make the name a SubDomain within the parent name Zone (i.e., Same
> Zone) then you will have those names on EXACTLY the same set of DNS
> servers as the main or parent zone since it is literally part of that
> zone.
>
> Zones are the Administrative Divisions of the DNS namespace -- subdomains
> are commonly Delegate to different zones but that is NOT a requirement.
>
> "Brillmike" <brillmike@yahoo.com> wrote in message
> news:95366F92-1709-421A-BFA0-1FC38D1694E2@microsoft.com...
>>I have an internal SMTP server that needs to receive mail relayed from my
>> exchange server. my exhange smtp mail is @company.com. I want to create a
>> smtp connector that relays all mail sent to @mail.company.com to another
>> non
>> exchange SMTP server for an internal application.
>
> That is NOT (really) a DNS question but a configuration in your Exchange
> server
> (and in you other SMTP Server).
>
>> What do i need to set up in DNS for the A record mail.company.com to
>> work?
>
> Simply that. If you need an "A record" then you add an A record, so
> presumably
> you meant something else by the question, perhaps what I covered above OR
> you may need to ask a follow-up question to clarify....
>
>
> --
> Herb Martin, MCSE, MVP
> http://www.LearnQuick.Com (phone on web site)
>
> If you use LinkedIn then tell me where you know me from when linking:
>
> http://www.linkedin.com/in/herbmartin
>
>

"Luka Manojlovic" <luka@news.manojlovic.net> wrote in message
news:faoqjc$f9d$1@registered.motzarella.org...
>I do allways make another zone for subdomain. It is more flexible.

Yes it is more "flexible" but making it a rule to ALWAYS do this is
also inefficient of the admins time and attention; having to setup
replication individually for a separate Zone that is going to be
managed exactly like the parent on the same set of servers is
not useful.

> I suggest you to use let say company.com zone for everything in this zone.
> And mail.company.com zone for things related to mail.company.com.
> Especiali if you wil create MX recrod for mail.company.com.
> I always do a new zone and I have no problems.

None of the records really care whether it is a separate or same zone.

The issue is do you wish a DIFFERENT "set of Admins" or a DIFFERENT
"set of Servers" or wish to have different "Zone Properties" for the child
domain -- if you do, then it should be a DIFFERENT zone, but if you wish
all of the above to be the SAME then you are wasting your time.

1) Admins
2) Servers
3) Zone properties

.... are the key.


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com (phone on web site)

If you use LinkedIn then tell me where you know me from when linking:
http://www.linkedin.com/in/herbmartin

> Luka
>
>
> "Herb Martin" <news@learnquick.com> wrote in message
> news:e2lERqq5HHA.5184@TK2MSFTNGP03.phx.gbl...
>>
>> For RESOLUTION by clients these are virtually indistinguishable but
>> if you DELEGATE to a Child Zone you can put the DNS for that
>> child zone on a different DNS server (set) and have it (possibly)
>> administrated
>> by different Admins.
>>
>> If you make the name a SubDomain within the parent name Zone (i.e., Same
>> Zone) then you will have those names on EXACTLY the same set of DNS
>> servers as the main or parent zone since it is literally part of that
>> zone.
>>
>> Zones are the Administrative Divisions of the DNS namespace -- subdomains
>> are commonly Delegate to different zones but that is NOT a requirement.
>>
>> "Brillmike" <brillmike@yahoo.com> wrote in message
>> news:95366F92-1709-421A-BFA0-1FC38D1694E2@microsoft.com...
>>>I have an internal SMTP server that needs to receive mail relayed from my
>>> exchange server. my exhange smtp mail is @company.com. I want to create
>>> a
>>> smtp connector that relays all mail sent to @mail.company.com to another
>>> non
>>> exchange SMTP server for an internal application.
>>
>> That is NOT (really) a DNS question but a configuration in your Exchange
>> server
>> (and in you other SMTP Server).
>>
>>> What do i need to set up in DNS for the A record mail.company.com to
>>> work?
>>
>> Simply that. If you need an "A record" then you add an A record, so
>> presumably
>> you meant something else by the question, perhaps what I covered above OR
>> you may need to ask a follow-up question to clarify....
>>
>>
>> --
>> Herb Martin, MCSE, MVP
>> http://www.LearnQuick.Com (phone on web site)
>>
>> If you use LinkedIn then tell me where you know me from when linking:
>>
>> http://www.linkedin.com/in/herbmartin
>>
>>
>
>

I think you are perfectly right... But it happened to me often than after
adding one host in a week or two users went out with other ideas and
suddenly there were alot of records. So I decited to "torture" me only
the first time. It is true, that if you need only one record its better to
add it to existent zone as it is / it works the same.

Luka

"Herb Martin" <news@learnquick.com> wrote in message
news:eMNiznc6HHA.464@TK2MSFTNGP02.phx.gbl...
>
> "Luka Manojlovic" <luka@news.manojlovic.net> wrote in message
> news:faoqjc$f9d$1@registered.motzarella.org...
>>I do allways make another zone for subdomain. It is more flexible.
>
> Yes it is more "flexible" but making it a rule to ALWAYS do this is
> also inefficient of the admins time and attention; having to setup
> replication individually for a separate Zone that is going to be
> managed exactly like the parent on the same set of servers is
> not useful.
>
>> I suggest you to use let say company.com zone for everything in this
>> zone. And mail.company.com zone for things related to mail.company.com.
>> Especiali if you wil create MX recrod for mail.company.com.
>> I always do a new zone and I have no problems.
>
> None of the records really care whether it is a separate or same zone.
>
> The issue is do you wish a DIFFERENT "set of Admins" or a DIFFERENT
> "set of Servers" or wish to have different "Zone Properties" for the child
> domain -- if you do, then it should be a DIFFERENT zone, but if you wish
> all of the above to be the SAME then you are wasting your time.
>
> 1) Admins
> 2) Servers
> 3) Zone properties
>
> ... are the key.
>
>
> --
> Herb Martin, MCSE, MVP
> http://www.LearnQuick.Com (phone on web site)
>
> If you use LinkedIn then tell me where you know me from when linking:
> http://www.linkedin.com/in/herbmartin
>
>> Luka
>>
>>
>> "Herb Martin" <news@learnquick.com> wrote in message
>> news:e2lERqq5HHA.5184@TK2MSFTNGP03.phx.gbl...
>>>
>>> For RESOLUTION by clients these are virtually indistinguishable but
>>> if you DELEGATE to a Child Zone you can put the DNS for that
>>> child zone on a different DNS server (set) and have it (possibly)
>>> administrated
>>> by different Admins.
>>>
>>> If you make the name a SubDomain within the parent name Zone (i.e., Same
>>> Zone) then you will have those names on EXACTLY the same set of DNS
>>> servers as the main or parent zone since it is literally part of that
>>> zone.
>>>
>>> Zones are the Administrative Divisions of the DNS namespace --
>>> subdomains
>>> are commonly Delegate to different zones but that is NOT a requirement.
>>>
>>> "Brillmike" <brillmike@yahoo.com> wrote in message
>>> news:95366F92-1709-421A-BFA0-1FC38D1694E2@microsoft.com...
>>>>I have an internal SMTP server that needs to receive mail relayed from
>>>>my
>>>> exchange server. my exhange smtp mail is @company.com. I want to create
>>>> a
>>>> smtp connector that relays all mail sent to @mail.company.com to
>>>> another non
>>>> exchange SMTP server for an internal application.
>>>
>>> That is NOT (really) a DNS question but a configuration in your Exchange
>>> server
>>> (and in you other SMTP Server).
>>>
>>>> What do i need to set up in DNS for the A record mail.company.com to
>>>> work?
>>>
>>> Simply that. If you need an "A record" then you add an A record, so
>>> presumably
>>> you meant something else by the question, perhaps what I covered above
>>> OR
>>> you may need to ask a follow-up question to clarify....
>>>
>>>
>>> --
>>> Herb Martin, MCSE, MVP
>>> http://www.LearnQuick.Com (phone on web site)
>>>
>>> If you use LinkedIn then tell me where you know me from when linking:
>>>
>>> http://www.linkedin.com/in/herbmartin
>>>
>>>
>>
>>
>
>

"Luka Manojlovic" <luka@news.manojlovic.net> wrote in message
news:fb5th7$tfq$1@registered.motzarella.org...
>I think you are perfectly right... But it happened to me often than after
>adding one host in a week or two users went out with other ideas and
>suddenly there were alot of records. So I decited to "torture" me only
>the first time. It is true, that if you need only one record its better to
>add it to existent zone as it is / it works the same.

Again it is NOT about "how many records" but rather if you need any of
the following to be DIFFERENT:

1) Servers which hold the child domain/zone

2) Admins who are responsible

3) Properties for a separate zone rather than the same domain/subdomain