Hi there,
One of our Windows 2000 domain controllers died last week so we had to
remove it from AD as per the following article ->
http://support.microsoft.com/kb/216498.
The problem is we have approximately 100 Active Directly integrated DNS
zones & the 'old' DC is still listed as a Name Server (NS) in all of them.
Is there a quick & easy to remove this entry or do we need to remove it
manually from all of the zones?
Any suggestions/comments are greatly appreciated.
Regards,
Veets

Re: Removing failed DC from AD Integrated Zones by Herb

Herb
Mon May 05 05:29:52 PDT 2008


"Veets" <Veets@h0tmail.com> wrote in message
news:%23XmttmqrIHA.2208@TK2MSFTNGP04.phx.gbl...
> Hi there,
> One of our Windows 2000 domain controllers died last week so we had to
> remove it from AD as per the following article ->
> http://support.microsoft.com/kb/216498.
> The problem is we have approximately 100 Active Directly integrated DNS
> zones & the 'old' DC is still listed as a Name Server (NS) in all of them.

> Is there a quick & easy to remove this entry or do we need to remove it
> manually from all of the zones?

Depends if you (likely) mean "100 Servers with the SAME single AD
Integrated Zone" or 100 distinct (i.e., for different domains) zones.

If the former, remove it from one of them and the deletion will replicate.

If the latter then one wonders why the SAME DNS would be listed in
100 different zones but what the heck:

Write a script using DNSCmd.exe and feed it a list (text file) of
each server name to repeate the process.

> Any suggestions/comments are greatly appreciated.
> Regards,
> Veets
>
>



Re: Removing failed DC from AD Integrated Zones by Veets

Veets
Mon May 05 07:33:23 PDT 2008

Thanks for replying Herb
It was actually the latter (100 distinct domains). We do a lot of internal
website testing which is why we have so many of them.
I will take a look at DNSCmd.exe
Thanks again.
Veets

"Herb Martin" <news@learnquick.com> wrote in message
news:eG1r4uqrIHA.524@TK2MSFTNGP05.phx.gbl...
>
> "Veets" <Veets@h0tmail.com> wrote in message
> news:%23XmttmqrIHA.2208@TK2MSFTNGP04.phx.gbl...
>> Hi there,
>> One of our Windows 2000 domain controllers died last week so we had to
>> remove it from AD as per the following article ->
>> http://support.microsoft.com/kb/216498.
>> The problem is we have approximately 100 Active Directly integrated DNS
>> zones & the 'old' DC is still listed as a Name Server (NS) in all of
>> them.
>
>> Is there a quick & easy to remove this entry or do we need to remove it
>> manually from all of the zones?
>
> Depends if you (likely) mean "100 Servers with the SAME single AD
> Integrated Zone" or 100 distinct (i.e., for different domains) zones.
>
> If the former, remove it from one of them and the deletion will replicate.
>
> If the latter then one wonders why the SAME DNS would be listed in
> 100 different zones but what the heck:
>
> Write a script using DNSCmd.exe and feed it a list (text file) of
> each server name to repeate the process.
>
>> Any suggestions/comments are greatly appreciated.
>> Regards,
>> Veets
>>
>>
>
>



Re: Removing failed DC from AD Integrated Zones by Blake

Blake
Mon May 05 09:29:49 PDT 2008

You should be able to pull all the zones with

dnscmd SERVERNAME /enumzones > .\zones.txt

this will give you a list of all the zones

Then something like

dnscmd SERVERNAME /recorddelete ZONENAME DEADDCNAME NS /f

I'd use VBS or something similiar to write a quick script to spit out 100
command lines of the /recorddelete line

Blake




"Veets" <Veets@h0tmail.com> wrote in message
news:uCKYizrrIHA.1200@TK2MSFTNGP03.phx.gbl...
> Thanks for replying Herb
> It was actually the latter (100 distinct domains). We do a lot of internal
> website testing which is why we have so many of them.
> I will take a look at DNSCmd.exe
> Thanks again.
> Veets
>
> "Herb Martin" <news@learnquick.com> wrote in message
> news:eG1r4uqrIHA.524@TK2MSFTNGP05.phx.gbl...
>>
>> "Veets" <Veets@h0tmail.com> wrote in message
>> news:%23XmttmqrIHA.2208@TK2MSFTNGP04.phx.gbl...
>>> Hi there,
>>> One of our Windows 2000 domain controllers died last week so we had to
>>> remove it from AD as per the following article ->
>>> http://support.microsoft.com/kb/216498.
>>> The problem is we have approximately 100 Active Directly integrated DNS
>>> zones & the 'old' DC is still listed as a Name Server (NS) in all of
>>> them.
>>
>>> Is there a quick & easy to remove this entry or do we need to remove it
>>> manually from all of the zones?
>>
>> Depends if you (likely) mean "100 Servers with the SAME single AD
>> Integrated Zone" or 100 distinct (i.e., for different domains) zones.
>>
>> If the former, remove it from one of them and the deletion will
>> replicate.
>>
>> If the latter then one wonders why the SAME DNS would be listed in
>> 100 different zones but what the heck:
>>
>> Write a script using DNSCmd.exe and feed it a list (text file) of
>> each server name to repeate the process.
>>
>>> Any suggestions/comments are greatly appreciated.
>>> Regards,
>>> Veets
>>>
>>>
>>
>>
>
>



