Also a good idea.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: 21 July 2006 14:05
To: [email protected]
Subject: RE: [ActiveDir] Using non-standard TLDs within Active Directory

 


For this and other reason I like to use the .ad or .ads TLD for my active directory.

Andrew Fidel

"Almeida Pinto, Jorge de" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]

07/21/2006 06:43 AM

Please respond to
[email protected]

To

<[email protected]>

cc

 

Subject

RE: [ActiveDir] Using non-standard TLDs within Active Directory

 

 

 




for the LOCAL tld, you need be aware that it can cause issues with MAC computers
 
http://support.microsoft.com/kb/836413/en-us
http://docs.info.apple.com/article.html?artnum=107800
Jorge


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent:
Friday, July 21, 2006 12:34
To:
[email protected]
Subject:
RE: [ActiveDir] Using non-standard TLDs within Active Directory


Thanks again. We're on the same wave length :)
 
I appreciate that .local can work but as you state, it's best to avoid names that can become obsolete if the company name changes.
 
The proposal here is to use .nom and the company name is Nomura.
 
...and no, it will not be a single domain forest, but let's not go there please :) I've already spent months on that subject :/
 
Thanks for the comments and feedback.
neil


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Johnson
Sent:
21 July 2006 10:30
To:
[email protected]
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 TLD’s are .com,.edu etc plus the country codes such as .za for South Africa which is where I from.
 
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]
Sent:
21 July 2006 11:19
To:
[email protected]
Subject:
RE: [ActiveDir] Using non-standard TLDs within Active Directory

 
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
Sent:
21 July 2006 09:56
To:
[email protected]
Subject:
RE: [ActiveDir] Using non-standard TLDs within Active Directory

I’ve 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 TLD’s and have never had any issues.
 

 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent:
21 July 2006 10:20
To:
[email protected]
Subject:
[ActiveDir] Using non-standard TLDs within Active Directory

 

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,
neil

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.
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.

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.

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

Reply via email to