- Jul 2, 2006
Where i work our domain is call..theforce and we name our server after star war characters..
2 digit incremental number for the function
Minor nitpick: .loc is not reserved for local use, .local is.
With the current madness I wouldn't count on any TLD to not be in use in the future, so better use only those who are now explicitly reserved for private use.
.loc is shorter. If ever there actually is a TLD .loc then I'll probably change it, if I actually run into an issue.
By two characters...
You want to have some real fun? Do non-standard subnets.Random numbers and letters to make time at work interesting
So not only didn't you research before "planning" your network, you executed it so poorly that you'd have to change the domain in 200 places?!2 characters times 200 or so places I'd have to edit to change it.
So not only didn't you research before "planning" your network, you executed it so poorly that you'd have to change the domain in 200 places?!
You want to have some real fun? Do non-standard subnets.
I don't understand why people put the actual username as part of the hostname. Unless that person is a lifer eventually you'll have someone else sitting there.
/facepalmWell, whenever we do have a new person come in, we just rename the host in our network database, and then run our rename script on the client. The reason we do this is so we can keep track of which machines belong to which users.
hey, when one asks a dumb question, one should expect a dumb answer. besides, if someone doesn't know their hostname, at least we can easily look up their machine name using their userid...but sometimes they don't even know that *facepalm*