3 ms·

Using CAA Records with Namecheap

19 points by aaronmdjones 1y ago

aaronmdjones 1y ago
I've been wanting to make a blog for a while now. This incident is as good a source of material as any.
- sejnfgd 1y ago
  Not really. You kinda come off as a twatwaffle in the way you interact with front line support folks who are unlikely to even know what an RFC is, let alone have read one. Who the hell uses their registrar as their primary name server anyway?
stop50 1y ago
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.
- aaronmdjones 1y ago
  I would do that if I could (I have done that in the past for other domains, and I am doing that right now for a subdomain of the domain in question). The domain itself is not mine; I only have enough access to maintain its records.
popcalc 1y ago
Plugging Infomaniak, the rare large registrar that has competent customer support.
n0ot 1y ago
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.
creatonez 1y ago
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.
- slater 1y ago
  Some discussion here: https://comp.mail.misc.narkive.com/TSEnT0kU/rfc-compliant-signatures-which-rfc-is-it https://comp.mail.misc.narkive.com/TSEnT0kU/rfc-compliant-si...
  - creatonez 1y ago
    Ah, that explains it. We're supposed to remember conventions from the Usenet days. I am sad to report that Usenet users are in their 50s and 60s now, so someone will need to pass the torch or this information will be lost to time! Snarkiness aside, I genuinely appreciate that email formatting was documented somewhere, even if it turns out that signature rules were just a convention and not a MUST in that RFC2646 document (as I would have expected given how forcefully people say it is the correct way)
    - aaronmdjones 1y ago
      For what it's worth, I used to post to Usenet a lot in my teens, and I'm only 34 now :)
- aaronmdjones 1y ago
tepmoc 1y ago
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

19 points by aaronmdjones 1y ago

aaronmdjones 1y ago

I've been wanting to make a blog for a while now. This incident is as good a source of material as any.

sejnfgd 1y ago
Not really. You kinda come off as a twatwaffle in the way you interact with front line support folks who are unlikely to even know what an RFC is, let alone have read one. Who the hell uses their registrar as their primary name server anyway?

stop50 1y ago

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.

aaronmdjones 1y ago
I would do that if I could (I have done that in the past for other domains, and I am doing that right now for a subdomain of the domain in question). The domain itself is not mine; I only have enough access to maintain its records.

popcalc 1y ago

Plugging Infomaniak, the rare large registrar that has competent customer support.

n0ot 1y ago

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.

creatonez 1y ago

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.

slater 1y ago
Some discussion here: https://comp.mail.misc.narkive.com/TSEnT0kU/rfc-compliant-signatures-which-rfc-is-it https://comp.mail.misc.narkive.com/TSEnT0kU/rfc-compliant-si...
- creatonez 1y ago
  Ah, that explains it. We're supposed to remember conventions from the Usenet days. I am sad to report that Usenet users are in their 50s and 60s now, so someone will need to pass the torch or this information will be lost to time! Snarkiness aside, I genuinely appreciate that email formatting was documented somewhere, even if it turns out that signature rules were just a convention and not a MUST in that RFC2646 document (as I would have expected given how forcefully people say it is the correct way)
  - aaronmdjones 1y ago
    For what it's worth, I used to post to Usenet a lot in my teens, and I'm only 34 now :)
aaronmdjones 1y ago

tepmoc 1y ago

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