"But still, the only way to make sure
that you can later create forest trusts (without renaming one of the forests)
with any other company/forest is to register your forest name (or use a
delegated one, such as corp.microsoft.com)."
...and that's (one of) my point. If we use a
non-standard TLD then we cannot register the name and may run into
issues.
Thanks for the
feedback.
neil
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sakari Kouti Sent: 21 July 2006 11:47 To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] Using non-standard TLDs within Active Directory Hi Neil and Peter,
If two companies both happen to choose corp.local for their
forest name, they cannot create forest trusts, if the need later arises. Of
course, if one of them is a chemical company in the west coast and the other is
a media company in the west coast, the risk is quite small.
But still, the only way to make sure that you can later
create forest trusts (without renaming one of the forests) with any other
company/forest is to register your forest name (or use a delegated one, such as
corp.microsoft.com).
Yours, Sakari From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Johnson Sent: 21. heinäkuuta 2006 12:30 To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] Using non-standard TLDs within Active Directory Hi
Neil Correct. The TLD is the
normally the last bit the in the string. So in the real world Internet examples
of TLDs are .com,.edu etc plus the country codes such as .za for
I always something like
corp.local for the forest name. I assuming you are going to be building a single
domain forest right? From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of
[EMAIL PROTECTED] Thanks
Peter. Are we referring to
same thing? I refer to the suffix
at the end of the DNS name - e.g. I refer to 'blob' in
'neil.blob'. I am not referring to
the 'neil' part. Does your response
still hold? neil From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Peter
Johnson Ive always gone the
opposite way. I like the idea of using a completely non-standard TLD for my
forest root so that if the company name changes etc it has no effect on the
forest. It also enables you to split the internal DNS from the external DNS
structure. If the internal DNS structure is ever published to the Internet it
will simply be dropped. I always set mine up
with non-standard TLDs and have never had any
issues. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of
[EMAIL PROTECTED] Does anyone have experience or
comments regarding the use of non-standard TLDs within a production AD
forest? E.g. xxxxx.nom The
name will be used within a production environment - a separate forest will exist
for testing and QA. I've always preferred to use
standard TLDs in prod [so the name can be registered etc] and permit the
non-standard TLD in test forests only. Any
comments? Thanks, PLEASE READ: The information
contained in this email is confidential and intended for the named recipient(s)
only. If you are not an intended recipient of this email please
notify the sender immediately and delete your
copy from your system. You must not
copy, distribute or take any further action in reliance on it. Email is
not a secure method of communication and Nomura International plc ('NIplc')
will not, to the extent permitted by law, accept responsibility or liability
for (a) the accuracy or completeness of, or (b) the presence of any virus,
worm or similar malicious or disabling code in, this message or any
attachment(s) to it. If verification of this email is sought then please request
a hard copy. Unless otherwise stated this email: (1) is not, and should
not be treated or relied upon as, investment research; (2) contains
views or opinions that are solely those of the author and do not necessarily
represent those of NIplc; (3) is intended for informational purposes only and
is not a recommendation, solicitation or offer to buy or sell securities or
related financial instruments. NIplc does not provide investment services
to private customers. Authorised and regulated by the Financial Services
Authority. Registered in no. 1550505 VAT No. 447 2492 35.
Registered Office: 1 PLEASE READ: The information
contained in this email is confidential and intended for the named recipient(s)
only. If you are not an intended recipient of this email please
notify the sender immediately and delete your
copy from your system. You must not
copy, distribute or take any further action in reliance on it. Email is
not a secure method of communication and Nomura International plc ('NIplc')
will not, to the extent permitted by law, accept responsibility or liability
for (a) the accuracy or completeness of, or (b) the presence of any virus,
worm or similar malicious or disabling code in, this message or any
attachment(s) to it. If verification of this email is sought then please request
a hard copy. Unless otherwise stated this email: (1) is not, and should
not be treated or relied upon as, investment research; (2) contains
views or opinions that are solely those of the author and do not necessarily
represent those of NIplc; (3) is intended for informational purposes only and
is not a recommendation, solicitation or offer to buy or sell securities or
related financial instruments. NIplc does not provide investment services
to private customers. Authorised and regulated by the Financial Services
Authority. Registered in no. 1550505 VAT No. 447 2492 35.
Registered Office: 1 PLEASE READ: The information contained in this email is confidential and
intended for the named recipient(s) only. If you are not an intended
recipient of this email please notify the sender immediately and delete your
copy from your system. You must not copy, distribute or take any further
action in reliance on it. Email is not a secure method of communication and
Nomura International plc ('NIplc') will not, to the extent permitted by law,
accept responsibility or liability for (a) the accuracy or completeness of,
or (b) the presence of any virus, worm or similar malicious or disabling
code in, this message or any attachment(s) to it. If verification of this
email is sought then please request a hard copy. Unless otherwise stated
this email: (1) is not, and should not be treated or relied upon as,
investment research; (2) contains views or opinions that are solely those of
the author and do not necessarily represent those of NIplc; (3) is intended
for informational purposes only and is not a recommendation, solicitation or
offer to buy or sell securities or related financial instruments. NIplc
does not provide investment services to private customers. Authorised and
regulated by the Financial Services Authority. Registered in England
no. 1550505 VAT No. 447 2492 35. Registered Office: 1 St Martin's-le-Grand,
London, EC1A 4NP. A member of the Nomura group of companies.
|
Title: Using non-standard TLDs within Active Directory
- RE: [ActiveDir] Using non-standard TLDs within Act... Peter Johnson
- RE: [ActiveDir] Using non-standard TLDs within Act... Almeida Pinto, Jorge de
- RE: [ActiveDir] Using non-standard TLDs withi... AFidel
- Re: [ActiveDir] Using non-standard TLDs w... Matheesha Weerasinghe
- RE: [ActiveDir] Using non-standard TLDs within Act... neil.ruston
- RE: [ActiveDir] Using non-standard TLDs within Act... Peter Johnson
- RE: [ActiveDir] Using non-standard TLDs within Act... Almeida Pinto, Jorge de
- RE: [ActiveDir] Using non-standard TLDs within Act... Peter Johnson
- RE: [ActiveDir] Using non-standard TLDs within Act... Peter Johnson
- RE: [ActiveDir] Using non-standard TLDs within Act... Almeida Pinto, Jorge de
- RE: [ActiveDir] Using non-standard TLDs within Act... neil.ruston
- RE: [ActiveDir] Using non-standard TLDs within Act... Peter Johnson
- RE: [ActiveDir] Using non-standard TLDs within Act... neil.ruston