Here's my situation (covers about 5 years):

1st - installed a Windows 2000 AD with DNS installed on W2K DC;

2nd - installed Windows 2003 DC with DNS - still mixed mode AD - AD
integrated ;

3rd - First DNS server starts to die, so we installed a new Windows 2003 DC
with DNS;

4th - removed DNS service from original Windows 2000 server;

5th - problems resulted. It seems that the AD still thinks that the
original server is a primary.

Not sure what to do at this point to let AD know that the original DNS
server is going to go away?

Thanks,
Mark

This is a first for me - I've found the answer myself (about an hour after
posting but a week after starting to look). Turns out the first DNS server
had two reverse lookup zones that weren't transfering to the other
nameservers. I looked at them and found that they were set to primary rather
than integrated. That was the problem...

D'oah!

Thanks,
Mark

In news:5E2F7515-FC9D-4B85-B57D-1A55EE0CF801@microsoft.com,
justmark <justmark@discussions.microsoft.com> typed:
> This is a first for me - I've found the answer myself (about an hour
> after posting but a week after starting to look). Turns out the
> first DNS server had two reverse lookup zones that weren't
> transfering to the other nameservers. I looked at them and found
> that they were set to primary rather than integrated. That was the
> problem...
>
> D'oah!
>
> Thanks,
> Mark

Glad you figured it out!

Ace