Oh god.
I'm a IT Manager, and I've had to deal with EXTREMELY POORLY named servers in this organization. Once you've got a server named, and have people pointing programs and queries to them by name, it's EXTREMELY difficult to change them (with a small staff and no time for troubleshooting).
Trust me on this, give them some kind of naming convention that's clean and that names the PRIMARY purpose of the server. If there are secondary purposes also, so be it.
If your company is named Arcade Restoration Group, and you have 2 offices in Podunk and Erie, do something like this:
ARGPODMAIL01 - ARG's 1st mail server in podunk
ARGPODMAIL02 - ARG's 2nd mail server in podunk
ARGPODFILE01 - ARG's 1st file server in podunk
ARGPODSQL01 - ARG's 1st sql server in podunk
ARGERIEMAIL01 - ARG's 1st mail server in erie.
ARGSQLMAIN - ARG's shared sql server
ARGDC01 - ARG's 1st domain controller
now if you decide to run DNS or whatever from any of these servers, so be it (just like you'll probably run antivirus on on of the mail servers, maybe not, depends on your setup). Don't get cute and name things like "pacman" and "galaga" or after roman gods, or after pokemon characters, or after your children (i have seen ALL of these in practice). At least give some indication about what they do, and make sure to have their uses and applications documented in your disaster recovery plan also.