---------------------- I'm sorry to say that I've read quite a bit (http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/directory/activedirectory/stepbystep/addomcon.mspx) (http://technet2.microsoft.com/windowsserver/en/library/54572f43-7c5f-4600-b8ff-3c91cf0541ed1033.mspx?mfr=true) (http://technet2.microsoft.com/windowsserver/en/library/00c5878b-c32c-43d9-bf00-04c58030627e1033.mspx?mfr=true) from Microsoft regarding this topic and still haven't gotten it right. I brought a new BDC up in our domain. I used DC Promo and followed the steps to add an additional domain controller to an existing domain and configure DNS - then bing-bang-boom it was done. Almost. The DNS part hasn't gone well. When I initially followed the steps an error was generated that mentioned something about a domain controller already being assigned to the domain. Anyway if I run ipconfig /all from any machine in the network a second DNS server isn't listed. Here's some facts: The only server OS we use is Windows 2003 R2 SP2. There is a forward lookup record for both name servers showing in Active Directory On my BDC the SOA shows the name of the BDC On my PDC the SOA shows the name of the PDC My PDC has a static IP address with the BDC's IP address as it's primary DNS server address MY BDC has a static IP address with the PDC's IP address as it's primary DNS server address We don't use Group Policy (although I don't know if that matters) I did find one or two erroneous references to old domain controllers throughout Active Directory. They all had different IP addresses than the current PDC and BDC so I deleted the records as I found them. I don't know what else to write. If more information is needed I will be happy to supply it. Thanks for the help.

First issue is Windows 2003 and Active Directory terminology. In AD there are no pdc or bdc. Those only exist in NT. There are the FSMO roles and there is a pdc emulator role but that is not the same as in NT and there is no bdc role. It would appear you installed DNS correctly as AD Intergrated. The SOA's are correct. "a second DNS server isn't listed." You have to setup DHCP to provide it. DNS does not update dhcp. Imagine the power if you knew how to internet search

Thank you, thank you. I guess I didn't look as closely at this as I thought I had when I started. I now see in DHCP Scope Options where the DNS server entry is and added my other DNS server's IP address. Took it a step further and set up Server Options to reflect this information. Sorry about the terminology. The only people I've ever talked about this stuff with started in the NT days and its the only terminology I know. When I go for my MCSA or MCSE (probably MCSA) I'll learn this stuff the right way. Thanks again for the help. Po