2.731.3132
-Original Message-
From: Joseph Heaton [mailto:jhea...@dfg.ca.gov]
Sent: Wednesday, April 28, 2010 9:22 AM
To: NT System Admin Issues
Subject: Current AD domain naming best practices
We are currently in the beginning phases of migrating from Novell e-Directory,
to AD. We
On Wed, Apr 28, 2010 at 4:48 PM, Michael B. Smith wrote:
> You won't get that for .int or .local.
.int? I take it some people are using that for "internal"? Heh. I
guess people have forgotten is a "real" top-level domain name.
It is used for international organizations. Try http://www.nato
nd Exchange MVP
http://TheEssentialExchange.com
-Original Message-
From: Joseph Heaton [mailto:jhea...@dfg.ca.gov]
Sent: Wednesday, April 28, 2010 3:57 PM
To: NT System Admin Issues
Subject: Re: Current AD domain naming best practices
I'm simply gathering information on the 3 o
: Wednesday, April 28, 2010 7:59 AM
To: NT System Admin Issues
Subject: RE: Current AD domain naming best practices
David,
Could you profile the differences in managing each of these? Is one "easier"
than the others?
>>> David Lum 4/28/2010 7:49 AM >>>
%dayjob% does s
I'm simply gathering information on the 3 options, and what everyone
recommends. Unfortunately, there is no clear-cut "winner". I've found that
all 3 are valid options, depending on how much administrative overhead you want
to add to the process. However, Michael Smith brought up a rather str
A subdomain is fine, but suffers many of the same drawbacks as using a
single DNS namespace.
And you're involving more DNS servers into the resolution process for what
purpose again?
-ASB: http://XeeSM.com/AndrewBaker
Sent from my Motorola Droid
On Apr 28, 2010 12:51 PM, "Joseph Heaton" wrote:
Andrew,
So you don't recommend the subdomain? Also, if you could expand on your
answer, it'd be great, as I'm bringing all ideas to a meeting this afternoon,
with pros/cons behind each option.
>>> "Andrew S. Baker" 4/28/2010 8:55 AM >>>
Use two separate domain names, even if you register the
Use two separate domain names, even if you register the internal one.
You can avoid all manner of political complexity this way plus support all
your external services as well.
-ASB: http://XeeSM.com/AndrewBaker
Sent from my Motorola Droid
On Apr 28, 2010 10:23 AM, "Joseph Heaton" wrote:
We a
On Wed, Apr 28, 2010 at 11:16 AM, Glen Johnson wrote:
> Say I have OWA secured. How does a cert work if I access it internally
> via owa.vhcc.local versus externally via owa.vhcc.edu?
You generate a different cert for different sites. That's how SSL
works. For internal sites, create your own
On Wed, Apr 28, 2010 at 10:22 AM, Joseph Heaton wrote:
> ... my thinking, and the other Windows admins, is that having the
> same FQDN internally would be ok.
I recommend strongly against creating disjoint namespaces in DNS.
Sure, it's possible, but it can create a number of IT management
heada
Admin Issues
Subject: Current AD domain naming best practices
We are currently in the beginning phases of migrating from Novell
e-Directory, to AD. We are having discussions to decide on a new
internal domain name. I know that years ago, it was best practice to
have a different internal domain
other client is same
inside/outside (I inherited this setup).
Dave
-Original Message-
From: Jacob [mailto:ja...@excaliburfilms.com]
Sent: Wednesday, April 28, 2010 7:42 AM
To: NT System Admin Issues
Subject: RE: Current AD domain naming best practices
What we use... sub-domain.
, 2010 7:42 AM
To: NT System Admin Issues
Subject: RE: Current AD domain naming best practices
What we use... sub-domain. Have had no issues for years.
-Original Message-
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Wednesday, April 28, 2010 7:31 AM
To: NT System Admin Issues
ple.com) of your external
domain.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
-Original Message-
From: John Aldrich [mailto:jaldr...@blueridgecarpet.com]
Sent: Wednesday, April 28, 2010 10:30 AM
To: NT System Admin Issues
Subject: RE:
What we use... sub-domain. Have had no issues for years.
-Original Message-
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Wednesday, April 28, 2010 7:31 AM
To: NT System Admin Issues
Subject: RE: Current AD domain naming best practices
This will _KILL_ you if you ever need
al Message-
From: Joseph Heaton [mailto:jhea...@dfg.ca.gov]
Sent: Wednesday, April 28, 2010 10:22 AM
To: NT System Admin Issues
Subject: Current AD domain naming best practices
We are currently in the beginning phases of migrating from Novell
e-Directory, to AD. We are having discussion
...@blueridgecarpet.com]
Sent: Wednesday, April 28, 2010 10:30 AM
To: NT System Admin Issues
Subject: RE: Current AD domain naming best practices
My understanding is the same as your Novell admin's: keep the two separate,
i.e. businessname.com for external and businessname.local for int
port Communities
-Original Message-
From: Joseph Heaton [mailto:jhea...@dfg.ca.gov]
Sent: Wednesday, April 28, 2010 10:22 AM
To: NT System Admin Issues
Subject: Current AD domain naming best practices
We are currently in the beginning phases of migrating from Novell e-Directory,
to AD
Tell your Novell guy you want to name it "workgroup" and see what he
does.
-Original Message-
From: Charlie Kaiser [mailto:charl...@golden-eagle.org]
Sent: Wednesday, April 28, 2010 9:28 AM
To: NT System Admin Issues
Subject: RE: Current AD domain naming best practices
Per
ssues
Subject: Current AD domain naming best practices
We are currently in the beginning phases of migrating from Novell
e-Directory, to AD. We are having discussions to decide on a new internal
domain name. I know that years ago, it was best practice to have a
different internal domain name from
Kaiser
charl...@golden-eagle.org
Kingman, AZ
***
> -Original Message-
> From: Joseph Heaton [mailto:jhea...@dfg.ca.gov]
> Sent: Wednesday, April 28, 2010 7:22 AM
> To: NT System Admin Issues
> Subject: Current AD domain naming best practices
>
>
We are currently in the beginning phases of migrating from Novell e-Directory,
to AD. We are having discussions to decide on a new internal domain name. I
know that years ago, it was best practice to have a different internal domain
name from your external domain name, which is what the Novell
22 matches
Mail list logo
