[newbie] dns placement?

[Eric]

hi, I'am new to exchange server 2003, so, there are some questions
when the company have one forest and 3 seperate domain tree,
first one, that is external domain connected to the internet, while other is
in
private network. How should I place dns servers that made connected from
one domain to any other domain.

coz when I created domain tree, it seen to be that the DCs srv record is
added
only to the root domain. But not the child domains where it should be place.
that lead to a problem arise. it's a user in a domain can't let connected to
other domain's servers
coz no other domain dns record is found. only the local domain dns record
could be found.
Is this connection can throught GC?

any ideas or suggestion are must.
Thanks you

Eric,

[Al Mulnick]

DNS is highly critical to your environment. You will need to find a way to
allow the child domain members to find root resources (infrequent, but
happens) and for the root members to find child domain members. I typically
favor stub zones where possible, but secondary zones will work also.

There's some great docs about DNS server records on the microsoft site if
you need them. http://www.microsoft.com/dns (I'm sure that the bit about it
being for Windows 2000 is just an oversight that will sooner or later be
corrected and or consolidated with the 2003 docs; concepts still apply but
you get some enhanced flexibility in 2003 AD :)


Al

"Eric" <pgeric888@hotmail.com> wrote in message
news:uP09pU8RFHA.3144@tk2msftngp13.phx.gbl...

hi, I'am new to exchange server 2003, so, there are some questions
when the company have one forest and 3 seperate domain tree,
first one, that is external domain connected to the internet, while other
is
in
private network. How should I place dns servers that made connected from
one domain to any other domain.

coz when I created domain tree, it seen to be that the DCs srv record is
added
only to the root domain. But not the child domains where it should be
place.
that lead to a problem arise. it's a user in a domain can't let connected
to
other domain's servers
coz no other domain dns record is found. only the local domain dns record
could be found.
Is this connection can throught GC?

any ideas or suggestion are must.
Thanks you

Eric,

[Eric]

thank AI,
your information so usefull
but, there are some concept that I might be not clear, would you give some
suggestions
for clients connect to remote domain member servers,
the flow would be as following,
client -> dns server - > DCs -> member servers ( single domain )
client -> dns server -> GCs -> other domains DCs -> member servers (
multiple domains )

so, dns server will provides information about DCs, and DCs will provides
the information for the computer ip address
please let me know if this is wrong,
might be coz I'am really not family will dns when in multiple domain
environment
and client finding member servers when in that environment.

thank you

Eric,


"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:uNuECnBSFHA.3704@TK2MSFTNGP12.phx.gbl...

DNS is highly critical to your environment. You will need to find a way
to
allow the child domain members to find root resources (infrequent, but
happens) and for the root members to find child domain members. I
typically
favor stub zones where possible, but secondary zones will work also.

There's some great docs about DNS server records on the microsoft site if
you need them. http://www.microsoft.com/dns (I'm sure that the bit about
it
being for Windows 2000 is just an oversight that will sooner or later be
corrected and or consolidated with the 2003 docs; concepts still apply but
you get some enhanced flexibility in 2003 AD :)


Al

"Eric" <pgeric888@hotmail.com> wrote in message
news:uP09pU8RFHA.3144@tk2msftngp13.phx.gbl...
hi, I'am new to exchange server 2003, so, there are some questions
when the company have one forest and 3 seperate domain tree,
first one, that is external domain connected to the internet, while
other
is
in
private network. How should I place dns servers that made connected from
one domain to any other domain.

coz when I created domain tree, it seen to be that the DCs srv record is
added
only to the root domain. But not the child domains where it should be
place.
that lead to a problem arise. it's a user in a domain can't let
connected
to
other domain's servers
coz no other domain dns record is found. only the local domain dns
record
could be found.
Is this connection can throught GC?

any ideas or suggestion are must.
Thanks you

Eric,

[Al Mulnick]

Name resolution is used to find network resources. DNS is name resolution.
Windows Server Active Directory uses DNS extensively.
DC's don't (for generall discussions) let other clients know where the
clients are located. That's the job of DNS.

So in your scenario, it's client ->DNS->memberserver

client -> dns server -> otherdomain's member servers (and GC's are involved)

Have you seen the multi-forest docs yet? If not, it would be a good idea to
get familiar with them. They'll talk about the best ways to deploy DNS for
this type of scenario as well as site topology etc.

Al


"Eric" <pgeric888@hotmail.com> wrote in message
news:eU8CpKUSFHA.3544@TK2MSFTNGP12.phx.gbl...

thank AI,
your information so usefull
but, there are some concept that I might be not clear, would you give some
suggestions
for clients connect to remote domain member servers,
the flow would be as following,
client -> dns server - > DCs -> member servers ( single domain )
client -> dns server -> GCs -> other domains DCs -> member servers (
multiple domains )

so, dns server will provides information about DCs, and DCs will provides
the information for the computer ip address
please let me know if this is wrong,
might be coz I'am really not family will dns when in multiple domain
environment
and client finding member servers when in that environment.

thank you

Eric,


"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:uNuECnBSFHA.3704@TK2MSFTNGP12.phx.gbl...
DNS is highly critical to your environment. You will need to find a way
to
allow the child domain members to find root resources (infrequent, but
happens) and for the root members to find child domain members. I
typically
favor stub zones where possible, but secondary zones will work also.

There's some great docs about DNS server records on the microsoft site if
you need them. http://www.microsoft.com/dns (I'm sure that the bit about
it
being for Windows 2000 is just an oversight that will sooner or later be
corrected and or consolidated with the 2003 docs; concepts still apply
but
you get some enhanced flexibility in 2003 AD :)


Al

"Eric" <pgeric888@hotmail.com> wrote in message
news:uP09pU8RFHA.3144@tk2msftngp13.phx.gbl...
hi, I'am new to exchange server 2003, so, there are some questions
when the company have one forest and 3 seperate domain tree,
first one, that is external domain connected to the internet, while
other
is
in
private network. How should I place dns servers that made connected
from
one domain to any other domain.

coz when I created domain tree, it seen to be that the DCs srv record
is
added
only to the root domain. But not the child domains where it should be
place.
that lead to a problem arise. it's a user in a domain can't let
connected
to
other domain's servers
coz no other domain dns record is found. only the local domain dns
record
could be found.
Is this connection can throught GC?

any ideas or suggestion are must.
Thanks you

Eric,