Edition of Tuesday 17 November 2026

It's always DNS, so why are we running our own?

Comments on “It's always DNS, so why are we running our own?”

3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked

S2, a streaming infrastructure company, replaced AWS Route53 with a custom authoritative DNS server to support unlimited basins, each mapped to a subdomain via CNAME records. Route53's API limit of roughly 5 upserts per second made instant, strongly consistent record creation impractical under load.

Read the original at s2.dev. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 69 of 122 with a score of 0.57. The panel rated it highest on new information (0.90) and technical depth (0.73), lowest on significance (0.46). Placed No. 69, No. 101 by score alone: the fifth Infrastructure & DevOps story of the day (−0.040). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Solid engineering write-up on replacing Route53 with a custom authoritative DNS server; useful lessons on rate limits and DNS attacks, but narrow audience and no primary benchmarks or data.
AI judgeJudge 3gpt-5.6-luna
A detailed production engineering account of replacing Route53 with a custom, database-backed authoritative DNS service, including rate-limit failure, attack considerations, testing, Cloudflare protection, HA architecture, and operational tradeoffs.

Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.

Score

0.57total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.46
  • Reader interest0.71
  • Audience breadth0.49
  • Practical relevance0.63
  • Substantiated0.59
  • Technical depth0.73
  • New information0.90
  • Counts against: Promotional0.08
  • Counts against: Overclaim0.22

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.470.300.620.460.32+0.24+0.111
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.650.620.860.710.24+0.26+0.185
Audience breadthHow many people who build technology does it concern?0.540.400.520.490.14+0.13+0.063
Practical relevanceHow useful is it to someone who builds software or tech products?0.650.450.780.630.33+0.22+0.138
SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations.0.450.500.830.590.38+0.05+0.030
Technical depthHow technically substantive is it?0.820.600.780.730.23+0.05+0.037
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.870.850.970.900.12+0.05+0.045
PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional.0.060.150.030.080.12−0.19−0.015
OverclaimDo the headline or conclusions claim more than the body supports?0.300.200.160.220.14−0.11−0.024
Sum of contributions+0.569
Claim-check penalty0.000
Total, as published0.569

Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.

The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.

Ranked #69 on Rubric, 17 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-17/69/"><img src="https://rubric.hrih.si/badge/2026-11-17/69.svg" alt="Ranked #69 on Rubric, 17 Nov 2026" width="245" height="28"></a>

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 64 pts, front page

Discussion on Hacker News

Recorded for context only, checked 17 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “It's always DNS, so why are we running our own?”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.

  1. Score 0.78

    NoisyTCP