Community Domain and Mailbox Setup

Community Domain Setup

Depending on the owner and host of the community domain name, there are five options for setting up the community domain, each requiring varying levels of effort from Fuel Cycle and the client.

Option 1

Fuel Cycle owns the domain and manages DNS and SSL

This option has Fuel Cycle handling everything, the client only needs to approve the domain name:

• Fuel Cycle purchases domains and manages all DNS.
• Fuel Cycle purchases and manages SSL certificates.
• On contract expiration, if the client decides to keep the domain Fuel Cycle can transfer the domain to the client.

Option 2

Client owns the domain, Fuel Cycle manages DNS and SSL

This option requires the client to purchase the domain and update the DNS, in collaboration with the Fuel Cycle DevOps team:

• The client purchases the domain.
• Fuel Cycle creates a hosted zone and provides name server records to the client.
• The client updates DNS records on their side.
• Fuel Cycle manages all other DNS records.
• Fuel Cycle purchases and manages SSL certificates.

Option 3

Client owns the domain and manages SSL, Fuel Cycle manages DNS

This option requires the client to purchase the domain and update the DNS, in collaboration with the Fuel Cycle DevOps team:

• The client purchases the domain.
• Fuel Cycle creates a hosted zone and provides name server records to the client.
• The client updates DNS records on their side.
• Fuel Cycle manages all other DNS records.
• The client purchases an SSL certificate and provides it to Fuel Cycle.
• Fuel Cycle installs certificate.

Option 4

Client owns the domain and manages DNS, Fuel Cycle manages SSL

This option requires full involvement on the client’s side in collaboration with the Fuel Cycle DevOps team:

• The client purchases the domain.
• Fuel Cycle provides all DNS records to the client.
• Fuel Cycle Purchases an SSL certificate and provides DNS to the client.
• The client uploads all DNS records on their side.
• Fuel Cycle manages SSL certificates.
• Fuel Cycle uses Amazon Web Services load balancers and cannot provide an IP address for an A record. The client will need to use a subdomain (e.g., www.) with a CNAME record or a CDN/DNS provider that supports zone apex mapping.

Option 5

Client owns the domain and manages DNS and SSL

This option requires full involvement on the client’s side in collaboration with the Fuel Cycle DevOps team:

• The client purchases the domain.
• Fuel Cycle provides all DNS records to the client.
• The client uploads all DNS records on their side.
• The client purchases an SSL certificate and gives it to Fuel Cycle.
• Fuel Cycle installs certificate.
• Fuel Cycle uses Amazon Web Services load balancers and cannot provide an IP address for an A record. The client will need to use a subdomain (e.g., www.) with a CNAME record or a CDN/DNS provider that supports zone apex mapping.

Community Mailbox Setup

There are two options for setting up the community mailbox, each requiring different levels of effort from Fuel Cycle and the client.

Fuel Cycle utilizes Google GSuite to create and manage Client mailboxes.

Option 1

Fuel Cycle owns and manages the mailbox

In this option, Fuel Cycle handles everything. The client can be given access to the mailbox:

• Fuel Cycle creates a mailbox in GSuite and manages all DNS.
• Fuel Cycle can provide mailbox login credentials to the client.

Option 2

Client owns and manages mailbox

This option requires the client to create and manage the mailbox. If Fuel Cycle is managing DNS, the client will need to provide records:

• The client creates a mailbox and manages the mailbox.
• Allowing Fuel Cycle to access the mailbox is optional.