3 ms·
Yep you’re right! My example was done with a CNAME on a subdomain (replaced the domain for privacy), and most providers provide flattening so I didn’t even thin
by antoniomika 4y ago
Yep you’re right! My example was done with a CNAME on a subdomain (replaced the domain for privacy), and most providers provide flattening so I didn’t even think about it! I’ll update the copy to mention that.
- naniwaduni 4y agoEven for a subdomain, having CNAME and TXT records on the same name isn't supposed to be okay; normally you'd work around it by reading the TXT record off an other unlikely-to-be-used subdomain of the name you're putting a CNAME on.
- antoniomika 4y agoNow that's one I never knew about. I'll have to take a look, should be easy enough to update prose to handle that though. edit: Updated prose to handle this
- mercora 4y agoi think SRV records might be more appropriate for this use case.
- kevincox 4y agoThis also has the advantage that it doesn't boat the TXT response for the domain. Putting it at some thing like _prose.sub.domain allows just getting the relevant record.