4 ms·
I cannot believe how absurd and out of hand this has gotten. Why did we not all standardise on some _well_known. subdomain or similar for these dozens of recor
by technion 3y ago
I cannot believe how absurd and out of hand this has gotten.
Why did we not all standardise on some _well_known. subdomain or similar for these dozens of records?
The part that gives me an eye twitch is so many domains have multiple verifications for the same group, your own example has Google three times for example. The reason being one marketing company sets up Analytics. A few months later, a different company expects to be authorised to run another set, but all the admins get told is "you have to add this record".
- lathiat 3y agoThey also generally don't need to stay there it's usually one-shot (at least the ones I've seen) but no one bothers to delete them.
- bandrami 3y agoI give talks to IT teams on the importance of cleaning up transient auth records in DNS and, as the night follows the day, I don't do it on my own personal ones.
- xorcist 3y agoOr just allocate proper DNS records as the standard intended. There was a SPF record type in DNS, TXT was suggested as a transition, but we all know how that went. Incidentally, SPF is a good example how a large company hijacked the process and tried to stuff the standard with things they had taken out patents on. That made the end standard less useful than what it could have been.