Question : Oddities when setting up a secondary dns server

The other day I tried setting up a new secondary DNS server.  While I was going through some of the steps in the KB I noticed that not all the steps matched up, then realizing I was following instructions for windows NT and not Server 2003 I simply removed the DNS service from the second server.

Today I went to re-attempt this with these instructions (http://support.microsoft.com/kb/816518).  When I finished my dns snapins look the same as they did in the previous attempt and I think things are just all screwed up, I'm not sure how to proceed at all right now.  Does everything appear ok in my primary DNS?  Any idea why the secondary dns snapin would look so different?

The new server is called CRBPServer.

Answer : Oddities when setting up a secondary dns server

chuku,
the current problem that bradlee27514 is trying to solve is the "strange" display resulting from a customized MMC.
If the zones on his current primary server are standard primary (and this seems to be the case, because otherwise, there would be errors in the event log), then his current configuration is *absolutely* *correct*. Not optimal, but correct.
The existing zones will *only* be transferred automatically if they are already configured as AD integrated zones.
Please try not to confuse a user who doesn't seem to have too much experience with Windows DNS by giving unrelated and incomplete information.

bradlee27514,
try double-clicking the dnsmgmt.msc that you copied over from the secondary machine.