Settings

Theme

Top Ten Most Frequent DNS Test Failures

dnsinstitute.com

22 points by jarreed0 · 5 comments

Reader

3 threads
colmmacc

This is an odd set of tests.

Apart from the negative cache value, none of the numbers in a SOA record matter at all unless you're doing very old-school secondary DNS setups with AXFR/IXFR, usually with Bind or maybe NSD. That's rare these days, and not very secure. You really shouldn't use that.

A TTL of 30 minutes is a terrible idea if you're using DNS for failover with health checks, or load balancing, and a negative cache value of 30 minutes also seems unnecessarily long. That's a long time to have people impacted by a mistakenly deleted record.

The CD bit being set or not doesn't matter if you're not using DNSSEC. Though it's probably worth getting the bit correct.

canvascritic

kind of an aside, but i've always been curious about how different DNS server implementations handle TTL outliers, especially given the discrepancies between recommended values and real-world configurations. particularly re D103900 in TFA about the SOA TTL recommendation, does anyone here have insights on dealing with the rate of stale records in caches due to exceptionally high TTL values? additionally, has there been any analysis on the impact of DNSSEC chain of trust integrity with long-standing SOA EXPIRE values, like the mentioned "ma" TLD's 19 years?

  • sillystuff

    Most recursive resolvers allow you to set a maximum and minumum ttl to override the supplied TTL if outside your specified range.

    E.g., on unbound, cache-max-ttl and cache-min-ttl

ShadowBanThis01

Here's a nitpick for y'all to downvote: "Top" and "most" don't belong in the same title. It's just the "ten most frequent DNS test failures." "Top" is redundant.

Keyboard Shortcuts

j
Next item
k
Previous item
o / Enter
Open selected item
?
Show this help
Esc
Close modal / clear selection