Azure Container App that is offline for to long makes the custom domain result in a connection reset error.

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

I've followed this blog post on how to assign a custom domain to an Azure Container App inside an Azure Container App Environment when deployed using Aspire: https://blog.mitchdenny.dev/custom-domains-with-aspire/.
Everything worked at first and I had the scaling rules configured to 0 and thus after a few minutes the containers went offline. After a few days I wanted to use my custom domain to browse to my container app again and now it's giving me a connection reset error.
Only if I use the URL that was generated by the container app, the custom domain is only assigned on the https port, I can actually boot up the app.
Even after the app as started again, the custom domain still doesn't work.

### Expected Behavior

If I browse to my custom domain I would want my container app to get provisioned and start the application.

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### .NET Version info

.NET SDK:
Version: 10.0.102
Commit: 4452502459
Workload version: 10.0.101.1
MSBuild version: 18.0.7+445250245

Runtime Environment:
OS Name: Windows
OS Version: 10.0.26200
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\10.0.102\

.NET workloads installed:
There are no installed workloads to display.
Configured to use workload sets when installing new manifests.

Host:
Version: 10.0.2
Architecture: x64
Commit: 4452502459

### Anything else?

Aspire version: 13.1.0+8a4db1775c3fbae1c602022b636299cb04971fde