4 ms·

This is news to me. Can you provide more details or point to some documentation of this feature?

matthewaveryusa 5y ago
My friend, it took me a few hours to find it -- there's zero documentation on Cloudflare about cloudflare supporting it, but it's supported [1], but godaddy luckily is a lot more vocal about it [2], here's the spec: https://www.domainconnect.org/ https://www.domainconnect.org/ Don't you hate it when you have a good idea and someone already did it, but also love it because it's validation of your good idea? [1] https://www.godaddy.com/engineering/2019/04/25/domain-connect/ https://www.godaddy.com/engineering/2019/04/25/domain-connec... [2] https://dash.cloudflare.com/domainconnect/v2/domainTemplates/providers/google.com/services/domain-verification/apply?domain=x&redirect_uri=x&groupId=verification&verifytxt=x&sig=x&key=x https://dash.cloudflare.com/domainconnect/v2/domainTemplates...
- anderspitman 5y ago
  Wow, I'm still reading the spec but on the surface this appears to be almost exactly what I've been looking for for over a year[0] and somehow unable to find. I really appreciate you taking the time. And yeah I hear what you're saying about ideas haha. [0]: https://news.ycombinator.com/item?id=23761788 https://news.ycombinator.com/item?id=23761788
  - ate53 5y ago
    My problem with this spec is it requires Service Providers and DNS Providers to know about each other. It's essentially formalising the status quo of cookie cutter setups for big name providers.
    - anderspitman 5y ago
      Yeah, I read the website and the entire spec. I think it's pretty good, but it's built by big names for big names. There's nothing wrong with that, but I'm concerned it might not be appropriate for things like quickly pointing a simple A Record at a self-hosted open source service. Maybe I'm wrong. I'm having a good discussion with the spec developers here: https://github.com/Domain-Connect/spec/issues/64 https://github.com/Domain-Connect/spec/issues/64

My friend, it took me a few hours to find it -- there's zero documentation on Cloudflare about cloudflare supporting it, but it's supported [1], but godaddy luckily is a lot more vocal about it [2], here's the spec: https://www.domainconnect.org/ https://www.domainconnect.org/ Don't you hate it when you have a good idea and someone already did it, but also love it because it's validation of your good idea? [1] https://www.godaddy.com/engineering/2019/04/25/domain-connect/ https://www.godaddy.com/engineering/2019/04/25/domain-connec... [2] https://dash.cloudflare.com/domainconnect/v2/domainTemplates/providers/google.com/services/domain-verification/apply?domain=x&redirect_uri=x&groupId=verification&verifytxt=x&sig=x&key=x https://dash.cloudflare.com/domainconnect/v2/domainTemplates...

anderspitman 5y ago
Wow, I'm still reading the spec but on the surface this appears to be almost exactly what I've been looking for for over a year[0] and somehow unable to find. I really appreciate you taking the time. And yeah I hear what you're saying about ideas haha. [0]: https://news.ycombinator.com/item?id=23761788 https://news.ycombinator.com/item?id=23761788
- ate53 5y ago
  My problem with this spec is it requires Service Providers and DNS Providers to know about each other. It's essentially formalising the status quo of cookie cutter setups for big name providers.
  - anderspitman 5y ago
    Yeah, I read the website and the entire spec. I think it's pretty good, but it's built by big names for big names. There's nothing wrong with that, but I'm concerned it might not be appropriate for things like quickly pointing a simple A Record at a self-hosted open source service. Maybe I'm wrong. I'm having a good discussion with the spec developers here: https://github.com/Domain-Connect/spec/issues/64 https://github.com/Domain-Connect/spec/issues/64