CNAME record

Every release before 1.26.1 is affected.

Upgrade to that, which shipped the same day, and closes eight more flaws, including a heap corruption in CNAME synthesis that Anthropic reported.

Eight, an unauthenticated attacker can drop Bind's Named process by sending one DNS over HTTPS request with a cryptographically invalid SIG0 record, and then closing the connection early.

It is one out of seven remote denial service flaws in the same release.

It's always the grammar part that trips me up.

Available records are A, Quad A, CNAME, MX, and TXT.

There we go.

So we've got that there.

We do not want that.

on that list.

So in that particular case, we would use a CNAME, a canonical name record.

This is exactly what the CNAME is built for, so that you can have a single device that might have a large number of names associated with it.