# Hostname PTR Record naming docs
# Schema:
Describes(#) | - (model/env) | . Kind/Purpose # | . (DC)Location (#) | . (Vendor) | . DOMAIN
# Detail:
Describes(#)
- Can be a name of the device/host: Such as Plato, ShaEdge etc.
- Usage of the device/host etc.: Such as vmcluster 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.
model/env
- Optional in naming schema.
- model:
- device mode: router’s model etc.
- env: Usage environment.
- dev: Development
- tst: Testing
- stg: Staging
- prd: Production
Kind/Purpose#
- What kind of server/device is this?
- What purpose is this server/device for?
- (2-3 letter for represent it, see list below)
- Common Kind:
- 3 Letters:
- Home
nas: NAS Serverups: UPS Powervmm: VM Manager
- Cloud:
web: Web Server (Apache or Nginx)app: Web/Mobile App Serverapi: API Server
- Home && Online
sto: Storage- Application Kind Server:
ftp: FTP Server (Including sFTP and/or rsync/sync)mal: Mail Servergit: (Orvcs,svnetc.) Version Control
- Purpose Kind Server:
ssh: SSH Jump Server etc.cfg: Configuration Server (Ansible etc.)mon: Monitoring Serverprx: Proxy Server (orvpnfor VPN Server)
- Home
- 2 Letters:
db: (Orsql) Database Serverfw: Firewall (Usually Hardware)rt: Router (Usually Hardware)ns: DNS Serversw: Switch (Usually Hardware)gw: Gateway (Usually Network Gateway outside your network)ap: Access Pointlb: Load Balancer (Both Hardware and Software level LB)
- 3 Letters:
Datacenter Location(#)
- IATA Airport Code for the city the Datacenter located in.
- Optional number after location for Colocation Service or Self-build datacenter in the future.
Vendor
- ISP provider
- Datacenter Vendor
- Optional for local subnet and local DNS hostname
DOMAIN
- Can be maximum third level domain
- Example:
naedge.net
Reference:
Last Update: 2024-11-10 22:31:14 Source File