In fairness, DNS entries do get cached for a while (usually 24 hours), so you might have gotten a stale version of the resource record. It’s even entirely possible that whatever DNS resolver Musk uses did have the up to date version already while yours did not.
Still, Twitter should double and triple checked that this works even from other resolvers before announcing it like this.
In fairness, DNS entries do get cached for a while (usually 24 hours), so you might have gotten a stale version of the resource record. It’s even entirely possible that whatever DNS resolver Musk uses did have the up to date version already while yours did not.
Still, Twitter should double and triple checked that this works even from other resolvers before announcing it like this.
Twitter didn’t announce it, Twit did.