title: Hostname Conventions (2025)
category: Server
time: 1752779493583
---
# Hostname PTR Record naming docs

> This is a updated version (2025) hostname conventions design
> Reason to update:
> - Try to limit the length of FQDN so it can be trimed when needed.
> - Try to ignore vendor when possible, so we consider all servers are one.
> - Try to include vendor to locations, when needed. 
> - Try to use a standard domain, for example `srv.DOMAIN.ltd` or simplify just `DOMAIN.ltd` for all hostname.

## Schema:

**[Name/Describes(#)/Purpose(#)]** | - **[model/env(Optional)]** | . **(DC)Location** *(#)* [+ . *(Vendor)*] | . ***DOMAIN***

## Detail:

**Name/Describes(#)/Purpose(#)**
- **NAME**: Can be a name of the device/host: Such as `Pluto` or `ZenEdge` etc.
- **Purpose**: Usage of the device/host etc.: Such as `vmcluster` or `crt01`  etc.
- OS if it's special OS that necessary to know.
- *Optional* number after Describes is optional for more than two same machine. Such as 2 DNS server or 2 NAS server.

**Kind/Purpose#**
- What kind of server/device is this?
- What purpose is this server/device for?
- This should be go with 'Describe' if possible or replace the 'model/dev' when needed.
- (2-3 letter for represent it, see list below)
- Common Kind:
  - 3 Letters:
    - Home
      - `nas`: NAS Server
      - `ups`: UPS Power
      - `vmm`: VM Manager
    - Cloud:
      - `web`: Web Server (Apache or Nginx)
      - `app`: Web/Mobile App Server
      - `api`: API Server
    - Home && Online
      - `sto`: Storage
      - Application Kind Server:
        - `ftp`: FTP Server (Including sFTP and/or rsync/sync)
        - `mal`: Mail Server
        - `git`: (Or `vcs`, `svn` etc.) Version Control
      - Purpose Kind Server:
        - `ssh`: SSH Jump Server etc.
        - `cfg`: Configuration Server (Ansible etc.)
        - `mon`: Monitoring Server
        - `prx`: Proxy Server (or `vpn` for VPN Server)
  - 2 Letters:
    - `db`: (Or `sql`) Database Server
    - `fw`: Firewall (Usually Hardware)
    - `rt`: Router (Usually Hardware)
    - `ns`: DNS Server
    - `sw`: Switch (Usually Hardware)
    - `gw`: Gateway (Usually Network Gateway outside your network)
    - `ap`: Access Point
    - `lb`: Load Balancer (Both Hardware and Software level LB)
  - 2 or 3 Letters for network equipment (Datacenter):
    - `et`: Ethernet Interface / `ae`: Aggregated Ethernet (Normally comes with port number on switch)
    - `ge`: Gigabit Ethernet / `xe`: 10-Gigabit Ethernet / `te`: 100-Gigabit Ethernet / `st`: Switching Interface
    - `hu`: High-Speed Uplink / `be`: Boardband Enternet / `st`: Switching Interface / `po`: Port Channel 
    - `ccr`: Core Control Router (maybe use `crt` Core Router) / `rcr`: Reginal Core Router (maybe use `rrt` Reginal Router) 
    - `cor`: Core (Router) /`bdr`: Boarder Route /  `pe`: Provider Edge (Router)

**model/env**
- **Optional** in naming schema.
- model:
  - device mode: router's model etc.
- env: Usage environment.
  - dev: Development
  - tst: Testing
  - stg: Staging
  - prd: Production

**Datacenter Location(#)**
- **IATA Airport** Code for the city the Datacenter located in.
- **ISO 3166 Country Code** (Alpha-2 & Alpha-3) Code for the country the Datacenter located in. (Optional)
- *Optional* number after location for Colocation Service or Self-build datacenter in the future.
- Common Location:
  - `yyz`: Toronto ON, Canada
  - `nyc`: New York City NY, USA
  - `lax`: Los Angeles CA, USA
  - `pdx`: Portland OR, USA

**Vendor**
- **ISP provider**
- Datacenter / Servers vendor
- Normally a 2 Letter represent each vendor. May also use number with Location for it.
- *Optional* for local subnet and local DNS hostname

**DOMAIN**
- Can be maximum third level domain
- Example:
  - `naedge.net`

**Example**
- `xe-0-0-0-1.ccr01.yyz01.naedge.net`: YYZ Location, Core Router #01, Port `xe-0/0/0/1`
- `zen.yyz.bl.naedge.net`: YYZ Location, Hostname 'Zen', `bl` provider (May stand for Bell)
- `zen-dev.yyz01.rg.naedge.net`: YYZ01 Location (Datacenter number may also represent ventor), 'Zen' host for `dev`
 
***Reference:***
- [Server Naming Conventions and Best Practices](https://blog.serverdensity.com/server-naming-conventions-and-best-practices/)
- [(Old) Hostname Conventions Wiki](https://wiki.zenuncl.com/page/server/hostname/)