|
|
This is my scenario:
I have primary and secondary DNS servers in a workgroup with no AD and all
seems to be working correctly. For example, zone transfer from primary to
secondary is correct and clients resolve IP addresses. Forward and reverse
nslookup queries from clients work correctly to the primary and secondary DNS
servers.
When I pull the network cable out from the primary DNS, a query such as
'nslookup www.address.com' is resolved by the secondary DNS server from the
Windows 2000 Server clients. i.e. the query looks for the primary dns, can't
reach it and so uses the secondary DNS. Brilliant! And other network requests
such as using a web browser also work. Again, brilliant!
So I then expected the same behaviour from my W2003 Server clients...but the
same 'nslookup www.address.com' fails because the primary DNS cannot be
reached but the nslookup doesn't then seem to try the secondary DNS server.
If I try 'nslookup www.address.com secondarydns' i.e. specify which server
the nslookup should use, then the query resolves OK.
Web browser requests from the Windows 2003 clients continue to all work
correctly so there doesn't actually appear to be a problem with the clients
or secondary DNS, more like the behaviour of nslookup is slightly different
between W2000 and W2003 clients. Can anyone shed any light on this?
I don't have any XP clients but I suspect I would get the same results. The
network settings on the W2003 machines are correctly set-up with the primary
and secondary DNS servers.
Thanks in advance.
|
|
|