Active Directory - using .local
#1
Moderator
Thread Starter
Join Date: Dec 1998
Location: Staffs
Posts: 23,573
Likes: 0
Received 0 Likes
on
0 Posts
Just come across something new in the SBS 2000 installer. I'd swear blind it wasn't in the other versions of SBS 2000 I've done. I think it's new in this 'version' of SBS 2000 that has W2000 SP3 rolled into it.
Anyway, the installer now recommends that instead of using your FQDN for your Active Directory domain name ie abc.co.uk, you use abc.local.
The installer say it's more secure to keep your internal setup seperate from your public domain and avoids DNS "issues".
What's the thinking behind this? Not saying it's wrong, just wondering why.
TIA,
Chris.
Anyway, the installer now recommends that instead of using your FQDN for your Active Directory domain name ie abc.co.uk, you use abc.local.
The installer say it's more secure to keep your internal setup seperate from your public domain and avoids DNS "issues".
What's the thinking behind this? Not saying it's wrong, just wondering why.
TIA,
Chris.
#2
Scooby Regular
There have been a number of issues with W2K sites publishing their complete infrastructure on the Web. Also you could wipe out (say) WWW.abc.co.uk by naming a machine www, all good fun !
I've always recomended that sites use .pri internally
Jeff
I've always recomended that sites use .pri internally
Jeff
#3
Chris
I recon thats part of there new 'Trustworth computing' initiative and something I agree with and have done as a matter of course in the past.
.local, .priv or even .internal.scoobynet.com works for me too.
Mind you theres not so many ISP's that except Dynamic Updates anyway.
Ids
I recon thats part of there new 'Trustworth computing' initiative and something I agree with and have done as a matter of course in the past.
.local, .priv or even .internal.scoobynet.com works for me too.
Mind you theres not so many ISP's that except Dynamic Updates anyway.
Ids
Thread
Thread Starter
Forum
Replies
Last Post
domu
ScoobyNet General
7
03 October 2015 03:46 AM