3 ms·

I have a service which allows git to be used to manage DNS. The way this used to work was that you'd host your DNS records in a github/etc repositories, config

I have a service which allows git to be used to manage DNS. The way this used to work was that you'd host your DNS records in a github/etc repositories, configure a webhook to point to my server, and then your updates would trigger DNS-updates. Rather than fighting to understand webhooks from the various git-hosting services I've decided that volume is low enough that I should just host the git repositories myself. I've spend a few evenings preparing for this transition, updating documentation, and reworking my codebase to avoid all use of webhooks. It's a fun update, which will simplify the service for new users, but keeping both systems in use at the same time makes it a little more complex than I'd like. I guess I need a flag-day in a few months where I drop the old webhook support.

strick 11y ago
That is very cool. Any chance a company could run that tool on premises? I think there is a market for that.
- stevekemp 11y ago
  Given that it ultimately pokes around with Amazon's route53 infrastructure I'm not too sure that there'd be a gain if the site/processor were available in-house. Even if the manipulation were local, the Amazon API would be remote, and not within a company's control. Interesting idea though. Most of the backend is portable perl and easy to pull out..
  - strick 11y ago
    Lots of companies already trust AWS and host various services there. Many of those companies might not trust your git servers to be up and running 24/7 with Amazon-like SLAs.
    - stevekemp 11y ago
      Thanks for the interesting perspective. I guess when I strip it down I've written a tiny layer of magic to convert a (bastardized)TinyDNS zone-file, or Bind zonefile, into Amazon Route53 update commands. Selling that as a one-off utility would be hard, but it does currently work well as a hosted service via the webhook integration-layer, and a small amount of git-magic. I will have a think to see if people would prefer it self-hosted, though nobody has expressed any interest in that previously.

strick 11y ago

That is very cool. Any chance a company could run that tool on premises? I think there is a market for that.

stevekemp 11y ago
Given that it ultimately pokes around with Amazon's route53 infrastructure I'm not too sure that there'd be a gain if the site/processor were available in-house. Even if the manipulation were local, the Amazon API would be remote, and not within a company's control. Interesting idea though. Most of the backend is portable perl and easy to pull out..
- strick 11y ago
  Lots of companies already trust AWS and host various services there. Many of those companies might not trust your git servers to be up and running 24/7 with Amazon-like SLAs.
  - stevekemp 11y ago
    Thanks for the interesting perspective. I guess when I strip it down I've written a tiny layer of magic to convert a (bastardized)TinyDNS zone-file, or Bind zonefile, into Amazon Route53 update commands. Selling that as a one-off utility would be hard, but it does currently work well as a hosted service via the webhook integration-layer, and a small amount of git-magic. I will have a think to see if people would prefer it self-hosted, though nobody has expressed any interest in that previously.