# Custom Domain documentation improvements

**URL:** <https://community.auth0.com/t/custom-domain-documentation-improvements/45191>\
**Category:** Get Help\
**Tags:** documentation\
**Created:** [June 24, 2020, 7:34am UTC](https://community.auth0.com/t/custom-domain-documentation-improvements/45191 "2020-06-24T07:34:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Civility](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/civility/32/20751_2.png) [@Civility](https://community.auth0.com/u/Civility)\
**Post date:** [June 24, 2020, 7:34am UTC](https://community.auth0.com/t/custom-domain-documentation-improvements/45191/1 "2020-06-24T07:34:26Z")

</div>

We’re trying to use [Custom Domain](https://auth0.com/docs/custom-domains) to prevent Safari ITP issues.

The documentation has a typo (extra “to”),

> you can have your users to see, use, and remain on **[login.northwind.com](http://login.northwind.com)**

but more confusingly, it doesn’t seem to “flow” logically - the landing doc page for Custom Domains doesn’t explain _how to set one up_. It goes from “We recommend that you use custom domains with Universal Login for the most seamless and secure experience for your users. See [Universal Login](https://auth0.com/docs/universal-login) to determine if your use case requires custom domains.” straight to technical details - **Token issuance**.

Before _Token issuuance_, it seems a more logical section would be “How to set up custom domains”. From what I see farther ahead in the docs, there are two options for this, depending on how the certificates are obtained? That would be good info to put in that _Howto set up_ section.

Another issue:

We have our custom domain `auth.civility.social` showing a status of Ready under Tenant Settings → Custom Domains, and want to use it [for the Universal login](https://auth0.com/docs/custom-domains/additional-configuration#universal-login) interstitial. That page reads,

> If you use the **default** login page without customization, you do not need to make any changes.

We do use the default, uncustomized New Universal Login experience, but Auth0 still serves it from `https://civility-app.auth0.com`. The Universal Login page of the Dashboard reads,

> The universal login page will be served by default at **[civility-app.auth0.com/login](http://civility-app.auth0.com/login)**. You can use your own domain by configuring it in [Custom Domains](https://manage.auth0.com/dashboard/us/civility-app/tenant/custom_domains).

 ![image](https://global.discourse-cdn.com/auth0/original/3X/b/7/b766bdc394e040bd4fef5d8cced2d168aaf469f3.png)

The custom domain is already configured in Custom Domains.

 ![image](https://global.discourse-cdn.com/auth0/original/3X/a/d/adbeaa735ecd39e12880c570824a2de52e2460af.png)

Turned out that which domain Auth0 served the Universal Login page on was determined by the `.login()` from `Auth0.js`, so its `AUTH0_DOMAIN` setting needed to be changed. Maybe worth a mention about that somewhere?

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [June 26, 2020, 5:53pm UTC](https://community.auth0.com/t/custom-domain-documentation-improvements/45191/3 "2020-06-26T17:53:03Z")

</div>

Thanks for the feedback! We really appreciate this kind of constructive info. I passed this info along to our docs team.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [July 11, 2020, 6:00pm UTC](https://community.auth0.com/t/custom-domain-documentation-improvements/45191/4 "2020-07-11T18:00:03Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.