Discussion Locked

DNS replication

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have an NT4 network with several remote sites joined together by various speed links - from 2mbps to 155mbps ATM. We have one primary DNS server with several secondary servers - mostly on the remote sites

For some reason the primary DNS server, in a central site, is not replicating to 1 of our remote sites.

The remote site has 2 DNS servers which should be updated by the primary DNS server, however, in the remote site you can ping -a externally & a DNS name is returned but you can't do this internally. Name resolution, on the remote site seems to be performed by WINS, i.e. a node name is returned but without the DNS attachment (NODE1 rather than NODE1.ac.uk)

The DNS table of both local servers is not uptodate with the primary DNS server.

Once I add the primary DNS server to a node in the remote network it can ping the dns name successfully.

Any ideas why the replication between the primary server & the remote servers is giving problems? The network is slow on the remote site and I suspect this is because the DNS locally is not working

Thanks in anticipation

3 replies

by cavedweller

On the primary DNS server: Are the secondary servers specified in the zone file?

On the remote server(s): Can you specify the pri server on the command line and get the right answer? Try nslookup NODE1 1.2.3.4 (substitute the server's address). Is it better if you try NODE1.domain?

Do the secondary servers know a route to the primary server?

Hopes this helps you debug a bit.

This discussion is closed to new replies.