Standard DNS naming #270

New issue

Closed

opened 2025-08-22 00:50:07 +00:00 by raito · 3 comments

raito commented

2025-08-22 00:50:07 +00:00

(Migrated from git.lix.systems)

Our DNS naming is a bit all over the place and this hurts the operators ability to remember what thing is what and all the conventions.

Let's come up with some informal guidance or pseudo standard naming and find a way to (a) teach people who works on infra how to follow it (b) help people to set the right values from the get go using abstractions in places where this is cheap perhaps.

cc @delroth

Our DNS naming is a bit all over the place and this hurts the operators ability to remember what thing is what and all the conventions. Let's come up with some informal guidance or pseudo standard naming and find a way to (a) teach people who works on infra how to follow it (b) help people to set the right values from the get go using abstractions in places where this is cheap perhaps. cc @delroth

raito commented

2025-08-22 00:51:16 +00:00

(Migrated from git.lix.systems)

@delroth says

in general I'd standardize on machine-name.az.infra.afnix.fr for baremetal machines, something similar for VMs (maybe .v. between machine name and infra), and then stuff directly under .infra.afnix.fr is just CNAMEs for services
(and user-facing is CNAMEs directly under .afnix.fr)

@delroth says > in general I'd standardize on machine-name.az.infra.afnix.fr for baremetal machines, something similar for VMs (maybe .v. between machine name and infra), and then stuff directly under .infra.afnix.fr is just CNAMEs for services > (and user-facing is CNAMEs directly under .afnix.fr)

raito commented

2025-08-24 00:43:53 +00:00

(Migrated from git.lix.systems)