# Internal network DNS propagation and new deployments

**URL:** <https://community.fly.io/t/internal-network-dns-propagation-and-new-deployments/3672>\
**Category:** Questions / Help\
**Created:** [January 13, 2022, 2:20pm UTC](https://community.fly.io/t/internal-network-dns-propagation-and-new-deployments/3672 "2022-01-13T14:20:49Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\
**Post date:** [January 13, 2022, 3:07pm UTC](https://community.fly.io/t/internal-network-dns-propagation-and-new-deployments/3672/4 "2022-01-13T15:07:22Z")

</div>

Yes I think that will work!

The deploy downtime you see through `<app>.fly.dev` is probably due to our slow service propagation. If you’re running behind an nginx, it probably won’t affect you.

The workaround until we get this fixed is to `fly scale count 3`. You can see more details here: [how do fly.io deploys work? - #2 by kurt](https://community.fly.io/t/how-do-fly-io-deploys-work/3378/2)

---

_[View the full topic](https://community.fly.io/t/internal-network-dns-propagation-and-new-deployments/3672)._