mitruly on gh-pages
updated site updated site updated site and 8 more (compare)
mitruly on master
Add max retries to MySQL queue … (compare)
./bin/docker-up-vinyldns.sh --version 0.9.4-SNAPSHOTand everything will start up with the test LDAP instance. I am open to thoughts on how to "start up" an alternative version. I suppose I could also promote this to the default and update the README
I completely mangled my explanation above (thanks mobile) so I deleted it; an example could resemble the following:
.xyz, such as
.xyzcan host second+ level domains via dynamic DNS; allowing second+ level operators to own and maintain zone data
In the scenario above:
@pauljamescleary Anyone can connect a zone; but that requires:
a) the zone to exist
b) the zone clause in
c) TSIG key generation for
allow-transfer in that clause
That is something that dnsadmin of .xyz would control for abc.xyz; if the .xyz DNS infrastructure was hosting abc.xyz
.xyz dnsadmin would do the steps above, then create the zone connection in the portal, and assign a user to be a "zone admin" or "super user" for abc.xyz
abc.xyz zone admin could then assign a user to mange limited records? (a.abc.xyz, cname.abd.xyz, txt.abc.xyz)
for a child zone of lmno.abc.xyz; the process would need to be repeated as above.
However, all of those users require an account in LDAP correct? Which account is the keystone (portal admin) account; how is that designated?
testuserinteraction for the moment; connect/abandon zones; record operations; verifying on my test DNS backend, etc.
./bin/docker-up-vinyldns.sh --version 0.9.4-SNAPSHOT --clean
planetexpressdocumentation and structure is comprehensive and I think it made sense to keep the container. :) There are definitely some deltas between the Debian-based
docker-test-openldapdocker vs. Red Hat/CentOS OpenLDAP setups ... For example: Red Hat's KB article re: OpenLDAP & cn=config has steps for manually editing
olcDatabase=\*files. I would not recommend. :(