What correct domain name should I use in W2K3?
Hi,
Will setup Windows 2003 R2 Standard as domain controller. I have my own domain name registered, let name it example.com. Web site is hosted on my IPS's server somewhere outside, and Windows 2003 server will be inside my small home-based office network with some Windows workstations and 1-2 MACs. What is the domain name which should I provide during AD setup?
Should it be example.com (I may decide later host my Web site internally, for example), or it should be example.local as it suggested by Microsoft? If it is example.local, I think I will have problems joining a domain from Macs, so in my case it must be something different. I don't know, but are domain names like:
example.lcl
example.internal
local.example.com
local.example
office.example.com
usable and suitable in my case, and why? I googled a while, but can't find any detailed explanation how to name the domain during Active Directory setup. I mean, I know about DNS, but I don't know how is correct to name it in AD.
Is the domain name tied, for instance, with Exchange server in case I will install it later on this server or if it already included in installation, how it is with Windows 2003 SMB?
Is there any difference in this case if I am using Windows 2000 instead of 2003?
Please, explain why your solution is recommended. Thank you.
Will setup Windows 2003 R2 Standard as domain controller. I have my own domain name registered, let name it example.com. Web site is hosted on my IPS's server somewhere outside, and Windows 2003 server will be inside my small home-based office network with some Windows workstations and 1-2 MACs. What is the domain name which should I provide during AD setup?
Should it be example.com (I may decide later host my Web site internally, for example), or it should be example.local as it suggested by Microsoft? If it is example.local, I think I will have problems joining a domain from Macs, so in my case it must be something different. I don't know, but are domain names like:
example.lcl
example.internal
local.example.com
local.example
office.example.com
usable and suitable in my case, and why? I googled a while, but can't find any detailed explanation how to name the domain during Active Directory setup. I mean, I know about DNS, but I don't know how is correct to name it in AD.
Is the domain name tied, for instance, with Exchange server in case I will install it later on this server or if it already included in installation, how it is with Windows 2003 SMB?
Is there any difference in this case if I am using Windows 2000 instead of 2003?
Please, explain why your solution is recommended. Thank you.
ASKER
It's because .local is sort of reserved name for Mac, but for different purpose, and during the installation of AD Windows informed about possible conflict if I use example.local domain name.
ahhh, well then you could use example.msft or example.internal or example.com
If you REALLY wanted to, you could use microsoft.com - of course, then you would have to mess with your DNS if you ever wanted to browse to www. or windowsupdate. - but you get the point.
If you REALLY wanted to, you could use microsoft.com - of course, then you would have to mess with your DNS if you ever wanted to browse to www. or windowsupdate. - but you get the point.
the only arguement i see is clueless people not being able to differenciate between the internal domain and the external domain. this however is not the case alot of the time. I personally tend to use corp.blahlah.com.au or int.blahblah.com.au
ASKER
In my case I'm talking about internal domain, I guess...
Make it .lcl - That should be fine. I do not recommend using the actual domain name - I've found this can cause DNS issues when trying to access your own setup. There should be no problem later hosting e-mail for your domain or your web site. Simply configuring a publicly accessible DNS is all you need to worry about. IIS supports Host Headers and can respond to any domain name if configured. Exchange is not a problem as it too can handle multiple domain names without issue.
one benifit of using your real fqdn is pda's will work internally over wireless and externally using the internet seemlessly without having to create fake records in on your internal dns servers.
>>the only arguement i see is clueless people not being able to differenciate between the internal domain and the external domain.
I wholeheartedly agree,
And, users find it far easier to log on to OWA or whatever as username@domain.com - as this is generally their email address as well - than other places where users have to remember username@internaldomain.lo
Making users remember anymore than they have to is a sure fire way to cause problems.
Using your external domain as an internal domain is only ever a problem for administrative staff, and if configured properly, should not be a problem at all.
leew, do you actually have a reason for not using the real domain name? I would love to hear it.
-red
I wholeheartedly agree,
And, users find it far easier to log on to OWA or whatever as username@domain.com - as this is generally their email address as well - than other places where users have to remember username@internaldomain.lo
Making users remember anymore than they have to is a sure fire way to cause problems.
Using your external domain as an internal domain is only ever a problem for administrative staff, and if configured properly, should not be a problem at all.
leew, do you actually have a reason for not using the real domain name? I would love to hear it.
-red
I agree slappa1, the problem is that you will have to create fake records anyway if your mail or website is hosted externally.
Which is actually my point - no matter what you do, you are going to need to configure yourself for it properly with DNS. Why confuse the issue by adding in a bogus DNS domain?
Which is actually my point - no matter what you do, you are going to need to configure yourself for it properly with DNS. Why confuse the issue by adding in a bogus DNS domain?
True, it just comes down to what people are more comfortable doing it really doesn't make a difference either way to someone that knows and understands what they are doing, and how it all hangs together.
I haven't had the inclination to further test things, but my own home network is setup using a routable internet address and there are issues for me when trying to access my sites internally.
In addition, you remove direct access to your domain through the internet as .lcl or .local are NOT resolvable.
ASKER
OK, so example.com is correct name and it is far easier for users to memorize for OWA. names like example.local or example.office are more secure because they are not resolvable. I both cases it will be necessary to perform similar setup, right? So what is the solution?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, Red. But, why the default internal domain name for Windows 2003 server is example.local ?
Is that question "Why are Microsoft recommending I use a .local DNS name?"
If so, I can answer that with another question;
Why is there a microsoft KB article giving out bad information, instruction that using a smart host on a virtual smtp server is a good thing to do (when it is widely accepted this is a terrible thing to do)?
Sometimes, the instructions given are not the best, but rather, the easiest. MS have to prepare themselves for the lowest common denominator - there are a lot of thick netadmins out there, and using .local for them is not such a bad idea - second, things change, .local addresses can have their uses, and 8 or so years ago when they became prevelant in 2000 domains, having a non-routable domain name would have sounded like a great idea.
-red
If so, I can answer that with another question;
Why is there a microsoft KB article giving out bad information, instruction that using a smart host on a virtual smtp server is a good thing to do (when it is widely accepted this is a terrible thing to do)?
Sometimes, the instructions given are not the best, but rather, the easiest. MS have to prepare themselves for the lowest common denominator - there are a lot of thick netadmins out there, and using .local for them is not such a bad idea - second, things change, .local addresses can have their uses, and 8 or so years ago when they became prevelant in 2000 domains, having a non-routable domain name would have sounded like a great idea.
-red
The argument for using .local or a .com will go on for a long time. Even Microsoft cannot make up their mind. The only exception to that is SBS which virtually forces you to use the .local - but then you end up putting in a split DNS system anyway.
Go with what you are comfortable with. If you decide not to use your own domain name, but a non-existing domain, then use .local and nothing else. I am always concerned with shorter TLDs that they could get used by someone on the internet causing all sorts of problems. The .local domain is so well used that ICANN and its members wouldn't even dream of suggesting that one to be used for public domains.
Simon.
Go with what you are comfortable with. If you decide not to use your own domain name, but a non-existing domain, then use .local and nothing else. I am always concerned with shorter TLDs that they could get used by someone on the internet causing all sorts of problems. The .local domain is so well used that ICANN and its members wouldn't even dream of suggesting that one to be used for public domains.
Simon.
ASKER
Thanks for all comments. It looks like example.com is better name than something like example.local in case I have registered domain name example.com
But, what about domain names like local.example.com or office.example.com? When and is it good idea to use this domain name for my domain controller? I am still not sure what is the correct name I should choose. Or for primary DC is better to use just example.com? Thanks.
But, what about domain names like local.example.com or office.example.com? When and is it good idea to use this domain name for my domain controller? I am still not sure what is the correct name I should choose. Or for primary DC is better to use just example.com? Thanks.
Don't confuse the machine name with the domain name. They are very different.
Machine names can be pretty much what you like. I tend to go down the route of server1, server2 etc.
If you are going to use a real domain name like example.com then make sure that you own the domain name. Don't use another one as that will cause you problems and the real owners of the domain will not be happy with you.
Simon.
Machine names can be pretty much what you like. I tend to go down the route of server1, server2 etc.
If you are going to use a real domain name like example.com then make sure that you own the domain name. Don't use another one as that will cause you problems and the real owners of the domain will not be happy with you.
Simon.
Personally, if there is any chance of having exchange hosted internally, I always use the real domain - so example.com
There are people that say that this creates problems, but I, as well as a few well respected Microsoft MVPs also do this commercially. I am yet to see a really good argument to not use example.com
Of course, no matter what you choose, exchange will not care - it just requires more or less configuration (but nothing special).
If you think the macs will have problems, you could try using example.com or maybe even example.internal - then again, I dont know why they macs would have problems!
-red