Name Your Domain

Daniel333

Anyone know of any good resources in naming your domain? Up until now I have kept it simple.

"sybex" was my last one and "kahn.local" before that. The guys at itdiots.com added "ad" to the front. What would be the logic on that?

e.g. ad.sanjose.local

Any other conventions I should know?

Essendon

They probably added "ad" in front to give them a subdomain. Just like, uk.yahoo.com, au.yahoo.com and the like. Mine is the ubiquitous contoso.com.

You can give it any name I guess, provided it's not been taken by someone already that's if you connect to the public internet.

astorrs

I always stick with <publicinternetdomain>.local for all my clients, so if their company domain name on the internet is ford.com their internal domain is ford.local. Keeps it simpler for everyone.

Essendon

Oops, seems my answer was a bit out of whack. Andrew's right.

Mishra

I like naming them with .ds. Makes it faster to type and easy to remember.

so

ford.ds

stands for directory services

sprkymrk

Mishra wrote:

I like naming them with .ds. Makes it faster to type and easy to remember.

so

ford.ds

stands for directory services

Same here.

dynamik

Just remember that Macs use .local for some of their services, and that might cause some problems until you adjust for that. You can change the settings on the Macs, but it might be better to just go with something else if you have a lot of them.

Personally, I make AD a child domain of our registered domain. ad.<domain name>.com

astorrs

dynamik wrote:

Just remember that Macs use .local for some of their services, and that might cause some problems until you adjust for that. You can change the settings on the Macs, but it might be better to just go with something else if you have a lot of them.

Personally, I make AD a child domain of our registered domain. ad.<domain name>.com

Don't get me started on stupid Apple adopting that one (they did it after .local was agreed to as a "quasi" approved TLD)...

Daniel333

Well, sounds like ad.mydomain.XXX is the standard. I should probably stick with that? Any other popular conventions I am likely to see?

Oh! And thanks for the Mac hint.

dynamik

Oh, I missed your, "What's the logic..?" question earlier.

You just don't want to use the same DNS namespace for both. You can use .com externally and .local (or whatever) internally, make your internal namespace start as a child of your registered name, etc. The main point to take away is that you want separate namespaces. Whatever convention you decide to go with is pretty much just personal preference.

sprkymrk

dynamik wrote:

Whatever convention you decide to go with is pretty much just personal preference.

Yeah, but my personal preference is always better than dynamik's. :P

liddane

So how would name resolution work in the case of using a subdomain of an internet registered domain name
I.e if my root ad domain was ad.microsoft.com, would I set up a conditional forwarder to the dns servers from the microsoft.com zone, for any queries ti www.microsoft.com?

Thanks

dynamik

sprkymrk wrote:

dynamik wrote:

Whatever convention you decide to go with is pretty much just personal preference.

Yeah, but my personal preference is always better than dynamik's. :P

That's why you're the moderator!

snadam

dynamik wrote:

sprkymrk wrote:

dynamik wrote:

Whatever convention you decide to go with is pretty much just personal preference.

Yeah, but my personal preference is always better than dynamik's. :P

That's why you're the moderator!

BTW, Moderator sir, care for some donuts?

TechJunky

I always use .corp for internal.

Slowhand

I usually use .local or .priv for internal domains. Although, Technomancer and I used "drunken.admin" for our test-domain when we were going to school together. The teacher wouldn't let us use our first choices, so that was our compromise. . .