Re: Where in AD is DNS kept?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Santhosh Sivarajan (Santhosh.Sivarajan_at_ins.com)
Date: 03/24/04


Date: Wed, 24 Mar 2004 13:16:56 -0600

You can extract the DNS zone information from ADI zone. Check out the
following link

http://support.microsoft.com/default.aspx?scid=kb;en-us;304489

Santhosh

"Steve Gould" <steve.gould(at)apawood.org> wrote in message
news:%239Z7zLdEEHA.2076@TK2MSFTNGP09.phx.gbl...
> Found it in ADSI. It all looks valid. Now I need to figure out why I can't
> add those zones and why they won't stay when I restart DNS.
>
> Steve
>
> "Santhosh Sivarajan" <Santhosh.Sivarajan@ins.com> wrote in message
> news:%238$e7kcEEHA.3336@TK2MSFTNGP12.phx.gbl...
> > If it the DNS zone is ADI, it is party of your AD database.
> >
> > What you have to do is, convert the Primary Zone to ADI and delete the
> > Seconday Zone from the second DC. After the next AD replication, you
will
> > see the ADI DNS zone on your second DC. Because DNS zone transfer is
also
> > part of AD replication!
> >
> >
> >
> >
> >
> > "Steve Gould" <steve.gould(at)apawood.org> wrote in message
> > news:esexFwbEEHA.3804@TK2MSFTNGP09.phx.gbl...
> > > I have two DC's with Win 2K and AD. Both run DNS, one as standard
> primary
> > > and one as secondary. I converted the first to AD Integrated and let
it
> > run
> > > for a few days to make sure there were no problems. Next I tried to
> > convert
> > > the secondary to AD integrated. It failed saying the zone didn't exist
> in
> > > AD. When I reset the DNS service on the first DC the zones
disappeared.
> It
> > > looks like the zones never wrote to AD after all. I was able to
recover
> > the
> > > zone files from backup and reset DNS to primary/secondary. I'm not
sure
> > what
> > > is wrong because there are no error messages.
> > >
> > > I tried the process with a new test zone and it worked like a charm.
> Doth
> > > DC's were able to use it and restarting the DNS service didn't blow
the
> > zone
> > > away as it did before. I tried again to convert my actual zones from
> > Primary
> > > to AD just on one server and this time the message said the zone
already
> > > existed in AD. I chose to overwrite the current zone in AD. When it
was
> > done
> > > I restarted DNS ALL my zones disappeared even though I only converted
> one
> > > zone.
> > >
> > > Suggestions?
> > >
> > > Where in AD are the zone data stored? Can I use ADSIedit to get to it?
I
> > > can't find it. I want to go in and blow away all references to the DNS
> > zones
> > > in AD so I can try from scratch.
> > >
> > >
> > > --
> > > Steve Gould
> > >
> > >
> > >
> > >
> >
> >
>
>



Relevant Pages

  • Re: DNS Directory partition issue
    ... DNS zone from Domain-wide replication to Forest-wide replication. ... Child's domain is still set to replicate domain-wide, and not Forest ...
    (microsoft.public.windows.server.dns)
  • Re: Naming AD Domain
    ... Each DNS zone is authoritative for the zone of that name so therefore the external DNS zone and internal AD/DNS zone will NOT replicate with each other thereby prevent internal company records to be visible to the outside Internet. ... For further reading on this scenario: ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Directory partition issue
    ... DNS zone from Domain-wide replication to Forest-wide replication. ... Child's domain is still set to replicate domain-wide, and not Forest ...
    (microsoft.public.windows.server.dns)
  • Re: After server restart Dns zone is disappears
    ... Sorry for my delayed response due to the weekend. ... there is an AD integrated zone which has the same name with the ... After server restart Dns zone is disappears ...
    (microsoft.public.win2000.dns)
  • Re: Reverse PTR zone not loaded
    ... the only DC in an SBS2003 environment and all roles are held by one server. ... I can't delete the zone as you suggest, ... Go to DNS, expand forward lookup zones, and delete the DNS Zone. ... PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were ...
    (microsoft.public.windows.server.sbs)