RE: [ActiveDir] Using a non-standard TLD in your domain name?

[joe]

Yeah the namespace collision thought is the only thing that crossed my mind. But then I stood next to Roger drinking beer while he went on about that subject to some depth a few weeks back and when Roger tells you something when you are standing next to him... You listen. :o)

 

   joe

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Seielstad
Sent: Wednesday, May 12, 2004 9:24 AM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Using a non-standard TLD in your domain name?

I prefer to use registered, valid TLD's, but not publishing the DNS zones to the outside world. That's what we've done here, and its been very successful for the last 2-3 years. I would register a different domain than your corporate domain, however.

 

I've been through a number of corporate mergers and acquitisons, and knowing that you won't have a namespace collision is critical for those.

 

Roger

--------------------------------------------------------------
Roger D. Seielstad - MTS MCSE MS-MVP
Sr. Systems Administrator
Inovis Inc.

 

---

From: Celone, Mike [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 12, 2004 8:39 AM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Using a non-standard TLD in your domain name?

We are reviewing designs for our global AD environment and one suggestion what so use a non-standard TLD for our domain instead of the usual .com, org, net, etc.  One group is arguing that using a non-standard TLD is better for security.  Can someone expand on this.  When they were asked to they simply said they heard it from a consultant.  Are there any applications that will be expecting a normal TLD and may not work with a non-standard TLD?  What are the pros/cons of using a non-standard TLD?  

 

Mike Celone

Systems Specialist

Radio Frequency Systems

v 203-630-3311 x1031

f 203-634-2027

m 203-537-2406