# Custom Domain with ASP.Net Core Web Site

**URL:** <https://community.auth0.com/t/custom-domain-with-asp-net-core-web-site/21517>\
**Category:** Get Help\
**Created:** [February 19, 2019, 5:26pm UTC](https://community.auth0.com/t/custom-domain-with-asp-net-core-web-site/21517 "2019-02-19T17:26:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zenit](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/zenit/32/11198_2.png) [@Zenit](https://community.auth0.com/u/Zenit)\
**Post date:** [February 19, 2019, 5:26pm UTC](https://community.auth0.com/t/custom-domain-with-asp-net-core-web-site/21517/1 "2019-02-19T17:26:04Z")

</div>

Hi,

I’ve managed to run [ASP.Net](http://ASP.Net) Core web site with Auth0 authentication flawlessly.  
That required minimum configuration on Auth0 side and pretty simple coding in StartUp.cs (as appeared in documentation).

However, the addition of a custom domain doesn’t work - I still get “[zzzzzz.auth0.com](http://zzzzzz.auth0.com)” domain when Universal Login loads.

Should I adjust the configuration settings in StartUp.cs?  
What settings govern the transition to custom domain during login?

Regards

---

<div class="post-metadata">

**Author:** ![nicolas\_sabena](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nicolas_sabena/32/6064_2.png) [@nicolas\_sabena](https://community.auth0.com/u/nicolas_sabena)\
**Post date:** [February 19, 2019, 7:38pm UTC](https://community.auth0.com/t/custom-domain-with-asp-net-core-web-site/21517/2 "2019-02-19T19:38:31Z")

</div>

On the .Net side, and assuming your code picks up the configuration as in the quickstart, you should only need to change the `zzzzz.auth0.com` domain configuration value in the settings file (`appsettings.json`) to your custom domain ([https://github.com/auth0-samples/auth0-aspnetcore-mvc-samples/blob/master/Quickstart/01-Login/appsettings.json#L18](https://github.com/auth0-samples/auth0-aspnetcore-mvc-samples/blob/master/Quickstart/01-Login/appsettings.json#L18)).

On the Hosted Login Page, make sure you configure Lock as explained here: [Configure Features to Use Custom Domains](https://auth0.com/docs/custom-domains/additional-configuration#universal-login)

Check the HTTP trace from the browser’s developer tools. If the app redirects to `https://zzzzz.auth0.com/authorize` when requesting an authentication, then the application is not picking up the configuration change.

---

<div class="post-metadata">

**Author:** ![Zenit](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/zenit/32/11198_2.png) [@Zenit](https://community.auth0.com/u/Zenit)\
**Post date:** [February 20, 2019, 9:39am UTC](https://community.auth0.com/t/custom-domain-with-asp-net-core-web-site/21517/3 "2019-02-20T09:39:48Z")

</div>

Hi Nicolas,

It works perfect 🙂

Actually, I tried it in the first place, and the changes didn’t work…  
Probably, it takes some time to propagate the changes when it’s related to the custom domains

Thank you 👍

---

<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:** [March 7, 2019, 4:50pm UTC](https://community.auth0.com/t/custom-domain-with-asp-net-core-web-site/21517/5 "2019-03-07T16:50:58Z")

</div>

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