# Can deleting a discontinued classic app mess up the new app's custom domain?

**URL:** <https://community.glideapps.com/t/can-deleting-a-discontinued-classic-app-mess-up-the-new-apps-custom-domain/83556>\
**Category:** Ask for Help\
**Created:** [July 30, 2025, 2:02pm UTC](https://community.glideapps.com/t/can-deleting-a-discontinued-classic-app-mess-up-the-new-apps-custom-domain/83556 "2025-07-30T14:02:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luiz\_Roberto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/luiz_roberto/32/80972_2.png) [@Luiz\_Roberto](https://community.glideapps.com/u/Luiz_Roberto)\
**Post date:** [July 30, 2025, 2:02pm UTC](https://community.glideapps.com/t/can-deleting-a-discontinued-classic-app-mess-up-the-new-apps-custom-domain/83556/1 "2025-07-30T14:02:55Z")

</div>

I’m having trouble accessing an app I’ve migrated to the new model. Up until now, everything was working fine, but a few days ago, I deleted the classic app, which was down, and the custom domain stopped working. I also saw on [https://status.glideapps.com/](https://status.glideapps.com/) that there were issues with the custom domain a few days ago. I don’t know if that could be related to my issue.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [July 30, 2025, 2:19pm UTC](https://community.glideapps.com/t/can-deleting-a-discontinued-classic-app-mess-up-the-new-apps-custom-domain/83556/2 "2025-07-30T14:19:21Z")

</div>

Yes, there were indeed issues with custom domain around 2 weeks ago. Here’s the official suggested workaround.

> [@All custom domains fail to resolve](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/53):
>
> Yesterday, we asked you to update your DNS A Name records to a specific IP address due to an unexpected issue with two of our hosting IPs. Earlier today, the third IP address also became unavailable. Our provider has now given us two new, stable IP addresses that are safe to use going forward: 162.159.142.16 172.66.2.12 (Please replace your existing A Name records with this new IP.) NOTES: It takes a little while for the DNS changes to be applied, so be patient. The IP addresses in the Cu…