Must use FQDN to resolve?

[rubiconx]

Here's what's going on, had 2 DNS servers set up running on 2000. I could resolve a name (via ping, etc) by just typing in the machine name for computers in the network or in one of the secondary zones set up. I've added a 3rd server running DNS which is 2003 and now the master server, all appears well except for one issue.

When I try to resolve a machine name from one of the secondary zones (which are outside of our domain) not using the FQDN it fails with domain unknown but only from the new 2003 server or computers pointing to it. If I flush dns and try this from one of the 2000 DNS servers it works. Resolving using the FQDN works fine from all machines.

The secondary zones are being transfered correctly and the machine names I'm trying to ping/resolve are listed. Any ideas why this is happening or if this is working as it should? Thanks in advance.

 

[Ztrek7]

Don't have a answer for why, I suspect is a "feature" of Windows 2003.

But, do have a work around for you, in the TCP/IP settings of the network adapter, just create an append list to your DNS suffixes.

 

[kbing]

the problem is likely because the DNS system doesn't know how to locate the sub-domains. If there are master DNS servers for those sub-domains, create NS records to point to them for those domains.

Another thing you could do is add forwarders to DNS that point to the domains DNS systems you need it to query.

 

[ShackDaddy]

Were you also running WINS on the 2000 servers, and had you set up the DNS server properties to use WINS to answer DNS queries? That would cause this if you hadn't done the same with the 2003 server.