Re: DNS setup for a child domain in Windows 2003
From: Herb Martin (news_at_LearnQuick.com)
Date: 02/09/05
- Next message: Herb Martin: "Re: integrated DNS"
- Previous message: Herb Martin: "Re: Best Practice Question"
- In reply to: burano: "Re: DNS setup for a child domain in Windows 2003"
- Next in thread: burano: "Re: DNS setup for a child domain in Windows 2003"
- Reply: burano: "Re: DNS setup for a child domain in Windows 2003"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 9 Feb 2005 17:00:12 -0600
"burano" <ravburano@hotmail.com> wrote in message
news:uNXGELuDFHA.3728@TK2MSFTNGP14.phx.gbl...
> Hello Herb,
>
> The thing is though if you are setting up a child domain you need to be
able
> to resolve to the dc in the root domain so you dont get the option there
to
> have ad install the DNS service. So you need to have DNS setup before
> dcpromo and add the zone in for the root, or have your server pointed to
the
> root DNS or again use ahost file i reckon.
Don't use a host file or even consider that.
You can leave the server pointed at the root zone
and you should probably go ahead and create the
delegation at the root for the (to be) child DNS server
you will install on the first child DC.
The servers client settings can find the Root Domain DNS,
from there find itself even.
Later you can setup the forwarding, stub, or secondaries
to patch it together permanently.
Or you can create the DNS server yourself (on the child DC)
and set it all up correctly to start.
> I am doing the same thing as Woody, I have read lots about DNS but there
> seems to be no simple process to follow on planning DNS for child domains.
> so you can never know what best practice is.
Because there really isn't -- the key is it must come out
right no matter what order you do the steps.
It is much easier to explain AND DO the correct steps
than to try to explain a particular sequence since there
are so many choice on the latter.
> I still dont know if I should have DNS running on all the child domains,
is
> that all I need? I have no external namepsace to worry about so it should
be
> simple but I'm just totally confused by it all.
If the DNS is on the child, I would go ahead and make
the child DNS SERVER (not it's client setting necessarily)
be able to find the root (a local Secondary, Stub, or Conditional
Forwarding for the root.)
Now when asked about the root the child DC-DNS server will
be able to find it and ALL CHILDREN (if there are others) of
that root.
>
> "Herb Martin" <news@LearnQuick.com> wrote in message
> news:uCGSwutDFHA.2676@TK2MSFTNGP12.phx.gbl...
> > "Woody" <Woody@discussions.microsoft.com> wrote in message
> > news:EF272F28-B8CB-4DE2-803A-DEEF33DD161A@microsoft.com...
> >> I'm trying to find a correct sequence for installing DNS for a Child
> > domain
> >> that I'm about to create in our Windows 2003 AD.
> >
> >> There is a very little or no materials out there that deals with this
> >> particular subject.
> >>
> >> I have Company.dom, our root domain. I'm about to create
> >> east.company.dom
> >> and create its own DNS for redundancy.
> >
> > There is no SINGLE correct sequence; the key is that
> > you have to get it right by the end.
> >
> > Easiest way is to just do the DCPromo on the "new DC"
> > and when it asks about your DNS tell it to go ahead and
> > install one for you.
> >
> > This pretty much guarantees it gets installed correctly
> > with the zone dynamic, and then you can fix up the "other
> > stuff".*
> >
> >> I Already read KB Article 255248 that deals with this subject but it's
> >> for
> >> Windows 2000 network.
> >
> > It's pretty much the same with a few more OPTIONS
> > for the "other stuff".*
> >
> >> I actually tried the solution in my VMware lab environment but I still
> > have
> >> Issues.
> >>
> >> I think it's something to do with the fact that windows 2003 AD keeps
> >> seperate _msdcs entries.
> >
> > That's good and it causes no problem.
> >
> >
> >> Please help!
> >
> > *Other stuff: child DNS server must be able to find the parent
> > (and any other parents if you have multiple trees). It can hold
> > a Secondary or Stub for the parent or it can have conditional
> > forwarding.
> >
> > Parent DNS mush be able to find the child -- it can Delegate
> > (choice when you right click), or hold a Secondary or Stub
> > for the child. (cond fwd also works)
> >
> > DNS for AD
> > 1) Dynamic for the zone supporting AD
> > 2) All internal DNS clients NIC\IP properties must specify SOLELY
> > that internal, dynamic DNS server (set.)
> > 3) DCs and even DNS servers are DNS clients too -- see #2
> > 4) If you have more than one Domain, every DNS server must
> > be able to resolve ALL domains (either directly or
indirectly)
> >
> > netdiag /fix
> >
> > ...or maybe:
> >
> > dcdiag /fix
> >
> > (Win2003 can do this from Support tools):
> > nltest /dsregdns /server:DC-ServerNameGoesHere
> > http://support.microsoft.com/kb/q260371/
> >
> > Ensure that DNS zones/domains are fully replicated to all DNS
> > servers for that (internal) zone/domain.
> >
> > Also useful may be running DCDiag on each DC, sending the
> > output to a text file, and searching for FAIL, ERROR, WARN.
> >
> > Single Label domain zone names are a problem Google:
> > [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
> >
> > --
> > Herb Martin
> >
> >
> >
>
>
- Next message: Herb Martin: "Re: integrated DNS"
- Previous message: Herb Martin: "Re: Best Practice Question"
- In reply to: burano: "Re: DNS setup for a child domain in Windows 2003"
- Next in thread: burano: "Re: DNS setup for a child domain in Windows 2003"
- Reply: burano: "Re: DNS setup for a child domain in Windows 2003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
