# Problems registering custom domains

**URL:** https://forum.dfinity.org/t/problems-registering-custom-domains/41855
**Category:** Command Line Tools
**Created:** [March 4, 2025, 12:21pm UTC](https://forum.dfinity.org/t/problems-registering-custom-domains/41855 "2025-03-04T12:21:02Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![jed.blip](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jed.blip](https://forum.dfinity.org/u/jed.blip)
#### Post date: [March 4, 2025, 12:21pm UTC](https://forum.dfinity.org/t/problems-registering-custom-domains/41855/1 "2025-03-04T12:21:02Z")

</div>

I have all the correct DNS records and my file structure is setup as below:

- Project
- 
  - src

- 
  - 
    - .ic-assets.json (containing the content from the tutorial)

- 
  - 
    - .well-known

- 
  - 
    - 
      - ic-domains (containing the url)

I get the error: domain is missing from canister \_\_\_\_\_\_\_\_\_\_\_ list of known domains

even after deploying the canister again.

Thanks for the help!

---

<div class="post-metadata">

### Author: ![rbirkner](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@rbirkner](https://forum.dfinity.org/u/rbirkner)
#### Post date: [March 4, 2025, 12:53pm UTC](https://forum.dfinity.org/t/problems-registering-custom-domains/41855/2 "2025-03-04T12:53:18Z")

</div>

Hey @jed.blip

The error points to an issue with your `.well-known/ic-domains` file:

You can check the contents of your file by running the following command:

```auto
curl -s https://CANISTER_ID.icp0.io/.well-known/ic-domains

```

Just replace `CANISTER_ID` with your canister ID.

If you can’t figure it out, I am happy to help you more, but will need more information (the canister ID and the domain name). You can also share that with me in a DM.

---

<div class="post-metadata">

### Author: ![jed.blip](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jed.blip](https://forum.dfinity.org/u/jed.blip)
#### Post date: [March 4, 2025, 1:27pm UTC](https://forum.dfinity.org/t/problems-registering-custom-domains/41855/3 "2025-03-04T13:27:37Z")

</div>

Thanks! This helped, managed to successfully put in the registration and it now says available. However, the website gives this:

### This app is powered by

# 400 - unknown domain

The requested domain is not served by this HTTP gateway.

How long should it take for the website to start working?

---

<div class="post-metadata">

### Author: ![rbirkner](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@rbirkner](https://forum.dfinity.org/u/rbirkner)
#### Post date: [March 4, 2025, 1:37pm UTC](https://forum.dfinity.org/t/problems-registering-custom-domains/41855/4 "2025-03-04T13:37:06Z")

</div>

It should take a few minutes from the moment it says it is available to the point where all HTTP gateways are aware of the custom domain and have the certificate.

---

<div class="post-metadata">

### Author: ![jed.blip](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jed.blip](https://forum.dfinity.org/u/jed.blip)
#### Post date: [March 4, 2025, 1:43pm UTC](https://forum.dfinity.org/t/problems-registering-custom-domains/41855/5 "2025-03-04T13:43:18Z")

</div>

So it’s an issue that I’m still getting this error 15+ minutes later?

---

<div class="post-metadata">

### Author: ![rbirkner](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@rbirkner](https://forum.dfinity.org/u/rbirkner)
#### Post date: [March 4, 2025, 2:16pm UTC](https://forum.dfinity.org/t/problems-registering-custom-domains/41855/6 "2025-03-04T14:16:33Z")

</div>

It is really difficult to help without any information. If you share with me the canister ID and the domain name, I am happy to look into it.

---

<div class="post-metadata">

### Author: ![jed.blip](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jed.blip](https://forum.dfinity.org/u/jed.blip)
#### Post date: [March 4, 2025, 2:41pm UTC](https://forum.dfinity.org/t/problems-registering-custom-domains/41855/7 "2025-03-04T14:41:26Z")

</div>

Canister ID is xw7l2-viaaa-aaaal-qditq-cai and URL is front-row.app

---

<div class="post-metadata">

### Author: ![rbirkner](https://avatars.discourse-cdn.com/v4/letter/r/838e76/32.png) [@rbirkner](https://forum.dfinity.org/u/rbirkner)
#### Post date: [March 4, 2025, 3:35pm UTC](https://forum.dfinity.org/t/problems-registering-custom-domains/41855/8 "2025-03-04T15:35:06Z")

</div>

It seems to have worked on the boundary node side. With the following command, you can make the request directly against a boundary node:

```auto
curl -sLv -X GET \
    --resolve front-row.app:443:2a00:fb01:400:200:5000:5aff:fef2:9428 \
    https://front-row.app

```

I have checked this against all boundary nodes: The TLS session is always successfully established and I get a 200 back.

From your DNS config, I see that front-row.app is actually being proxied through AWS. I think the issue is somewhere there.
