domain.local - rebuild
We have 2 physical servers. One is many yrs old and needs replacing and the other is 3 yrs old and needs rebuilding; coz the guy that set it up messed up the RAID and some other settings.
Also, whoever installed the DC many moons ago decided to use, for the FQDN: a) the wrong name! [a short version of the school name which made it the name of another school in existence] b) .org at the end. Since then it's been left like that.
I am having thoughts about rebuilding it from scratch, during summer, to correct this. I was all set to use .local until a couple weeks ago, when an Apple reseller Tech advised me not to coz MAC's use .local (we have MACs) and it would just work easier if i didnt. So .. what other options are available?
I could just continue using .org but would rather not. A lot of our stuff is hosted externally at .org and it just works better if internal is not .org as well.
Generally; make it simple, not to long, not .local, and not something that'll need changing. For instance, ours is schoolname.sch.uk. Works fine, compatible, happily replicates to our LEA's DNS.
Have you not thought about schoolname.internal
I hadn't. Good idea :)
Originally Posted by nev104
I did some research on this very topic a month ago.
Our domain was setup by a predecessor a while ago as well and is very long.
Internal domain Schoolname.schoolname.k12.st.us
Public / website schoolname.k12.st.us
I considered shortening our internal to schoolname.lan but didnít based on other posts.
To sum it up, just because .lan, .local, and .internal are not real TLDís now doesnít mean they wonít be in the future.
I had a minor issue of accessing our website from within, but a couple DNS changes fixed that.
Unless you have a lot of problems with your current domain I would look into domain renaming. Otherwise youíll have to recreate all you users, rejoin your computers, and reset all your permissions.
You can demote, then rebuild one server at a time, or bring up a third.
Look into registering a sch.uk or use your schools .org fqdn.
Other suggestions I came across were
You don't have to recreate all your users, you can copy them, and their passwords Migrating User Accounts: Active Directory
There is nothing wrong with using a routable domain for your AD domain name, You just need to set your DNS up properly.
Originally Posted by detjo
Personally I use .internal for my private setup, I'm aware the arguments that its not a real TLD and could become one, But my network isn't large enough I care about and its one of the rarer ones that I doubt will ever get approved.