secondary dns

You can ping the server,so the problem exist with the DNS configuration.
Install the DNS network services if this was not done at installation:You will manually have to install it through Add/Remove Programs applet within the Control Panel.
Now using the DNS service,use the DNS manager,to configure the service to provide your network enviroment with DNS name resolution.
Create a foward Lookup Zone
Start the DNS manager (named dns on the toolbar) from Start/Programs/Administrative Tools
In the left pane,select the domain you wish to create a foward lookup zone in to view the Foward Lookup Zone folder in the right pane
Right-click on the Foward Lookup Zone folder and select New Zone
This will initiate the new zone wizard
Follow the on screen Instructions
AD relies on DNS to resolve names to IP addresses.
Hope this Helps

This is more info:
Active Directory-integrated-relies on AD to store the master copy of the DNS databaseAD not only stores the info,it is also responsible for replicating changes to other AD-integrated servers.
Standard DNS employs primary and oneor more secondary DNS servers for each zone.
The secondary DNS servers keep up-to-date and synchronized with the primary DNS server through a replication mechanism appropiately called zone transfer.Zone transfer replicate the entire contents.
Is the TCP/IP protocol,name resolution process working whereas it can translate the correct name to IP address.
The primary DNS server is responsible for supplying any changes to the secondary DNS SERVER
The DNS should consist of one or more zone files
1)Root Hints File-a cache file that contains names and IP addresses of root
2)Zone file Stores Information that is pertinent to a specific zone.
hope this adds some light on your dilemma

The secondary DNS servers keep-up-to date and synchronized with the primary DNS server through a replication called zone transfer.
This type of zone relies on AD to store the master copy on the DNS database,which is also responsible for replicatingchanges,which is consideredd authoritive for the zone.
Changes to the DNS database can only be made to the primary,the secondary is synchronized with the primary.
Files that make up the data base
BIND Boot File-Defines startup parameters or not the DNS server is primary or secondary
The DNS database consists of one or more zone files-which holds a collection of resource records
Resource record specifiies the host address
Name Server (NS) resource records lists other name servers that contain info for a domain
Roots Hints File known as the cache file or cache hints file,it contains names and IP addresses of root servers
Name resolution also plays a part in translating a name into an IP address
Hope this helps

I believe AD domains are seperate zones as well. DNS is automatic in Win2k. I suggest you master the subject of Win2K, it's DNS, domains and forests and their organization within DNS. DOn't just guess about how they work and expect to use DNS as youdid in NT4.0. It's all differnet now....I know, I took the win2K 1560 MS 5-day course...

I think you may have a catch22 situation. You need DCs at each site to communicate in order to get the rights you need to properly setup secondary DNS. But the DCs at each site aren't talking because their sites DNS doesn't have the zone transfer working. Try making an lmhosts file with all DCs on both sites listed as well as a couple of management workstations at each site. After the lmhosts file is installed all machines need a reboot to pick up the info. lmhosts is only read at startup. Thenretry the procedures everyone else is commenting on to setup the secondary DNS server.

This question was closed by the author