DNS Problems

Hi Guys
I have a problem, that I seem to be making worse with every effort to fix
it.
At the moment I have about 150 workstations xp/nt/98/mac all running on
workgroup with 4 2000/2003 servers
I have installed a 2003 domain controller with active directory which
obviously has to point at itself for DNS.
So I set up forwarders to my current DNS server - Linux, which seems to be
ok, but I can't get my workstations to connect to the domain, I get "A
domain controller for the domain xxx could not be contacted" on XP
workstation.
So I ran dcdiag on the DC and get server GUID DNS name could not be resolved
to an IP address.....
Does anyone know of a how to for installing a DC with an existing DNS server
and setting up DNS CORRECTLY, because I don't think i've done it right, or
just any other suggestions.

TIA

--
Steven Cooke

<snippage>
> Does anyone know of a how to for installing
> a DC with an existing DNS server and setting
> up DNS CORRECTLY, because I don't think
> i've done it right, or just any other suggestions.

Hmm ... you aren't giving too much details here :-)
but in any case .. I suspect that the problem is due
to the handling of the DNS AD "zones"; the *nix DNS
has no idea about AD, and this causes the DC issues
you've seen; I'd try setting up the windows DNS as a
primary for the zone (along with all the needed AD
zones); once you'll be up and running this way you
may as well delegate the "regular" DNS zones to
your *nix DNS .. although I'm not sure I'd setup the
whole thing this way; usually, when it comes to AD
I prefer keeping all the data on a windows DNS and
if needed, using *nix DNS as forwarders for external
resolution and/or to serve public domain data