One time steps to use the custom domain devinci.onicai.com
:
-
Define the DNS records as described in step 1 of IC Custom Domain Docs
You can verify everything is propagating with "dig":
% dig CNAME devinci.onicai.com ;; ANSWER SECTION: devinci.onicai.com. 3600 IN CNAME icp1.io. % dig CNAME _acme-challenge.devinci.onicai.com ;; ANSWER SECTION: _acme-challenge.devinci.onicai.com. 3600 IN CNAME _acme-challenge.devinci.onicai.com.icp2.io. % dig TXT _canister-id.devinci.onicai.com ;; ANSWER SECTION: _canister-id.devinci.onicai.com. 3600 IN TXT "x6occ-biaaa-aaaai-acqzq-cai"
-
Created this file:
src/DeVinci_frontend/assets/.well-known/ic-domains
:
devinci.onicai.com
-
After build, verify that files are included in
dist/.well-known
-
Deploy the canister
-
Initiate the registration of domain with IC this command & check that the output looks similar as:
$ curl -sLv -X POST \
-H 'Content-Type: application/json' \
https://ic0.app/registrations \
--data @- <<EOF
{
"name": "devinci.onicai.com"
}
EOF
...
* Connection #0 to host ic0.app left intact
{"id":"xxx..."}
e.g. {"id":"50c9888f77c132534498d0f6ffd19b4269a2373eb55a90c705e2b2c3471bada9"}
- Query the status, using the REQUEST_ID: (You might need to repeat this several times before everything is 'approved')
$ curl -sLv -X GET \
https://ic0.app/registrations/xxx
...
e.g. curl -sLv -X GET https://ic0.app/registrations/50c9888f77c132534498d0f6ffd19b4269a2373eb55a90c705e2b2c3471bada9
# once approved
* Connection #0 to host ic0.app left intact
{"name":"devinci.onicai.com","canister":"x6occ-biaaa-aaaai-acqzq-cai","state":"Available"}