Newly added Windows 2000 PDC server with AD. (My first time with AD). This server is "server.newdomain.com". There are other, older NT servers on this LAN, too. They are in another NT domain and they are also in "olddomain.com". I have set up trust relationships between new and old NT domains.
Internal DNS server on the new W2K server. Has FLZ entries for newdomain.com (itself) and Forwarders is active to the ISP's DNS servers.
This internal DNS ALSO has FLZ zone entries for the local servers that still belong to olddomain.com.
Problem: when doing a nslookup for a host that is not on this LAN that belongs to the olddomain.com, it fails. (as in mail.olddomain.com, which is in another city....)
My assumption was that it would forward this request to the ISP's DNS servers if not found in it's own entries. Obviously not, I guess, if the domain being queried is found in it's FLZ entries...
I suppose I can work around this by either adding all the olddomain.com entries to this DNS server or to the hosts file. But I was hoping to learn what I'm doing wrong with my
DNS.
Thanks in advance for all your help.....
Internal DNS server on the new W2K server. Has FLZ entries for newdomain.com (itself) and Forwarders is active to the ISP's DNS servers.
This internal DNS ALSO has FLZ zone entries for the local servers that still belong to olddomain.com.
Problem: when doing a nslookup for a host that is not on this LAN that belongs to the olddomain.com, it fails. (as in mail.olddomain.com, which is in another city....)
My assumption was that it would forward this request to the ISP's DNS servers if not found in it's own entries. Obviously not, I guess, if the domain being queried is found in it's FLZ entries...
I suppose I can work around this by either adding all the olddomain.com entries to this DNS server or to the hosts file. But I was hoping to learn what I'm doing wrong with my
DNS.
Thanks in advance for all your help.....