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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Ask HN: Is Cloudflare DNS Broken?

4 点作者 xrd大约 1 年前
Over the last few months I&#x27;ve found that it takes a lot longer to add new DNS records which are managed by Cloudflare DNS. I get that they are probably managing billions of records and writing these zone files in a scalable way isn&#x27;t a simple problem; I expect there might be a minute delay, but it feels like I&#x27;m often waiting five to ten minutes which makes using certbot to get certificates a challenge.<p>Today I&#x27;m adding records and double check the name and they don&#x27;t show up in Google tools like https:&#x2F;&#x2F;toolbox.googleapps.com&#x2F;apps&#x2F;dig&#x2F;#TXT at all.<p>Does anyone know if something is happening there?<p>I check their self-reported status and nothing is reported:<p>https:&#x2F;&#x2F;www.cloudflarestatus.com&#x2F;

1 comment

xrd大约 1 年前
An update: I was using certbot with an internal address, which explains why certbot certonly did not work when it uses a self-hosted web server and webroot. But, there is still definitely something weird about using preferred-challenge dns + manual mode, the acme-challenge TXT records do not show up in the Google dashboard.