# Persistent DNS Resolution Errors

**URL:** <https://discuss.huggingface.co/t/persistent-dns-resolution-errors/153827>\
**Category:** Spaces\
**Created:** [May 6, 2025, 10:58pm UTC](https://discuss.huggingface.co/t/persistent-dns-resolution-errors/153827 "2025-05-06T22:58:02Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [May 7, 2025, 8:52am UTC](https://discuss.huggingface.co/t/persistent-dns-resolution-errors/153827/7 "2025-05-07T08:52:58Z")

</div>

I happened to find some information on Discord’s `ask-for-help`.

> [@Inference API stopped working](https://discuss.huggingface.co/t/inference-api-stopped-working/150492/45):
>
> From Hugging Face Discord: Tom Aarsen Hello! I believe some of the inference endpoints currently have “Scale to zero” enabled temporarily, meaning they will go down when there’s no usage for a while. The first request will then be slow/fail, but subsequent ones will work. We’re going to remove the scale to zero again so that this is not an issue anymore, apologies for the inconvenience. cc @ VB can you update the scale to zero for the big ST models that already had APIs?

---

_[View the full topic](https://discuss.huggingface.co/t/persistent-dns-resolution-errors/153827)._