Earlier quoted context omitted.
It seems like a pretty useful feature one of the big boys could offer to differentiate themselves. Or I could see a new entrant in the domain seller space marketing this as a main feature.
But it only works if it has significant compliance. If a new entrant offers the service, there's little reason for other places to implement it, because only a tiny percentage of their customers will be using it. And the big boys have a disincentive because they already offer things like email and web hosting. Making it easy for people to buy those services elsewhere will cut in to their revenue.
Mess with DNS
91–94 of 94 posts
Re: Mess with DNS
#92Earlier quoted context omitted.
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/ 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/2…
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
Re: Mess with DNS
#93Earlier quoted context omitted.
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
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.