DNS problems resolving on a member server - Server 2003

Archived from groups: microsoft.public.win2000.dns (More info?)

I have a member downstream server which is running DNS (same location). I
planning to use this on a separate VLAN in one of our testing areas.
Eventually this will forward to the production DNS.

There is a primary forward and a primary reverse zone. The forward zone
cannot resolve, as everything is timing out. The setup appears to be fine.
The zone name space is different to the production environmet, although both
are in the same domain. Not sure if this matters.

The reverse zone appears to resolve the server name, however I created a
dummy PTR record which did not resolve.

This is the first time I'm setting up a DNS server on a member server and am
after some advice on this one. Because this is a member server the zones
are not directory integrated. The SOA records are pointing to the server by
it's production name space.

I hope this makes sense and someone can assist.

Cheers,