Picking an Active Directory domain name

I

InorganicMatter

[H]F Junkie
Joined
Oct 19, 2004
Messages
15,461
I own the address cortiaus.net for my family website. For my current DC I have the domain name set up as cortiaus.net, but I have some problems resolving DNS, and I hear this is bad practice, so I'd like to move away from it.

I see some suggesting I use a subdomain: ad.cortiaus.net or home.cortiaus.net.
I also see some suggesting am unused suffix: cortiaus.local or cortiaus.lan.

Any reason to use one or the other?

I forgot to mention that I'd like to run Exchange and service @cortiaus.net email addresses, if that makes any difference.
 
Last edited:
I always do .local for internal domain names. A lot of the older admins I work with do the ad.domain.com because that was what MS recommended in the NT/2000 days.
Posted via [H] Mobile Device
 
Almost always use a .local or .lcl for the active directory name. This is best practice for internal domain names. You still use Exchange and IIS with this schema as well so dont worry about that.
 
Captain Colonoscopy said:
I always do .local for internal domain names. A lot of the older admins I work with do the ad.domain.com because that was what MS recommended in the NT/2000 days.
Posted via [H] Mobile Device
Click to expand...

Lazy_Moron said:
Almost always use a .local or .lcl for the active directory name. This is best practice for internal domain names. You still use Exchange and IIS with this schema as well so dont worry about that.
Click to expand...

We have lots of iPhones (and soon to be Macs), which have known problems with DNS systems that use the .local suffix. (Bonjour uses .local for auto-configuration of printers and routers.) So barring that name, I should still use an alternate suffix like lan, pvt, or lcl? I'm kinda liking the ring of cortiaus.lan.
 
.lcl should be fine. As long as it doesn't fall into the public domain space your fine. Alot of our clients have troubles because we started them out on .int domains.

I personally use .local domains for everything i setup, but i've had a buddy go as far and use .app for his hosted stuff.

Sky is kind of the limit really.
 
May I ask what problems are caused by using the h.int? I work for a local school district and we are currently migrating from Novell to Server 08 and so far the thing is on life support. I work as a technician and my Sys. Admin just started setting this Windows environment up about 3 weeks ago. He quit yesterday. So ummmm..yeah..I'm in a pickle to say the least. I am having a hell of a time getting teacher account policies to work and trying to get folder redirection to work right is an exercise in futility. Could it be related to him naming it using the .int? We have no one to replace him as of yet and I know the shit storm is about to fall in my lap. School starts this coming Friday and I have 4 schools to set up on windows. Its around 300 machines to physically set up by myself. My stress level is off the charts to say the least. I apologize if I'm thread jacking but when it read it, it hit me like a truck. Can you guys explain it to me please?
 
InorganicMatter said:
We have lots of iPhones (and soon to be Macs), which have known problems with DNS systems that use the .local suffix. (Bonjour uses .local for auto-configuration of printers and routers.) So barring that name, I should still use an alternate suffix like lan, pvt, or lcl? I'm kinda liking the ring of cortiaus.lan.
Click to expand...

Maybe Apple shouldn't be silly and use a well-known internal domain name suffix for that junk? People have been using .local for years . . .
 
InorganicMatter said:
We have lots of iPhones (and soon to be Macs), which have known problems with DNS systems that use the .local suffix. (Bonjour uses .local for auto-configuration of printers and routers.) So barring that name, I should still use an alternate suffix like lan, pvt, or lcl? I'm kinda liking the ring of cortiaus.lan.
Click to expand...

For this exact reason we started using .lan
 
You must log in or register to reply here.
Back
Top