Internal Domain Name

[kj4ezj]

Background

Currently, all EOS Network Foundation (ENF) infrastructure exists at eosnetwork.com or one of its sub-domains. This is ideal for (external) customer-facing services such as learn.eosnetwork.com.

Problem

Using the primary, customer-facing web real estate at eosnetwork.com for internal services, developer work, and engineering testing creates unnecessary risk to our outward-facing properties and currently involves friction. While we have plans to eliminate the friction, the risk will remain.

There are a number of other domains marketing has picked up to protect our brand and they are more than happy to let engineers use some of them, but they have asked that their department approve changes made to these domains in advance. This is a perfectly reasonable request. Automation is grateful to work with Marketing and we are certain requests will be approved quickly. However, this is still friction.

Solution

Automation is requesting permission to purchase one or two domain names to be used exclusively for inward-facing services, developer work, and engineers. These domains would be frictionless in the sense that Automation and Engineering would have ownership over them, be able to provision resources for internal projects without risk to external customer-facing resources, and provision resources without approval from other departments. Automation has a shortlist of domain names we have confirmed are available to use for this purpose but we have intentionally excluded them from this ticket to protect their availability. The list is available via IM or email upon request.

The cost of these domains would be $20-$40 per year per domain name.

[kj4ezj]

Yesterday, @wanderingbort gave me the authorization to move forward with purchasing one domain name.

[kj4ezj]

We purchased enf.land for these purposes.