I have a Server 2016 stand along server (not VPS and not part of a domain)
When I set up a Linux web server I usually name the web server using a FQDN, is this the best practice for a Windows server?
Currently the server is just named some generic name, probably what windows installation gave it during install.
Just wondering if there was a best practice for naming a Windows Server and I assume we do that through Computer —> properties —> Advanced System Settings —–> Computer Name
Well server naming is highly personal (and we seen many combinations).
fqdn you normally only do with Active Directory joined servers, not so much workgroup servers.
In most cases Location-type-number is a common way to name servers but thats our own favorite (for example NL001-msSQL-01 )
For database servers i would always assign a fqdn for the users to use such as mysql01.mydomain.com which you can set in both dns aswell as hostname file. (mainly so in the future you can easily migrate database servers if ever needed without the customers having to change any settings).
- Views369 times
- Answers1 answer