We've adopted a network that includes one Windows Server 2003 domain controller and about 70 workstaions of varying types. Mostly XP, a few W2Ks and a few Window 7s. There are also a couple of member servers. The domain controller is running DNS as well as AD. I immediately noticed a lot of strange behaviour on the network. Things like workstations and member servers being able to join the domin properly but not being able to log on after joining, citing reasons like "a domain controller for this domain cannot be found". I then discovered about a dozen regularly occuring error (red) and warning (yellow) events in the system, applicaion, directory and dns logs that suggest communicaion issues between AD and DNS. Then when I looked at the DNS applicaiton I discoverd that there are no forward lookup zones. Obviously there are no DNS records in those forward lookup zones because the forward lookkup zones dont exist. There are three reverse lookup zones each with two records in them. The strange thing is that the network is still reasonably functional. Alot of staff members can log on wth their domain accounts and those that cant just log on with local workstation acoounts. The bottom line is that I need to get rid of this strange behaviour, fix the errors, and get the DNS server working as it should. Any help would be appricated.