Re: change secondary zone to AD integrated

• Previous message: Roger Abell: "Re: PDC Emulator DNS entries"
• In reply to: Gary: "Re: change secondary zone to AD integrated"
• Next in thread: Gary: "Re: change secondary zone to AD integrated"
• Reply: Gary: "Re: change secondary zone to AD integrated"
• Messages sorted by: [ date ] [ thread ]

Date: Thu, 10 Jun 2004 01:00:43 -0700

If I followed the added info, the DC showing the problem
was running DNS on NT4 and was then upgraded. It now
runs company.com (as standard prinary?) and the AD
supporting local.company.com as a secondary pulling
from DCs of the same domain where that zone is AD
integrated.
It is my understanding that this is supposed to be an
impossible configuration, having the local.company.com
zone other than as as an AD integrated zone on a DC of
the same domain where it exists AD integrated on other
DCs.
In the company.com zone, is there a delegation for the
local subdomain that points to all DCs ?
If you delete the secondary for local.company.com, and
then add local.company.com specifying AD integrated
what happens ?
In the final analysis, after taking care relative to what is
pointed to this DC for DNS, and where company.com is
held in the interrim, it might not hurt to then uninstall and
reinstall DNS on that DC - given that the machine was
upgraded from NT4 with NT4 DNS.

-- 
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4)  MCDBA
"Gary" <anonymous@discussions.microsoft.com> wrote in message
news:1984201c44cdf$75f699d0$a001280a@phx.gbl...
> Thanks for the replies,
>
> To answer your question, its running 1 single domain,
> local.company.com
>
> also some more more info for you - the DNS Server that has
> a problem was previously the PDC on the NT4 Domain (domain
> was upgraded about 6 weeks ago). When an NT4 pdc it ran
> the DNS for company.com (the name of Domain). During the
> upgrade we named domain to 'local.company.com', and DNS
> configured itself, now hosting both company.com and
> local.company.com, with local. as an AD integrated zone.
>
> We promoted other BDCs, and let windows install DNS onto
> these. As we upgraded the bdc's they showed 'error 4515,
> duplicate zone exists' in dns log whenever the service
> started. We phoned MS Professional support and got help
> with this message - they talked us through removing the
> duplicate zone.
>
> at some point soon after this the local.company.com
> zone 'disapeared' from the old pdc. imeditaly after we had
> removed the duplicate zone as above everything seemed to
> be working OK.
>
> the server is now running as a secondary zone, while all
> the other DCs are AD integrated.
>
> my thought is maybe to remove the dns service on the
> server and reinstalled, hoping that it will auto install
> the AD integrated zone onto it. My only concern is not to
> break DNS in the domain, as at the moment all other
> servers seem to working.
>
> thanks again
> .
>
>
> >-----Original Message-----
> >Hi Ulf,
> >
> >There seems even more at work here, as I thought it
> impossible
> >to have a zone as secondary if that zone is AD integrated
> on other
> >DC/DNS of the same domain.
> >
> >Hence, removing the exisiting definintion as a secondary
> and then
> >defining the zone as AD integrated (or simply changing
> the existing
> >def to AD integrated) may not be the answer here.
> >
> >-- 
> >Roger Abell
> >Microsoft MVP (Windows Server System: Security)
> >MCSE (W2k3,W2k,Nt4)  MCDBA
> >"Ulf B. Simon-Weidner [MVP]" <nospam2-ulf@usw-
> consulting.com> wrote in
> >message news:OUyYX2fSEHA.2716@tk2msftngp13.phx.gbl...
> >> "Gary" <anonymous@discussions.microsoft.com> wrote in
> message
> >> news:1817201c449ea$6575f260$a101280a@phx.gbl:
> >> > Hi,
> >> >
> >> > For an unknown reason the internal dns zone on one of
> my
> >> > 2003 Domain Controllers 'disapeared'. All servers run
> 2003
> >> > server, and all DC's are set as DNS servers.
> >> >
> >> > Users had slow logins one morning, and I found that
> the
> >> > DNS server given as the primary DNS server in DHCP no
> >> > longer had the zone 'local.company.com'. All other DNS
> >> > servers were working, so that issue was fixed by
> removing
> >> > the IP of the bad server from DNS props on clients.
> >> >
> >> > After that I installed the 'local.company.com' zone
> back
> >> > into the problem server as a secondary zone, and this
> has
> >> > been working without problems.
> >> >
> >> > I now want to return the DNS on this server to run as
> an
> >> > AD intergrated zone. How can I do this? Do I need to
> >> > remove the DNS service and reinstall (I dont want to
> do
> >> > this as the server also contains other zones which
> havent
> >> > had any problems, and arnt AD integrated so wont auto
> >> > rebuild from other servers), or can I somehow convert
> the
> >> > secondary zone on this server into an AD intregrated
> one?
> >> >
> >> > Thanks in advance
> >> >
> >> > Gary
> >>
> >> Hello Gary,
> >>
> >> if I understand correctly you've got multiple DNS-
> Servers covering a
> >> AD-Integrated zone, but one of them failed to host the
> zone anymore. So
> >> you created a secondary zone on this server?!?
> >>
> >> If this is the case, then check your DCs very well, a
> DC is not
> >> supposed to "loose" a AD Integrated DNS-Zone as long as
> he's in the
> >> replication scope for that zone.
> >> You'll get the zone back by simply deleting the
> secondary zone and make
> >> sure your replication is working, the zone should be
> replicated from
> >> the other DCs which are also DNS-Servers.
> >>
> >> -- 
> >> Gruesse - Sincerely,
> >>
> >> Ulf B. Simon-Weidner
> >
> >
> >.
> >

• Previous message: Roger Abell: "Re: PDC Emulator DNS entries"
• In reply to: Gary: "Re: change secondary zone to AD integrated"
• Next in thread: Gary: "Re: change secondary zone to AD integrated"
• Reply: Gary: "Re: change secondary zone to AD integrated"
• Messages sorted by: [ date ] [ thread ]