Re: Removing failed DC from AD Integrated Zones by Veets

Veets
Mon May 05 17:17:57 PDT 2008

Thanks guys

"Blake" <blake@blake.com> wrote in message
news:%23VBt%230srIHA.800@TK2MSFTNGP02.phx.gbl...
> You should be able to pull all the zones with
>
> dnscmd SERVERNAME /enumzones > .\zones.txt
>
> this will give you a list of all the zones
>
> Then something like
>
> dnscmd SERVERNAME /recorddelete ZONENAME DEADDCNAME NS /f
>
> I'd use VBS or something similiar to write a quick script to spit out 100
> command lines of the /recorddelete line
>
> Blake
>
>
>
>
> "Veets" <Veets@h0tmail.com> wrote in message
> news:uCKYizrrIHA.1200@TK2MSFTNGP03.phx.gbl...
>> Thanks for replying Herb
>> It was actually the latter (100 distinct domains). We do a lot of
>> internal website testing which is why we have so many of them.
>> I will take a look at DNSCmd.exe
>> Thanks again.
>> Veets
>>
>> "Herb Martin" <news@learnquick.com> wrote in message
>> news:eG1r4uqrIHA.524@TK2MSFTNGP05.phx.gbl...
>>>
>>> "Veets" <Veets@h0tmail.com> wrote in message
>>> news:%23XmttmqrIHA.2208@TK2MSFTNGP04.phx.gbl...
>>>> Hi there,
>>>> One of our Windows 2000 domain controllers died last week so we had to
>>>> remove it from AD as per the following article ->
>>>> http://support.microsoft.com/kb/216498.
>>>> The problem is we have approximately 100 Active Directly integrated DNS
>>>> zones & the 'old' DC is still listed as a Name Server (NS) in all of
>>>> them.
>>>
>>>> Is there a quick & easy to remove this entry or do we need to remove it
>>>> manually from all of the zones?
>>>
>>> Depends if you (likely) mean "100 Servers with the SAME single AD
>>> Integrated Zone" or 100 distinct (i.e., for different domains) zones.
>>>
>>> If the former, remove it from one of them and the deletion will
>>> replicate.
>>>
>>> If the latter then one wonders why the SAME DNS would be listed in
>>> 100 different zones but what the heck:
>>>
>>> Write a script using DNSCmd.exe and feed it a list (text file) of
>>> each server name to repeate the process.
>>>
>>>> Any suggestions/comments are greatly appreciated.
>>>> Regards,
>>>> Veets
>>>>
>>>>
>>>
>>>
>>
>>
>
>



Re: Removing failed DC from AD Integrated Zones by Herb

Herb
Mon May 05 18:42:40 PDT 2008


"Blake" <blake@blake.com> wrote in message
news:%23VBt%230srIHA.800@TK2MSFTNGP02.phx.gbl...
> You should be able to pull all the zones with
>
> dnscmd SERVERNAME /enumzones > .\zones.txt
>
> this will give you a list of all the zones
>
> Then something like
>
> dnscmd SERVERNAME /recorddelete ZONENAME DEADDCNAME NS /f
>
> I'd use VBS or something similiar to write a quick script to spit out 100
> command lines of the /recorddelete line

Yes, sometimes I use Perl (instead of VB but the same idea) to WRITE the
DNSCMDs rather than to necessarily execute them all.

Perl and VB can of course do either, but sometimes it is just easier to
write
something to write the command script to do the actual work.

Especially for "one off" scripts that will likely see limited reuse.

> Blake
>
>
>
>
> "Veets" <Veets@h0tmail.com> wrote in message
> news:uCKYizrrIHA.1200@TK2MSFTNGP03.phx.gbl...
>> Thanks for replying Herb
>> It was actually the latter (100 distinct domains). We do a lot of
>> internal website testing which is why we have so many of them.
>> I will take a look at DNSCmd.exe
>> Thanks again.
>> Veets
>>
>> "Herb Martin" <news@learnquick.com> wrote in message
>> news:eG1r4uqrIHA.524@TK2MSFTNGP05.phx.gbl...
>>>
>>> "Veets" <Veets@h0tmail.com> wrote in message
>>> news:%23XmttmqrIHA.2208@TK2MSFTNGP04.phx.gbl...
>>>> Hi there,
>>>> One of our Windows 2000 domain controllers died last week so we had to
>>>> remove it from AD as per the following article ->
>>>> http://support.microsoft.com/kb/216498.
>>>> The problem is we have approximately 100 Active Directly integrated DNS
>>>> zones & the 'old' DC is still listed as a Name Server (NS) in all of
>>>> them.
>>>
>>>> Is there a quick & easy to remove this entry or do we need to remove it
>>>> manually from all of the zones?
>>>
>>> Depends if you (likely) mean "100 Servers with the SAME single AD
>>> Integrated Zone" or 100 distinct (i.e., for different domains) zones.
>>>
>>> If the former, remove it from one of them and the deletion will
>>> replicate.
>>>
>>> If the latter then one wonders why the SAME DNS would be listed in
>>> 100 different zones but what the heck:
>>>
>>> Write a script using DNSCmd.exe and feed it a list (text file) of
>>> each server name to repeate the process.
>>>
>>>> Any suggestions/comments are greatly appreciated.
>>>> Regards,
>>>> Veets
>>>>
>>>>
>>>
>>>
>>
>>
>
>