name not being resolved

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have two computers running win2000 as domain controllers in diffrent
domains. Computer1 is a domain controller for the cohowinery.com domain.
Computer 2 is a domain controller for the cohovineyard.com domain.
Computer1's primary dns server is itself and secondary server is computer2.
Computer2's primary dns server is itelf and seconday dns server is computer1.
On computer1 I can not ping computer2 by dns name. Why would I not be able
to ping computer2 by dns name from computer1?
 
In
gmckinley said:
I have two computers running win2000 as domain
controllers in diffrent domains. Computer1 is a domain
controller for the cohowinery.com domain. Computer 2 is a
domain controller for the cohovineyard.com domain.
Computer1's primary dns server is itself and secondary
server is computer2. Computer2's primary dns server is
itelf and seconday dns server is computer1. On computer1
I can not ping computer2 by dns name. Why would I not be
able to ping computer2 by dns name from computer1?
Click to expand...

Because computer1's DNS server cannot resolve computer2's domain and is
answering not found and therefore will not even query the alternate DNS.

The DNS client will not switch to the alternate DNS unless the preferred
DNS times out. A not found answer is just as good an answer to the client as
an answer that returns an IP.

IF you want DNS 1 to resolve domain 2 then DNS 1 will need to be able to
find domain 2 by either the use of recursion or a secondary zone. Vice versa
if you want DNS 2 to resolve domain 1.
 
Its happen in multidomain environment when DCs in different domains are
unable to resolve host name. You can creat a secondary zone on domain1 for
domain2 and secondary zone on domain2 for domain1.
This will help you out.
 
Back
Top