Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Best practice and method while installing DNS in workgroup environment...

Posted on 2009-05-11
4
Medium Priority
?
208 Views
Last Modified: 2012-05-06
Hi friends !

I have installed DNS in the same installation of Active Directory and managed Domain Controller too. But I never installed DNS in workgroup.

Through my previous post here on experts-exchange, I came to know about ins and outs of DNS in workgroup. Yet I want to install DNS in workgroup as per the agreement of our IT department.

My idea is to will bring all the internal clients in same workgroup i.e. XYZ and in System Properties--->Computer Name---->Change--->More---->Primary DNS Suffix of this computer, I will give xyz.internal, SO THAT all computers make entry in DNS themselves (and I wont have hurdles to manually enter them.)

Tell me:

1. Do we use the same (.) in DNS while installing it WITHOUT Active Directory. I mean to say that while installing DNS, do we HAVE TO use something like xyz.internal (as we use in Domain environment) or just XYZ is OK ?

2. We have our public domain: xyz.ac.in. Should I use the same for internal DNS or I should use something like xyz.internal as mentioned above ?

Please comment on my ideas and tell me the best practices while using DNS in Workgroup environment. Also tell me one important thing about DNS Name.

Regards
0
Comment
Question by:JatinHemant
  • 2
  • 2
4 Comments
 
LVL 71

Assisted Solution

by:Chris Dent
Chris Dent earned 750 total points
ID: 24362127

1. Clients won't register in just "XYZ" without registry changes on each system. Because of that I advise you use a full name, xyz.internal is fine if you like that one.

2. You could, but it would be better to use "internal.xyz.ac.in" as it keeps it out of the way of xyz.ac.in. If you were to use your public name you would have to create a version of each public record on your internal DNS server. Unnecessary work.

Chris
0
 

Author Comment

by:JatinHemant
ID: 24372765
Chris ! Thanks for your reply.

at 1:
As you are advising to use "xyz.internal", means that "." can be used in DNS Naming even when we are NOT installing it in Active Directory environment and we are using Workgroup environment. Am I getting right ? Please clarify.

at 2:
************************You could, but it would be better to use "internal.xyz.ac.in"************************
I am confused.
If I use "xyz.internal" then FQDN of a PC1 will be: PC1.xyz.internalI
If I use "internal.xyz.ac".in then FQDN of PC1 will be: PC1.internal.xyz.ac.in

Please clarify which is better and what is your mean by this statement:
************************If you were to use your public name you would have to create a version of each public record on your internal DNS server.************************

Regards.
0
 
LVL 71

Accepted Solution

by:
Chris Dent earned 750 total points
ID: 24372801

1. You are correct. DNS naming is quite separate from AD, there are few limitations on what the name can be.

2. There are no rules that say you must use one over the other. You could use either xyz.internal, or internal.xyz.ac.in. Both are valid it really just depends which format you prefer.

If you were going for an AD Domain I'd suggest you use "internal.xyz.ac.in", but there's no harm in using the made up ".internal" suffix for a made up domain on a workgroup.

> If you were to use your public name

If you were to call your internal domain name "xyz.ac.in" you would find that you would not be able to get to "www.xyz.ac.in".

To get there you would have to tell your server where www is (in the same way as you tell it where PC1 is). DNS won't forward the request for www off to your public DNS servers while it believes it know everything about xyz.ac.in.

Chris
0
 

Author Comment

by:JatinHemant
ID: 24374207
Thanks for your reply.

I got it.

Regards.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

Had a business requirement to store the mobile number in an environmental variable. This is just a quick article on how this was done.
Group policies can be applied selectively to specific devices with the help of groups. Utilising this, it is possible to phase-in group policies, over a period of time, by randomly adding non-members user or computers at a set interval, to a group f…
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…
Suggested Courses

971 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