On Sep 9, 8:32 am, "Rick Yazwinski (Principal Engineer - Tucows Inc.)"
Thanks Rick, and sorry for being so late in answering.
> At Tucows we sell wholesale email services. Completely whitelabel and
> brandable for our customers needs.
> It's be great if as part of our provisioning of a new customer we
> could manage their data in the ispdb through a json call or some other
> Essentially we'd want to be able to add (or update) an entry and
> eventually be able to delete that entry if the customer moved away
> from us.
> Will this be available in the new ispdb setup?
As Ludovic said, our approach at first is going to focus on manual
steps, and making sure that the basics work. But I'd very much like
this system to scale to a long-tail of domains, and I expect that
facilitating cooperation with wholesalers such as yourselves would be
a good way to do that.
It'll take some crypto and API work, but in principle, as long as we
can get comfortable that the system is secure, it seems fine too.
Note that there are other possibilities which might be easier to do
from your perspective -- for example we've thought about doing a
variation of the exchange autodiscovery system, which, IIUC, means
that for a domain foo.com
, we could do a query on autoconfig.foo.com
(or some variation) and get data there directly, w/o going through our
central DB. That has the advantage of being decentralized, but there
are technical challenges to doing that (DNS may not be secure enough,
DNSSEC isn't deployed enough, plain HTTP wouldn't be secure enough,
HTTPS is more work to setup, it might not even work for you if you
only handle MX records and not domains, etc. etc.).