Solved

DNS Resolution in Child Domain

Posted on 2009-05-13
4
503 Views
Last Modified: 2012-05-06
I'm running a Windows 2003 SP2 Environment with a newly created child domain. I'm having issues with DNS resolution from my parent - child domain. I can ping child domain workstations (from parent domain) using their IP address or by Fully qualified domain name. I'm unable to ping via netbios name though.

On the other hand I'm able to ping netbios names from the child - parent domain. I don't think that I have setup DNS correctly in the child domain and DNS isn't one of my strengths. Can someone point me in the right direction? Any ideas on what would be causing this? Thank you!
0
Comment
Question by:bsc77
  • 2
4 Comments
 
LVL 70

Accepted Solution

by:
Chris Dent earned 125 total points
ID: 24374728

Hey,

It's working exactly as it should.

To be able to resolve by Host Name only the client system must have one of two things configured:

1. A DNS Suffix Search List that includes each domain you want to search.

Typically the client will have a Primary DNS Suffix of "domain.com", so when you ping "host" you get a reply from host.domain.com. The suffix is automatically appended by the DNS Client.

So when you ping "HostInChild" then to have it resolve by host name alone you would need a DNS Suffix of "child.domain.com" so the query becomes "HostInChild.child.domain.com".

You can see the current DNS Suffix Search List by typing "ipconfig /all".

The DNS Suffix Search list can be configured in a number of places. Manually under TCP/IP settings, Advanced and DNS. Or through Group Policy.

2. A WINS Server or Relayed Broadcast

WINS holds a database of all names in a network (they have to register with the WINS server in the same way as with DNS). You can ping by host name only if you can resolve the name using WINS.

Alternatively you can relay Broadcast (although I cannot possible recommend you do). The system will craft a "Who Has <Name>" request and spam it to the entire network, hoping for a response.

Other stuff: GlobalNames

If you happen to be using Windows 2008 you can enable GlobalNames support which allows resolution by host name only to every host configured in the GlobalNames zone. But I bet you're not using 2008?

Chris
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 24374794

Oops... forgot to include the location of the Group Policy.

You will find it under:

Computer Configuration \ Administrative Templates \ Network \ DNS Client

There's a policy called "DNS Suffix Search List".

Then if your PC had a Primary DNS Suffix of domain.com, and a DNS Suffix Search List of "child1.domain.com,child2.domain.com" it would lookup the IP as follows:

nslookup host

nslookup tries: host.domain.com
nslookup tries: host.child1.domain.com
nslookup tries: host.child2.domain.com

The order is important if you have hosts of the same name across domains.

I forgot to mention resolution up the tree. In TCP/IP settings / Advanced / DNS there is an option (a tick box) that allows a client to search parent domains. The text is "Append parent suffixes of the primary DNS suffix". That makes the client do this:

Primary DNS Suffix: child1.domain.com

nslookup host

nslookup tries: host.child1.domain.com
nslookup tries: host1.domain.com

It doesn't try host.com, there's a setting that limits that buried in the registry.

Chris
0
 

Author Comment

by:bsc77
ID: 24375069
Thank you so much Chris, that worked like a charm. Just added the suffix's in my network connection and I'm golden! Have a great day, thanks again.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Resolve DNS query failed errors for Exchange
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question