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
Proof of concept #2
Comments
The tricky bit is the JSON representation format, which I'd like to nail down (at least in a basic sense) for POC. It's more of a standard API of sorts, allowing for flexibility of metadata. The standardEvery DJDNS document must contain a resource of type "direct/json" and path "/djdns-branch". The contents of the top-level map must contain the following keys according to specifications. Other keys may be present, they will simply be ignored for DJDNS purposes. branchesThe first required property is "branches", which is a list of branches, using list order to infer priority (first = highest, perfect for traversal). branchEach branch is an mapping with the following properties:
Targets support the following pseudoprotocols:
The correct behavior of the server is to check if "records" has items in it, return them all via DNS if so, and otherwise recurse through the targets (in whatever order the server feels like) until it finds a matching branch with records. reverseReserved. Will be a very branches-like approach to reverse DNS. metaHuman-readable metadata about this DJDNS document.
|
For the purpose of the POC, I'm just going to implement a very simplistic branch traversal system. |
Serve static content from local files as DNS data.
The text was updated successfully, but these errors were encountered: