In
Glen Williamson said:
Thanks very much for replying, but the two domains are
separate entities. I don't want everyone from domain2 to
query domain1.
It is not going to be possible to control who DNS resolves any domain for.
IT is either going to resolve it for everyone or nobody. The only thing you
can do is control who can access the resources and who can't.
The only suggestion I can give you is to pull secondary zones from the other
domain's DNS. Then use your access control list to control access.
You certainly don't want these two DNS servers forwarding to each other
either, that would set up a DNS loop that would bring both DNS servers down.
Then, you'd have everybody on your case.
Domain1 has DNS active directory integrated and domain2
has its own active directory. I would like to use
domain2 to serve only the domain2 clients and query
Domain1 when it can't resolve.
This would require forwarding, like I said, you don't want two DNS servers
forwarding to each other.
The problem occurs when installing DNS on Domain2. It
asks the question when configuring the server whether
there is another DNS on the network. If I put in the IP
of Domain1, it tells me that its not available.
I can however ping Domain1. Any further help would be
much appreciated
You can't rely on ping to test DNS connectivity because it uses the wrong
protocol, for you to test DNS connectivity you need to use nslookup, dig or
Netdig. Netdig by William Stacey is available from
www.mvptools.com has
become my favorite DNS tool because of its eas of use. It has a GUI version,
its only requirement is .NET Framework but, if you run it from a network
drive you have to adjust its trust. Netdig makes it easy to check both UDP
and TCP DNS connectivity. You just put the DNS server in the server field by
name or IP, select the option on the query, select the query and the type
records your querying for.