I work for a department in a large organization which uses static IP & DNS. It’s a mixed environment: There are Win xp and 2000 clients, and NT 4.0 domain controllers, 2003 servers and unix, and IBM mainframes. A couple of departments, including our own have decided we want to upgrade our NT 4.0 DCs to 2003 server Active directory DCs. All of the clients in all of the departments use the same static DNS servers, and the clients names are all client.beach.state.hi.us, but in fact there is no beach.state.hi.us domain.
Anyway, in a test environment I created a 2003 DC for beach.state.hi.us for our department. Depending on how I set TCP/IP on our clients we have different results:
If I use one of the static DNS servers as the primary DNS server and the DC as the secondary DNS server, it takes a long time to logon (its "applying policies" forever). In the event viewer I notice a lot of errors "cannot find user or domain" And then the client cannot browse active directory.
If I use the DC as the primary DNS server in the client's TCP/IP setting and use the static DNS servers as secondary and 3rd DNS servers, then these problems are not there, but some applications cannot resolve names. For example a terminal emulator cannot resolve the IP for a unix server named WAVES.
I cannot make changes on the static DNS server (other than client name change requests) nor on the servers or clients in other departments that we might access. I'm wondering if there might be a way of configuring our DC or setting up another DDNS server to query the static DNS servers on behalf of the clients in our AD domain (and perhaps cache responses). In otherwords, our clients might then use the DDNS as their primary or their only DDNS server.