TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

IO name servers down

102 点作者 gator-io超过 7 年前
I&#x27;m getting swamped DNS resolution errors for anything .IO.<p>ns-a1.io timesout on every request so do all the others

13 条评论

fenwick67超过 7 年前
I&#x27;m so glad I passed on the .io TLD for my personal page and got .pizza one instead.
评论 #15300364 未加载
评论 #15299284 未加载
devnull42超过 7 年前
It appears that the issue at first impacted all servers in the anycast pool however eventually it only impacted servers ns-a2 and ns-a4. Those servers started returning NXDOMAINs. I am wondering if this was related to the root server key change yesterday. .IO seems to struggle with basic DNS engineering. We are seeing stabilization except for minor issues still on one of the gTLD servers.
评论 #15295734 未加载
评论 #15295452 未加载
JelteF超过 7 年前
For more info check the other post on this topic: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=15293578" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=15293578</a><p>Not sure why that was taken of the front page suddenly.
X-Istence超过 7 年前
Noticed this issue this morning too...<p><a href="https:&#x2F;&#x2F;twitter.com&#x2F;bertjwregeer&#x2F;status&#x2F;910515512903319552" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;bertjwregeer&#x2F;status&#x2F;910515512903319552</a><p>Interestingly enough I found that only some of them were returning NXDOMAIN&#x27;s, so resolution would sometimes work and sometimes it would fail completely.
nodesocket超过 7 年前
Same here for my startup commando.io. Using AWS Route53. What DNS provider are you using?
评论 #15295118 未加载
评论 #15295286 未加载
评论 #15293878 未加载
gator-io超过 7 年前
I am so done with .io. This is one of many issues they&#x27;ve had in the last year.<p>My problem is that we have scripts all over customer websites hardcoded with api.gator.io<p>We&#x27;re going to have to have them update the scripts and that is going to be a major pain.
评论 #15297270 未加载
tbarbugli超过 7 年前
team mate posted on HN already about this: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=15293578" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=15293578</a>
riffic超过 7 年前
Not a surprise; country code top-level domains are run poorly and I sure wouldn’t stick all of <i>my</i> eggs in this single basket.
tbarbugli超过 7 年前
These two nameservers: ns-a2.io, ns-a4.io return wrong results consistently
gator-io超过 7 年前
Everything appears to be functioning at this point
jmkni超过 7 年前
Seems to be sorted now
thekemkid超过 7 年前
Seems like a hijacking: <a href="https:&#x2F;&#x2F;www.theregister.co.uk&#x2F;2017&#x2F;07&#x2F;10&#x2F;io_hijacking_in_transition_cockup&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.theregister.co.uk&#x2F;2017&#x2F;07&#x2F;10&#x2F;io_hijacking_in_tra...</a>
评论 #15295247 未加载
partycoder超过 7 年前
Well, the .io domain name is intended for the British Indian Ocean territory.<p>I think the common practice of misusing TLDs (such as registering an .io domain if you are not from the British Indian Ocean territory, or having a Soviet Union domain... a country that no longer exist), is bad.<p>However, I acknowledge this is not the root problem. The root problem is the scarcity of domains under traditional TLDs, and that&#x27;s in great part due to speculation (e.g: domain parking). It is hard to establish what constitutes placeholder content, therefore rules preventing domain parking are hard if not unfeasible to forbid.
评论 #15299134 未加载