Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 40
  • Last Modified:

Probably a very simple answer to a DNS and child domain question

Need some help if possible please.
We've led a sheltered existence in our organisation with a simple one domain forest with not many servers all on the same network, contiguous IP addresses etc.
We would now like to add a child domain (server 2012r2) to our existing (server 2008) domain, so we will have TEST.NET and CHILD.TEST.NET
I have added the  child domain and for the most part everything is working fine, however from the original (TEST.NET) domain, in order to get to any servers in the child domain i have to type the FQDN of computername.child.test.net, instead of just being able to type the computer name.
From the child domain though i just need to type the computer name of a server/workstation in the root domain and it will find it no problem without typing the FQDN.
Please could somebody tell me if there is a way to be able to just type the computer name without the FQDN so that i can browse all computers withing the forest (and across domains?)
I have tried creating a secondary zone of the child.test.net DNS on the test.net primary server and this shows all of the child domains DNS entries, but i still need to type the FQDN to get it to ping.
Thanks in advance
0
parxuk
Asked:
parxuk
  • 4
1 Solution
 
Jan SpringerCommented:
In the zone "test.net" create to however many deep as RFC suggests or limits.  The only time that you would put "child" in its own zone is if the zone is large (and then you still must provide NS records) or if the nameservers reside elsewhere.

So, you can add, "youngest.child" and "oldest.child" or just "child" in the zone "test.net".
1
 
footechCommented:
The issue is all about which DNS suffixes your clients will try appending when you only provide a hostname.  Defaults are to append primary and connection specific suffixes, which would be determined by domain membership and DHCP, respectively, though they could also be set manually.  You would need to add the child.test.net domain to the list of suffixes for clients in the test.net domain.  Easiest way to do this is probably via Group Policy.
1
 
parxukAuthor Commented:
Thanks for the help.

Its actually only 1 machine on the parent domain that needs visibility of the client domain, so I have implemented a suffix on the network connection of that machine, and now it can resolve fine.

Thx again
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
footechCommented:
Glad to help.
Please close the question and award points as you see appropriate.
0
 
footechCommented:
@parxuk - Another reminder, please close this question.  Thanks.
0
 
footechCommented:
The author confirmed that #a41719432 was the solution.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now