Recommended FQDN (domain name) for SBS 2003
Hi - in SBS Unleashed by Neale, et al - p.49
There is a consideration of naming the domain something other than .local because using .local prevents Mac from performing name resolution.
What experiences have you all had using the alternative suggestions in the book .office and .lan? How about I use something like sfden.office?
Is there a minimum or maximum when considering the name of the domain?
The mac's I'll be integrating will most likely be running XPPro on parallels or bootcamp, but I want to be able to integrate them running osx too...
thanks.
There is a consideration of naming the domain something other than .local because using .local prevents Mac from performing name resolution.
What experiences have you all had using the alternative suggestions in the book .office and .lan? How about I use something like sfden.office?
Is there a minimum or maximum when considering the name of the domain?
The mac's I'll be integrating will most likely be running XPPro on parallels or bootcamp, but I want to be able to integrate them running osx too...
thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, thanks everyone for the useful information.
Trouble is - I'm even more confused now.
I think I will go with pdent.lan
Since I don't go with .local, will i need to do additional configuring?
What real world issues will i face with this name given my SBS 2003 server, 3 XP Pro machines and 1-2 OSX 10.5 machines? Does SBS 'like' .local more - ie. does its services look for .local by default or something?
Trouble is - I'm even more confused now.
I think I will go with pdent.lan
Since I don't go with .local, will i need to do additional configuring?
What real world issues will i face with this name given my SBS 2003 server, 3 XP Pro machines and 1-2 OSX 10.5 machines? Does SBS 'like' .local more - ie. does its services look for .local by default or something?
You won't face any other more issues than you would with .local. Just because .local is generally recommended for SBS, does not mean that it is required or has special meaning.
Services, etc. are configured when AD is installed - so if you choose pdent.lan, that is the name they will look for - no issues in this regard will occur. You do exactly the same setup as if you were using .local, you just put .lan in instead!
Services, etc. are configured when AD is installed - so if you choose pdent.lan, that is the name they will look for - no issues in this regard will occur. You do exactly the same setup as if you were using .local, you just put .lan in instead!
ASKER
Thanks for addressing that - I am simply jittery setting up my first sbs!
>>I am simply jittery setting up my first sbs!
Good, that will mean you follow the instructions to the letter. pdent.lan will be a perfect internal domain for you, now just run through the guide to install and configure SBS and you will be away in no time.
SBS is a product that will make you look really good if you follow the installation guide :)
Good, that will mean you follow the instructions to the letter. pdent.lan will be a perfect internal domain for you, now just run through the guide to install and configure SBS and you will be away in no time.
SBS is a product that will make you look really good if you follow the installation guide :)
So, short and sweet really...