using short names for name resolution

Hi,

I am trying to troubleshoot short name resolution. My setup is as follows:

Windows 2003 AD forest. All child DNS servers use forwarders pointing to the
forest root DNS servers. We have no additional DNS suffixes in place.

I am trying to resolve short name resolution for a server which is in a
different child domain from my PC. This is what I am experiencing:

My PC which is in child domain 2 uses DNS server NS2. NS2 has forwarders
pointing to the forest root DNS server NS1. If I ping a sever in child domain
3 using only short name:

From my PC Ping server1. FAIL (server1.child3.root.local). Strangely, if I
was to try to ping server1 from the DNS server which my PC points at (NS2)
using only short name it is successful.

From my DNS server NS2. (ns2.child2.root.local) Ping server1 PASS
(server1.child3.root.local).

Obviously, if try to ping using FQN then this is successful. Short name
resolution is working but not consistent. Some child servers can be resolved
from other child domains but not all and yet all child DNS servers use the
same forest root DNS servers as their forwarders.

If I try to ping a different server in child 3 from my PC it is successful

From my PC (pc.child2.root.local) Ping server2
PASS (server2.child3.root.local)

"Willie Eckerslike" <Willie > wrote in
message news:4D331901-C6AB-42B6-835F-...
> Hi,
>
> I am trying to troubleshoot short name resolution. My setup is as follows:
>
> Windows 2003 AD forest. All child DNS servers use forwarders pointing to
> the
> forest root DNS servers. We have no additional DNS suffixes in place.

I assume this is a parent-child delegation.


>
> I am trying to resolve short name resolution for a server which is in a
> different child domain from my PC. This is what I am experiencing:
>
> My PC which is in child domain 2 uses DNS server NS2. NS2 has forwarders
> pointing to the forest root DNS server NS1. If I ping a sever in child
> domain
> 3 using only short name:
>
> From my PC Ping server1. FAIL (server1.child3.root.local). Strangely, if I
> was to try to ping server1 from the DNS server which my PC points at (NS2)
> using only short name it is successful.

You will need suffixes on all the child domains for the other child domains.

>
> From my DNS server NS2. (ns2.child2.root.local) Ping server1 PASS
> (server1.child3.root.local).

Ok, I'm confused wtih the naming structure. I asumed server1 would be in the
parent domain following the naming paradigm you;ve been using up to this
point, meaning that "1" is your parent, and "2" and "3" etc, are the child
domains.

>
> Obviously, if try to ping using FQN then this is successful. Short name
> resolution is working but not consistent. Some child servers can be
> resolved
> from other child domains but not all and yet all child DNS servers use the
> same forest root DNS servers as their forwarders.
>
> If I try to ping a different server in child 3 from my PC it is successful
>
> From my PC (pc.child2.root.local) Ping server2
> PASS (server2.child3.root.local)
>

Basically to get DNS in a parent-child DNS delegation, all child DNS servers
are delegated from the parent to the child domain DNS servers, there is a
forwarder on each DNS server in the child domains pointing back to the
parent, and the child members (all members, DCs, etc) have a suffix for the
other child domains.

If you need NetBIOS resolution, it should work using DirectSMB, however in
many cases, some apps do not use DirectSMB such as some Exchange/Outlook
functions, SQL and others that actually use NetBT, you may need to use WINS
in the infrastructure.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.