Base solution for your next web application
Open Closed

Production deployment? {TENANCY_NAME}.MYDOMAIN.COM issues #3735


User avatar
0
mdonogma created

Purchased ssl wildcard cert per asp zero support. This is due to wanting to support multi-tenancy configured {TENANCY_NAME}.MYDOMAIN.COM in the JSON file SEE SCREENSHOT OF CURRENT DNS Settings. (A Record used) However it fails when navigating to the site after registration: <a class="postlink" href="https://mynewtenant.MYDOMAIN.COM">https://mynewtenant.MYDOMAIN.COM</a>

I logged a call with the hosting provider and they indicated a subdomain needs to be created for each tenant???????

from your documentation is says nothing about such requirement?

What are the exact DNS configs for production deployment of aspnet zero on 3rd party site. we are using <a class="postlink" href="http://www.smarterasp.net/">http://www.smarterasp.net/</a> for hosting


1 Answer(s)
  • User Avatar
    0
    alper created
    Support Team

    Hi

    There's a document about subdomains; <a class="postlink" href="https://aspnetzero.com/Documents/Development-Guide-Core#web-site-root-url">https://aspnetzero.com/Documents/Develo ... e-root-url</a>

    You should configure DNS to redirect all subdomains to a static IP address. To declare 'all subdomains', you can use a wildcard e.g. *.mydomain.com. You should configure IIS to bind this static IP to your application.