-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposed DNS management solution for iojs.org and nodejs.org #124
Comments
👍 sounds like a solid approach. |
@rvagg did you get the email with our LF point of contact on the DNS? Please also sync with @misterdjules as well b/c we wouldn't want anything to break. |
@mkdolan yep, I have that email, and yes, @misterdjules should definitely be part of the process, I'm not suggesting a radical break with the past or anything and want to make sure that any legacy concerns are taken care of while we're doing this. I'll get iojs.org set up first so I can use that as a concrete proposal and we can assess from there. |
Great, just wanted to make sure all the connections are there.
|
Since we're using cloudflare I don't see this change in the foreseeable future. Closing. |
Continuing on from @mikeal's comments here.
We are currently using Route53 for for iojs.org but it's not transparent enough yet. I really like the approach of building tooling around this like what I did in https://github.com/nodejs/email so that the DNS config can be stored on GitHub and can be discussed and changed via pull request with a couple of people authorized to run a simple command that will sync the config with Route53.
I've actually used cli53 in the past and have had good results, so we could actually use a proper zone file format for this.
So, here's my proposal for how to achieve this:
I'll put up my hand for this but of course anyone else with energy and skills is welcome to jump on in since I'm not the quickest at getting things done these days.
/cc @mkdolan
The text was updated successfully, but these errors were encountered: