©CC BY-NC-SA 4.0

频道: cx.ms/channel
笔记: cx.ms/memo
博客: cx.ms/blog
剪贴: cx.ms/clip
社交: cx.ms/sns
#吐槽

Cloudflare 三天前更新, 把自己的公共 DNS 解析器 1.1.1.1 的缓存响应顺序改出了一点问题, CNAME 响应的本来是先响应解析结果 example.com IN CNAME cname.org 然后再跟着 cname.org IN A 1.0.0.1. 更新之后突然之间变成了 example.com 的响应直接先是 cname.org IN A 1.0.0.1, 然后才是 example.com IN CNAME cname.org.
本来 DNS 也没严格规定响应结果的顺序, 只要能解析出 IP 就行. 但是另一边, 某些企业的思科交换机预设了 1.1.1.1 为 DNS, 而交换机系统解析 NTP 服务器和 www.cisco.com 的时候只会按照 DNS 响应结果顺序去找自己要的 IP, 于是第一条本来就是是结果的响应大概是被当成错误处理掉了, 因为响应变成了 canme.org 的 A 记录, 而预期应该是 example.com 的 A 记录. 然后交换机系统来到第二条看到一个 CNAME 记录, 但是继续往下找却没找到这个 CNAME 的 IP, 于是认为是解析失败了.

Cloudflare Status - Global Issues with 1.1.1.1 public resolver
https://www.cloudflarestatus.com/incidents/rk3dgkmy89kc

Cisco switches hit by reboot loops due to DNS client bug
https://www.bleepingcomputer.com/news/security/cisco-switches-hit-by-reboot-loops-due-to-dns-client-bug/?sa=1#cid37986

#Cloudflare #DNS

via Nostr@cxplay
#吐槽

In reply to nevent1q…hv4z
_________________________

I am always sensitive to any naming or convention that is described as "human-readable" because they virtually imply permanence, despite the fact that I could theoretically modify them. However, doing so would break many references and links that are built upon these readable names. In the fediverse, it even binds user identities to domain names, once key exchange occurs, the domain name effectively becomes an immutable resource.

via Nostr@cxplay
#吐槽

方向錯亂 - pixiv / Twitter
* https://www.pixiv.net/users/2671042
* https://x.com/houkou_sakuran

难得的不是画白幼瘦也不是大粗肿的, 更加符合我「健全」和「丰满」 定义的画师. 图为几个经常被人画成白幼瘦或者大粗肿的角色, 他的笔下就很和谐了. 虽然说某些官方设定里面就是那样的, 但同人就应该拿出同人该有的创造力, 我作为观众也可以说我不喜欢某些官设里面的人物设计.

#art

via Nostr@cxplay
Back to Top