Wednesday, March 03, 2010

Server Name Considerations - DNS and More (Mar. 2, 2010) (273750)

This editorial was posted on the SSWUG.org website in the editorial section on 2 March 2010. This is a great read on server naming conventions. I have copied the text below as this will become lost on the site.

Server Name Considerations - DNS and More

I hadn't planned on more naming items - but this is great feedback from a more "holistic" sense and I wanted to pass along this note from Johan.

"I know this is a pure Database Admins forum but when you start discussing server names, you are also referencing one of my other networking tasks. As I am working for a globally operating company with limited ICT staff, I am responsible for Databases, Active Directory, Server installations and Business Continuity Management. The server name standard I introduced uses ISO country code (Char 2), City Code (Char 3), Virtualization (‘V’ or not present), primary function (Char 3) and a number (Char 2). This results in NLEHVSQL03 for the third physical SQL server based in The Netherlands and the city of Eindhoven. This way the location of a server and its primary function is always known by its name.

The thing you are missing in your fine newsletter is the fact that your example server "GGSH389FKSJJS" can have a DNS Alias (technically called CNAME) that also describes another function. So your file server can have the Windows Active Directory and DNS name "GGSH389FKSJJS" and another DNS alias (CNAME) "FSBookKeeping" for the users.

This has multiple advantages:
  • When the server fails, you can bring a new one online called "JXZ596JVSUT", point the DNS alias "FSBookKeeping" to this server and no scripts, unc paths and documents have to be changed as the users use file://fsbookkeeping/fileshare
  • When your location has a Business Continuity crisis. Only DNS aliases have to be pointed to the servers in the backup server room. This also limits the scripting and configuration tasks during a crisis
  • Your server can have multiple functions to the user under different Aliases.
  • DNS entries can be updated with a script so they can be prepared for the case of an emergency. (see http://www.vansoest.it/v1/uk/default.asp?file=Hotlist.whc and click “Domain Name Server (DNS) Tips” for more information about the DNSCMD command line command)
There is a fileserver security option “DisableStrictNameChecking” that must be set before a fileserver (SMB) can be accessed by a DNS alias (CNAME). You can also find more information here: http://www.vansoest.it/v1/uk/default.asp?file=Hotlist.whc and click “Domain Name Server (DNS) Tips” I hope this gives your readers a lot more possibilities for efficiently naming their servers."

No comments: