<![CDATA[Topics tagged with dns]]>https://fusionauth.io/community/forum/tags/dnsRSS for NodeMon, 17 Aug 2026 05:08:52 GMTInvalid Date60<![CDATA[Want to run FusionAuth and the backend app in Docker]]>You can create two values for the FusionAuth url:

internalFusionAuthURL="http://fusionauth:9011" externalFusionAuthURL="http://localhost:9011"

So basically whenever you are sending the redirect to the browser (pretty much just the authorize and logout URLs) you use externalFusionAuthURL which references localhost.

When you are communicating with FusionAuth from the application backend (the express app) you use the internalFusionAuthURL which references the docker domain name.

I tested that out and it seems to work fine.

Give that a try.

]]>https://fusionauth.io/community/forum/topic/3020/want-to-run-fusionauth-and-the-backend-app-in-dockerhttps://fusionauth.io/community/forum/topic/3020/want-to-run-fusionauth-and-the-backend-app-in-dockerInvalid Date<![CDATA[We use FusionAuth cloud and want our instance to have a custom domain name]]>As of July 25, 2023 we now support Unlimited Custom Domains for FusionAuth Cloud! You can read more in this post, on how to add a custom domain.

]]>https://fusionauth.io/community/forum/topic/239/we-use-fusionauth-cloud-and-want-our-instance-to-have-a-custom-domain-namehttps://fusionauth.io/community/forum/topic/239/we-use-fusionauth-cloud-and-want-our-instance-to-have-a-custom-domain-nameInvalid Date