Open bnchrch opened 4 years ago
I think we have to write out externally hosted vs on our name servers.
The externally hosted version should just be CNAME to SUBDOMAIN.fission.name
(CNAME of root depends on the provider. Have to see what we can support with Route53)
The switch to our name servers is the same as purchasing a domain from us.
I would prioritize CNAME first. And probably make “use our name servers” as a separate issue as it is a sub flow of purchasing.
The new domains table that I suggested in the other issue applies here.
Wrote up some details over here (https://github.com/fission-suite/web-api/issues/255) before realizing that it was a repeat issue.
These are the steps for registering a domain (and also addresses the SSL concern above):
example.com
are properly configuredexample.com
example.com
using the DNS challenge optionexample.com
Route53 hosted zone for the DNS challengeexample.com
to the load balancer in front of the IPFS gatewayexample.com
to the list of user's domains in the DB
Dependant on: #218 and #219
Summary
We should allow users to use any domain of their choice
Problem / Impact
By not having this feature we are putting up a large blocker to having fission used in production.
Solution
We need to allow users to point their nameservers at our own then be able to link the domain to their account.
Detail
fission add domain test.xyz
If a user types
fission set domain test.xyz
add
will occur in addition to belowfission.yaml
fileUpdates to the API
GET /user/domain/{domain}
that will return the status of a domain. Is it's nameservers configured? does a user already own it? is it available to be assigned to the requesting user?POST /user/domain/{domain}
That will add the domain to the userDependant on
129 For allowing more than one domain per account
Unknowns
Impossibles
CNAME redirects
Netlify allows users to point subdomain and apex (depending on DNS provider) CNAME records to their pages directions. i.e. CNAME
*.benchurch.com
->{site}.netlify.com
.https://docs.netlify.com/domains-https/custom-domains/configure-external-dns/#configure-an-apex-domain
However due to how IPFS and IPNS lookups work I believe we wont be able to fill that case.
Sanity check here would be nice @fission-suite/core
Inspriation
https://docs.netlify.com/domains-https/custom-domains/
After Completion