I always manage my dns via own servers(currently using Powerdns). these webuis always miss recordtypes or try to parse them before giving it to tge dns servers.
I've been wanting to make a blog for a while now. This incident is as good a source of material as any.
First time, eh? I remeber namecheap had problems 10 years ago when they upgraded interface and something was wrong with dns srv records. So i had to move out to gandi at time
I was working on a CAA implementation and wanted to use one of my domains (at Namecheap) to test. This was around 5 years ago. I had the same frustrating experience with support. I understand front line support personelle might not know what the heck an RFC is, but you'd think this would be a case when escalating to the next level would be warranted. I felt like they weren't even reading half of my message. I switched to different nameservers, and that worked fine in my case. I did eventually move over to Porkbun, but not for that reason.
Plugging Infomaniak, the rare large registrar that has competent customer support.
Okay, this is a nitpick, but:
> They also haven't correctly signed off the e-mail with --. No matter, this is hardly the first case of a company that can't correctly send e-mail these days. Note this is meant to be hyphen, hyphen, space, but I can't figure out how to get Markdown to not eat that last space.
I've been looking for a while, and I can't find a single plaintext email formatting guide that specifies exactly how to format a signature. Even RFC1855 doesn't cover this topic. How is anyone supposed to find this information? Anyone who cares so precisely about plaintext email formatting should publish a style guide, because obviously this information has been lost to time. No wonder nobody knows how to send an email, no one is interested in telling anyone how to.
> Also, DNS propagation is a myth.
Since when? Is this another hyper-specific nitpick? Ignoring TTLs is still a thing, and accidentally burning yourself by setting too high of a TTL is still a thing.