# All custom domains fail to resolve **URL:** \ **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:** 3
**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, 12:10pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/43 "2025-07-18T12:10:52Z")
thats why i wonder why the previous IP didn’t work… i thought it was because two websites using same IP address for their custom domain creates conflicts. ---
**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:14pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/44 "2025-07-18T12:14:02Z")
Everybody uses the same IP. It was a different problem. This is the fix. ---
**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, 12:25pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/45 "2025-07-18T12:25:30Z")
May i know what should i do to fix it myself when it comes to the same problem everytime? Thanks so much Jeff! ---
**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:45pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/46 "2025-07-18T12:45:12Z")
This should not be a normal occurrence. But if it does happen again, Glide would have to be involved in the same way. It is their servers, so they are the ones that have to make corrections before you would have to do anything with reconfiguring your domain. ---
**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, 7:31pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/47 "2025-07-18T19:31:28Z")
I merged a couple of threads, so now I’m reposting my last update: We’re aware that custom domains are not working. Using 172.67.20.230 as the A Name record is no longer a solution, and we’ve reached out to our service provider. The current thought is that they’re working on resolving the original issue, which is causing a disruption to the 172.67.20.230 address. You can follow the status here: [Minor incident: Some custom domains not resolving | Glide Status](https://status.glideapps.com/incidents/303217) We’re sorry for the inconvenience and appreciate your patience as we work to resolve this. In a pinch, you can still use the Glide provided URL (ex, my-app.glide.page). ---
**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, 8:12pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/48 "2025-07-18T20:12:01Z")
This is the biggest problem, all the users in the app including all QR Codes promotions are linked to the custom domain, using Glide provided URL is not a practical option for businesses ---
**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, 8:13pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/49 "2025-07-18T20:13:33Z")
Please provide a proper A Name record for the circumstances to us for the final resolution ---
**Author:** ![Pete\_Lippincott](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/pete_lippincott/32/19429_2.png) [@Pete\_Lippincott](https://community.glideapps.com/u/Pete_Lippincott)\ **Post date:** [July 18, 2025, 9:31pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/50 "2025-07-18T21:31:19Z")
Same issue with my domain [airhockeyrank.com](http://airhockeyrank.com) ![Screenshot 2025-07-18 at 4.32.32 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/8/68c3cef61e70b50fa65e4f586184f4bc9ca75860.png) ---
**Author:** ![E\_J\_E](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/e_j_e/32/29498_2.png) [@E\_J\_E](https://community.glideapps.com/u/E_J_E)\ **Post date:** [July 18, 2025, 10:26pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/51 "2025-07-18T22:26:20Z")
Having same issue for my domain: [ejeagro.com](http://ejeagro.com) also down. tried yesterday the partial fix changing the A address, but thats down again today. Not so minor after a hours down! Any time guide on when it will be fixed??? ---
**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:26pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/52 "2025-07-18T23:26:56Z")
Awaiting to get the latest update fix or any working IP address ? the recent one 172.67.20.230 isnt working anymore! ---
**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, 11:27pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/53 "2025-07-18T23:27:43Z")
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:** 1. **It takes a little while for the DNS changes to be applied, so be patient.** 2. **The IP addresses in the Custom Domain configuration tool have been updated, but if you saw one of the old addresses, you can ignore it.** 3. **If you restarted the Custom Domain configuration process, make sure to click through to the last screen so the app knows it still has a Custom Domain associated with it.** You only need to use one of the above IP addresses. To help distribute traffic and improve reliability, we recommend choosing randomly – flip a coin, roll a die, or let your favorite pet decide. Both options are equally valid. We understand how frustrating it is to be asked to make this kind of change more than once in a short period of time. While the situation is outside of our direct control, we’ve worked closely with our service provider to ensure these new IPs are not subject to the same problem and will remain in place going forward. We’re also taking steps behind the scenes to prevent this type of disruption in the future. In the meantime, thank you for your continued trust and patience while we work through this with our infrastructure partner. If you have any questions, we’re here to help. ---
**Author:** ![mrt224](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mrt224/32/490_2.png) [@mrt224](https://community.glideapps.com/u/mrt224)\ **Post date:** [July 19, 2025, 12:13am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/54 "2025-07-19T00:13:14Z")
what if my domain was not affected? ---
**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 19, 2025, 12:18am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/56 "2025-07-19T00:18:07Z")
That’s probably because you had subdomains like [app.domain.com](http://app.domain.com/). ---
**Author:** ![mrt224](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mrt224/32/490_2.png) [@mrt224](https://community.glideapps.com/u/mrt224)\ **Post date:** [July 19, 2025, 12:19am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/57 "2025-07-19T00:19:19Z")
that is correct ---
**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:39pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/58 "2025-07-18T18:39:07Z")
172.67.20.230 This is the A record I’m using over at GoDaddy for my custom domain. My website isn’t resolving but my glide.page is. I get it, guys, its free advertising to have to point all users at your domain, but c’mon here. 😉 Seriously, though, what I can I do to resolve this issue? ---
**Author:** ![newyorkengineer](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/newyorkengineer/32/91527_2.png) [@newyorkengineer](https://community.glideapps.com/u/newyorkengineer)\ **Post date:** [July 18, 2025, 9:33pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/59 "2025-07-18T21:33:22Z")
My domains were down and 172.67.20.230 worked earlier today. Now I just checked again and having the same issues again. ---
**Author:** ![TappTech](https://avatars.discourse-cdn.com/v4/letter/t/a587f6/32.png) [@TappTech](https://community.glideapps.com/u/TappTech)\ **Post date:** [July 18, 2025, 10:16pm UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/60 "2025-07-18T22:16:25Z")
All of our apps have been down since 1pm CST because of a custom domain issue. This is no a “Minor Incident”. ---
**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 19, 2025, 12:53am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/61 "2025-07-19T00:53:10Z")
> [@dezwatz](#): > > Seriously, though, what I can I do to resolve this issue? Please read the solution posted above: > [@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.) You only need to use one of them. To help distribute traffic and improve reliability, we recommend choosing r… ---
**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 19, 2025, 12:57am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/62 "2025-07-19T00:57:26Z")
Thanks for sharing the IP addresses. I’ve updated the A records as instructed — using one IP for each of my two apps — but unfortunately, neither of them is working so far. Is it just a matter of time until everything is back up and running normally? Appreciate your help as always. ---
**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 19, 2025, 12:59am UTC](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223/63 "2025-07-19T00:59:16Z")
> [@Miguel\_Coelho](#): > > Is it just a matter of time until everything is back up and running normally? Yes, it takes a little time for the changes to propagate. Please be patient. [Previous page](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223.md?page=2) [Next page](https://community.glideapps.com/t/all-custom-domains-fail-to-resolve/83223.md?page=4)