# Forum down only for chrome? RESOLVED

**URL:** <https://discuss.emberjs.com/t/forum-down-only-for-chrome-resolved/7322>\
**Category:** Meta\
**Created:** [February 14, 2015, 1:50pm UTC](https://discuss.emberjs.com/t/forum-down-only-for-chrome-resolved/7322 "2015-02-14T13:50:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![broerse](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/broerse/32/9497_2.png) [@broerse](https://discuss.emberjs.com/u/broerse)\
**Post date:** [February 14, 2015, 1:50pm UTC](https://discuss.emberjs.com/t/forum-down-only-for-chrome-resolved/7322/1 "2015-02-14T13:50:24Z")

</div>

This forum can’t be used since this morning from multiple PC’s in the Netherlands in Chrome because of this error:

GET [http://www.fastly.net/](http://www.fastly.net/) net::ERR\_NAME\_NOT\_RESOLVED

In IE all works fine from the same PC’s ??

Seems like some strange CDN bug.

More detail: GET [https://sea1.discourse-cdn.com/flex019/uploads/stylesheet-cach…ktop\_fbb9e644ff1969ad6b74177ab1a8eba4c43c1d6e.css?\_\_ws=discuss.emberjs.com](https://sea1.discourse-cdn.com/flex019/uploads/stylesheet-cach%E2%80%A6ktop_fbb9e644ff1969ad6b74177ab1a8eba4c43c1d6e.css?__ws=discuss.emberjs.com) net::ERR\_NAME\_NOT\_RESOLVED

---

<div class="post-metadata">

**Author:** ![broerse](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/broerse/32/9497_2.png) [@broerse](https://discuss.emberjs.com/u/broerse)\
**Post date:** [February 14, 2015, 3:38pm UTC](https://discuss.emberjs.com/t/forum-down-only-for-chrome-resolved/7322/2 "2015-02-14T15:38:42Z")

</div>

With some great help from [Fastly](http://www.fastly.com)’s @cjackel we found that this issue only concerns [KPN](http://kpn.com) users that use the Primary DNS: 195.121.1.34, Secondary DNS: 195.121.1.66 numbers. It keeps working in all browsers but Chrome. Clearing caches and host cache does not help but if you switch to the google DNS Chrome works again fine with this forum. Perhaps it is just a strange DNS wave only effecting Chrome?

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/codinghorror/32/3515_2.png) [@codinghorror](https://discuss.emberjs.com/u/codinghorror)\
**Post date:** [February 15, 2015, 6:28am UTC](https://discuss.emberjs.com/t/forum-down-only-for-chrome-resolved/7322/3 "2015-02-15T06:28:23Z")

</div>

Bizarre. Glad Fastly was able to help. This is why we use them, because they are the best! 😃

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/codinghorror/32/3515_2.png) [@codinghorror](https://discuss.emberjs.com/u/codinghorror)\
**Post date:** [November 6, 2016, 5:43am UTC](https://discuss.emberjs.com/t/forum-down-only-for-chrome-resolved/7322/5 "2016-11-06T05:43:39Z")

</div>


