Hi JDK,
Here is what I suggest:
1. Install NT 4.0 on the new server. Join it to the domain, and when you are sure everything is good, promote it to PDC.
2. Take the BDC off-line. If something goes wrong, you can promote this BDC to PDC to restore your NT domain.
3. Upgrade the new PDC to Windows 2000, install SP3 (I still don't trust SP4) and any other updates you want.
4. When you are convinced that the new machine is stable, bring the BDC back on-line.
You will now have a "mixed mode" 2000 domain. In mixed mode, NT BDCs and member servers behave as though they are in an NT domain. In many respects, they are.
You are correct that Windows 2000 domains do not have the PDC/BDC distinction, there are only domain controllers and member servers. In theory, all DCs have a writable copy of the user database (well, and other things too). However, in a mixed mode domain, there is only server with a writable copy of the database.
In Windows 2000 domains, all DCs are equal, but some are more equal than others. There are three "roles" that only one DC per domain can have, and two "roles" that only one DC per forest can have. The forest-wide roles are Schema Master and Domain Naming Master, and the domain-wide roles are RID Master, Infrastructure Master, and PDC Emulator. Your new 2000 server will have all five of these roles to begin with, as well as being global catalog server.
As the PDC Emulator, the new server will have the only writable copy of the user database. The NT BDCs still have a read-only copy. The new server will behave just like an NT PDC for the BDCs.
I highly recommend that you introduce at least one more Windows 2000 DC into this domain as soon as you can and transfer some of the roles to it. When you are ready to do this, post here again for advice on which roles to transfer.
Regards,
z.