# All custom domains fail to resolve

**URL:** <https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223>\
**Category:** Ask for Help\
**Created:** [July 16, 2025, 6:55pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223 "2025-07-16T18:55:02Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Marcel\_at\_Glide](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/marcel_at_glide/32/60371_2.png) [@Marcel\_at\_Glide](https://community.glideapps.com/u/Marcel_at_Glide)\
**Post date:** [July 17, 2025, 4:48pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/22 "2025-07-17T16:48:58Z")

</div>

I don’t know what the issue was last week for your domain, but this issue was not related. If you DM me some details, I’ll see what I can figure out about last week’s issue.

---

<div class="post-metadata">

**Author:** ![Hbrezy](https://avatars.discourse-cdn.com/v4/letter/h/ea666f/32.png) [@Hbrezy](https://community.glideapps.com/u/Hbrezy)\
**Post date:** [July 17, 2025, 4:50pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/23 "2025-07-17T16:50:59Z")

</div>

Exact issue lasted 3-4 hours

> [@Glide is down. Again](https://community.glideapps.com/t/glide-is-down-again/83096):
>
> Is anyone app down too and not loading? Its loading fine via the glide.page but domain is down.

---

<div class="post-metadata">

**Author:** ![Hbrezy](https://avatars.discourse-cdn.com/v4/letter/h/ea666f/32.png) [@Hbrezy](https://community.glideapps.com/u/Hbrezy)\
**Post date:** [July 17, 2025, 4:53pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/24 "2025-07-17T16:53:15Z")

</div>

You are right hence why its called a web. I guess as a tech a entrepreneur, this is what comes with the game.

---

<div class="post-metadata">

**Author:** ![MegannLock](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/megannlock/32/19680_2.png) [@MegannLock](https://community.glideapps.com/u/MegannLock)\
**Post date:** [July 17, 2025, 5:54pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/25 "2025-07-17T17:54:11Z")

</div>

@Marcel_at_Glide Things are resolving & my URLs are working now after that DNS record update. Thank you!

---

<div class="post-metadata">

**Author:** ![Miguel\_Coelho](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/miguel_coelho/32/17150_2.png) [@Miguel\_Coelho](https://community.glideapps.com/u/Miguel_Coelho)\
**Post date:** [July 17, 2025, 6:21pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/26 "2025-07-17T18:21:23Z")

</div>

Thank you so much for the update — it worked perfectly! 🙌 Everything is now correctly pointing to the new IP. Really appreciate you finally sharing this info here, as Glide hadn’t addressed the issue anywhere else until now. Glad to see it resolved!

---

<div class="post-metadata">

**Author:** ![jiwook\_hwa](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jiwook_hwa/32/48787_2.png) [@jiwook\_hwa](https://community.glideapps.com/u/jiwook_hwa)\
**Post date:** [July 18, 2025, 12:56am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/27 "2025-07-18T00:56:48Z")

</div>

The issue has been resolved. 🙂 Thank you so much for all your hard work! I truly appreciate your prompt resolution and feedback once again. 🙂

---

<div class="post-metadata">

**Author:** ![jgentile](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jgentile/32/40909_2.png) [@jgentile](https://community.glideapps.com/u/jgentile)\
**Post date:** [July 18, 2025, 3:04am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/28 "2025-07-18T03:04:34Z")

</div>

If anyone is experiencing a domain name outage - I was.. and I just found the answer here. Scroll down and look at the update (tempoprary??) IP address they suggest using\>

> [@All Apps domains have failed. Again](https://community.glideapps.com/t/all-apps-domains-have-failed-again/83223):
>
> Is anyone else experiencing an outage when accessing their app through the domain? This is the second time it’s happened to me this week. Are the Glide dev team currently working on updates or maintenance? What may be causing this outage?

(SOLVED POST BELOW)

Can anyone see if [assemblycare.org](http://assemblycare.org) is pointing to our glide site. (assemblycare.glide.page is the default provided).

This was working for months. Our domain provider tech support said there was a domain name forwarder that was preventing the site from loading. Site aside whether that was a foolish staff worker or a security breach. 7 hours ago that forwarder was removed. But the site is still not loading properly. Glide domainname wizard gives us two green checks indicating that things look good from glide in terms of what two DNS records should be present. Still the site isn’t loading on multiple devices all afternoon?

Any smart people out there who can try to detect what is going wrong with domain [assemblycare.org](http://assemblycare.org) and why its not pointing to our glide site? **Not sure if someone out there has some tools that can let them see DNS/domain problems from the outside.**

---

<div class="post-metadata">

**Author:** ![dezwatz](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dezwatz/32/77903_2.png) [@dezwatz](https://community.glideapps.com/u/dezwatz)\
**Post date:** [July 18, 2025, 6:32pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/29 "2025-07-18T18:32:12Z")

</div>

> [@Marcel\_at\_Glide](#):
>
> 172.67.20.230

I’ve been using this for my A record and now its down.

---

<div class="post-metadata">

**Author:** ![Hbrezy](https://avatars.discourse-cdn.com/v4/letter/h/ea666f/32.png) [@Hbrezy](https://community.glideapps.com/u/Hbrezy)\
**Post date:** [July 18, 2025, 6:43pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/30 "2025-07-18T18:43:50Z")

</div>

Yes it looks like we are offline again.

---

<div class="post-metadata">

**Author:** ![Marcel\_at\_Glide](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/marcel_at_glide/32/60371_2.png) [@Marcel\_at\_Glide](https://community.glideapps.com/u/Marcel_at_Glide)\
**Post date:** [July 18, 2025, 6:44pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/31 "2025-07-18T18:44:01Z")

</div>

Heads up. Users are starting to report that 172.67.20.230 isn’t working We’re looking into this and checking with our service provider. My current thought is they’re trying to resolve the original issue, which is causing some disruption to the 172.67.20.230 address.

Follow the status here: [Minor incident: Some custom domains not resolving | Glide Status](https://status.glideapps.com/incidents/303217)

---

<div class="post-metadata">

**Author:** ![Brian\_Banks](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/brian_banks/32/80720_2.png) [@Brian\_Banks](https://community.glideapps.com/u/Brian_Banks)\
**Post date:** [July 18, 2025, 1:55pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/32 "2025-07-18T13:55:47Z")

</div>

My app remains having Domain issues. I have updated A records in my DNS setting and received the green checks on validation. However the issue remains.

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [July 18, 2025, 2:25pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/33 "2025-07-18T14:25:44Z")

</div>

Are you using the new IP?

[https://community.glideapps.com/t/not-working-with-cloudflare-custom-domains-while-glide-is-suggesting-we-use-cloudflare-paid-maker-plan/83279/2?u=jeff\_hager](https://community.glideapps.com/t/not-working-with-cloudflare-custom-domains-while-glide-is-suggesting-we-use-cloudflare-paid-maker-plan/83279/2)

---

<div class="post-metadata">

**Author:** ![Brian\_Banks](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/brian_banks/32/80720_2.png) [@Brian\_Banks](https://community.glideapps.com/u/Brian_Banks)\
**Post date:** [July 18, 2025, 4:19pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/35 "2025-07-18T16:19:34Z")

</div>

Ok, no I was using the address suggested in the custom domain process. Once I change it, I am assuming the Glide verification process will not give the double green check, yet still work?

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [July 18, 2025, 6:48pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/36 "2025-07-18T18:48:45Z")

</div>

> [@All custom domains fail to resolve](https://community.glideapps.com/t/all-apps-domains-have-failed-again/83223/31):
>
> Heads up. Users are starting to report that 172.67.20.230 isn’t working We’re looking into this and checking with our service provider. My current thought is they’re trying to resolve the original issue, which is causing some disruption to the 172.67.20.230 address. Follow the status here: [Minor incident: Some custom domains not resolving | Glide Status](https://status.glideapps.com/incidents/303217)

---

<div class="post-metadata">

**Author:** ![steveforwan](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@steveforwan](https://community.glideapps.com/u/steveforwan)\
**Post date:** [July 18, 2025, 10:53am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/37 "2025-07-18T10:53:06Z")

</div>

Please help! My users are getting lost! showing everything “Could not load network resources”

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [July 18, 2025, 11:41am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/38 "2025-07-18T11:41:43Z")

</div>

> [@All custom domains fail to resolve](https://community.glideapps.com/t/all-apps-domains-have-failed-again/83223/19):
>
> To resolve the issue, we now have another IP address you can point your A record to. Sign in to your DNS provider’s site and update the A record for your domain to point at 172.67.20.230. Our service that manages custom domains will take a little while to see the change, but it’ll eventually resolve. You do not need to make changes to your custom domain configuration in the Builder environment, and this is a permanent change. You won’t need to go back and update later. Please be patient waitin…

---

<div class="post-metadata">

**Author:** ![steveforwan](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@steveforwan](https://community.glideapps.com/u/steveforwan)\
**Post date:** [July 18, 2025, 11:49am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/39 "2025-07-18T11:49:03Z")

</div>

> [@All Apps domains have failed. Again](#):
>
> 172.67.20.230

i have two glide sites that is using the same service provider with same account, does it matter if i have two glide sites sharing same IP address for CloudFlare?

---

<div class="post-metadata">

**Author:** ![steveforwan](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@steveforwan](https://community.glideapps.com/u/steveforwan)\
**Post date:** [July 18, 2025, 11:51am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/40 "2025-07-18T11:51:07Z")

</div>

![glide to cloudflare changed IP 202507181950](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/a/8/a81ed2de5b7c82a252c4f0bdefd62148e3a5b326.png)

is that correct? any changes needed to be made?

---

<div class="post-metadata">

**Author:** ![steveforwan](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@steveforwan](https://community.glideapps.com/u/steveforwan)\
**Post date:** [July 18, 2025, 11:54am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/41 "2025-07-18T11:54:40Z")

</div>

> [@All Apps domains have failed. Again](#):
>
> 172.67.20.230

it works just fine now with dreamlifthk.page . But how about i set the same IP 172.67.20.230 for [clawdollmap.com](http://clawdollmap.com) domain for another website? will it conflict?

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [July 18, 2025, 12:03pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/42 "2025-07-18T12:03:11Z")

</div>

Wasn’t it the same IP for both previously? Now it’s just a different IP. Should be fine.

[Previous page](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223.md?page=1)

[Next page](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223.md?page=3)
