Name your domain/server naming scheme.

Kyuki said:
http://serverfault.com/questions/40612/issues-with-using-real-domain-for-active-directory-domain could be one reason.
Click to expand...
Doesn't help any, but only further reinforces to me that you should use a real TLD. For example, if the website company.com is the website for your business, you should perhaps use corp.company.com or even company.net.

If you go with company.net, you can get the domain for real from some place like Namecheap if you want, but not necessary at all. You could use company.com for real website, and company.net (non-existent on Internet) for private/local/domain/internal-use only. If you did also buy the domain, you could mirror company.net to company.com so that in the real world they are identical and don't cause problems. On the inside, you could setup IIS to redirect users to company.com from company.net (or www.company.net from company.net, and have www point to company.com)

I did do some Googling and found that if you're going to use company.local as the domain name for ADDS, it will cause problems with Mac OSX (but then it's a question of "well, are we even planning to have Macs on the network? no. So we're good." <-- but I don't agree with this logic). I have also heard it is not good to use .local, as for the same reason problems will rise with Mac OSX, that some network services and software conflict with .local. It would be wiser to not use .local. However, about using non-existent TLDs other than .local, like .lan, .matrix, .bogosphere, I don't know. :X
 
aronesz said:
Why do you guys use .local and made-up TLDs that don't actually exist?
Click to expand...

.local isn't made up. It's an (unofficially) reserved TLD especially for local network use. I don't understand using a completely made up one either, though, since ICANN is about to allow the registration of arbitrary TLDs.

.local isn't technically a reserved name because it's not specified in an RFC. (The officially reserved TLDs are: .localhost .example .test and .invalid) However, ICANN would cause a huge shitstorm if they ever tried to make it a "real" TLD since it's used in mDNS.

aronesz said:
I have also heard it is not good to use .local, as for the same reason problems will rise with Mac OSX, that some network services and software conflict with .local. It would be wiser to not use .local.
Click to expand...

We've been using .local for a long time and have never had issues with it on our Macs. Please elaborate on these conflicts.
 
CEpeep said:
.local isn't made up. It's an (unofficially) reserved TLD especially for local network use. I don't understand using a completely made up one either, though, since ICANN is about to allow the registration of arbitrary TLDs.

.local isn't technically a reserved name because it's not specified in an RFC. (The officially reserved TLDs are: .localhost .example .test and .invalid) However, ICANN would cause a huge shitstorm if they ever tried to make it a "real" TLD since it's used in mDNS.



We've been using .local for a long time and have never had issues with it on our Macs. Please elaborate on these conflicts.
Click to expand...
Ok, thanks for your input! And thank you for being patient with my question :)
 
We have a 10 digit standard

first three digits is for a site identifier (using airport codes), followed by a one digit environment identifier (P-Production, D-Dev, Q-QA, etc.), then a one digit use identifier (G-General, F-Firewall, S-Switch, D-Database, etc), followed by a three digit server identifier (MBX, CAS, DPM, CFS, ESX), then a 2 digit number.

So a Dallas, TX ESX host in production would be

DALPGESX01 or a SAN would be DALPGSAN01 or a SAN switch would be DALPSSAN01.
 
You must log in or register to reply here.
Back
Top